Children and schools
How VESPR will treat students and children when we offer it to schools, written down first so schools and parents can hold us to it.
On this page
What is true today
- VESPR is not designed for children under 13 and we ask them not to use it (minimum age [to confirm with counsel]).
- There are no student accounts, no classroom features, no teacher tools and no school contracts.
- We do not knowingly collect data from children under 13. If you are a parent or school and think a child has used a workspace, write to [Children’s privacy contact email] and we will delete their data.
- The public demo is not a classroom product. See Privacy for what it stores and Security for its gaps.
Why this page exists
We plan to offer VESPR to schools, because a tool where every line records whether a student or an AI wrote it can help teachers. Children need stronger protection than adults. In the United States, the Children’s Online Privacy Protection Act (COPPA) covers online services for children under 13, and the Family Educational Rights and Privacy Act (FERPA) covers student records held for schools. States and other countries have their own rules. [counsel to review which laws apply]
Schools first: contracts Planned
- Students under 13 will use VESPR only through a school or district that has signed a written agreement with us. The school is our customer and decides who gets an account.
- Students will sign in through the school (Clever is the planned route), so we never ask a child to make a password with us.
- The agreement will limit use of student data to the school’s educational purpose, put the school in control of the data, and cover deletion and breach notice. [counsel to draft the agreement and confirm it meets COPPA and FERPA]
- Children will not be able to create an account on their own outside a school.
Parent and school consent Planned
- For students under 13, consent will come from the school for its educational use, or from a parent through a method we choose with counsel ([consent method]).
- Parents will be able to ask the school, or us when there is no school, to see, correct or delete their child’s data, and to refuse further collection.
- We will not require a child to share more than the class needs in order to use the tool.
What teachers can see Planned
- Teachers will be able to see a student’s conversations with the AI agent and which parts of the work the student wrote and which the agent wrote.
- Students will be told this on screen, inside the product, not only in this policy. There will be no hidden monitoring and no private chat with the agent in a student account.
- The student version of the agent is meant to give hints and ask questions rather than hand over answers, and to leave the student’s own files alone unless asked.
- Teachers will be able to set limits for a class: no internet for commands, run and AI-token limits, locked files.
What we will not do with student data Planned
- No ads, of any kind, in the student product.
- No selling, renting or trading student data.
- No profiling or targeting based on student data.
- No training or fine-tuning AI models on student data.
- No use for anything except providing the school’s educational service.
- No outside analytics or trackers, and no marketing messages to students.
What we would collect Planned
| Data | Why | Who sees it |
|---|---|---|
| Name or school ID, class | To put the student in the right class | The student, their teachers, the school |
| The student’s files and work | To do the assignment | The student, their teachers |
| Conversations with the agent, and who wrote which part | So the agent can help and the teacher can see the student’s own work | The student, their teachers |
| Usage counts (AI tokens, run time) | To keep within class limits | The teacher, the school |
We do not plan to ask for a phone number or a personal email address for school-issued sign-in.
Keeping and deleting Planned
- The school can export or delete student data at any time, and we will delete what remains within [number of days] of the contract ending.
- We plan to let a school choose where its data is stored. [regions]
- We will tell the school about a data breach within [number of hours].
AI model providers Planned
Student conversations would go to an AI model provider, as described in Privacy. We have not yet confirmed any provider’s terms for student data. We will use only providers whose agreements do not allow training on it, and we will list them to schools. [providers and terms to confirm]
What has to happen first Planned
- A lawyer reviews this page, the school agreement and our data handling. No school uses VESPR before that.
- The security gaps that matter for students are closed first: today anyone with a token can reach every workspace on a server, and the agent’s sandbox shares its secrets. See Security. [confirm this commitment before publishing]
- The student features are built and tested with teachers.
Contact
[Children’s privacy contact email], [Registered address].