Last Updated: November 2026
A summary for school leaders and IT teams reviewing Askie for Schools: where student data is stored, which outside services process it, and how we handle FERPA, COPPA, breaches and deletion. Our Schools Privacy Policy and Schools Terms of Service are the binding documents, and they take precedence over this page.
The school stays in control of its students' data, and Askie uses it only to run the service for the school. We never show ads to students, never sell student data, and never use it to train AI models. The schools database is in Ireland, in the European Union, and some of the outside services listed below are based in the United States. If we confirm a breach of student data, we notify every affected school within 72 hours.
• The schools database: MongoDB Atlas, in Ireland, in the European Union. • Application servers: Railway, in its EU West region. • Files for the apps and games students build: Cloudflare R2, in the European Union. • Pictures and video clips: Cloudflare R2. • The schools product runs on its own services and its own database, separate from our consumer product. Some of the outside services in section 2 process data in the United States or other countries, as listed there.
Unless a location is given, a service may process data in the United States or other countries where it operates. • Railway: application hosting (EU West). • MongoDB Atlas: the schools database (Ireland, EU). • Google Cloud: AI for text, pictures, video clips, apps, games and read-aloud voices; Google's Gemini API for voice conversations; student memories (Netherlands, EU); and Firebase Cloud Messaging for app notifications. • Cloudflare: storage for pictures, video clips, and app and game files (app and game files in the EU), and delivery of the Askie for Schools website. • Daily: real-time audio for voice conversations. • Auth0: sign-in for teachers and students. • PostHog: product analytics (United States). Activity in student sessions is linked to a pseudonymous account ID. • Sentry: error and crash reports, with personal-data collection turned off (United States). • Resend: email to teachers and school staff. • Google Classroom and Wonde: roster sync, only if the school connects them. We will give schools advance notice of material changes to this list.
These services never receive student data: • Stripe: payments and billing for schools. • Google Ads: measuring which school sign-ups and purchases come from our advertising, using ad click identifiers on our website. • Meta and AppsFlyer: measuring which sign-ups and app installs come from our advertising, on the pages of our website that are not for students and when teachers use our apps. • UserJot: a feedback form for signed-in teachers on our website. • Telegram: internal alerts to the Askie team when a school's plan is bought, changed or cancelled, naming the account that bought it.
• A first name or nickname (or the name in the school's roster), age or grade level, avatar, learning preferences and class. • What students ask and make: questions and AI responses, voice conversations, and the pictures, apps, games and video clips they create. • Usage statistics for the teacher dashboard, the school's usage allowance and safety monitoring. Students do not create their own accounts, do not pay, and are not asked for contact details. Their teacher creates their account, or imports it from a roster the school connects. When a roster includes a date of birth, we keep only the age.
• Show advertising to students, or use student data for targeted advertising. • Sell or rent student data. • Build profiles of students for any purpose other than the school's educational use. • Use student data to train Askie's or anyone else's AI models. • Run advertising or ad-measurement tools in a student's session, on our website or in our apps.
• Every AI feature in Askie for Schools, from chat and voice to pictures, video clips and the AI App Builder, runs on Google's AI. No other AI provider receives student data. • Students' questions, voice conversations, picture and video requests, and app and game instructions are sent to the AI providers in section 2 only to produce the answer, picture, clip, app or game. • Under its terms, Google may not use this content to train its models. It may keep prompts and responses for a limited time to detect and prevent misuse and to meet legal obligations (for example, up to 55 days under Google's Gemini API terms), and then deletes them. • Askie can remember a few things a student shares in conversation, such as a favourite topic. These memories are stored in the EU, used only to answer that student, and deleted with the student or once the school's retention period has passed.
• Askie checks what students ask, and what the AI answers, against a list of words unsuitable for children. Students under 8 get a stricter list. • Google's own harm filters run on every answer, at Google's strictest setting for students under 8. • Picture and video requests are checked before anything is made, and what is made must suit the student's age. • Text in apps and games is checked before classmates can see it. Attempts to trick the AI into ignoring these rules are detected. • If a student mentions self-harm, abuse or danger, Askie answers kindly and encourages them to talk to a trusted adult. • If our safety review finds that a student may be at risk, Askie also emails the student's teachers a short alert with the kind of concern and a link to the conversation in the teacher dashboard; the email does not include the conversation. • In the teacher dashboard, teachers can read every conversation, picture and voice conversation transcript of their students, by student, class and date. • Teachers choose which features each class can use. Video clips and the AI App Builder stay off until a teacher turns them on. Teachers can also add their own learning units and hide Askie's built-in lessons. • Apps and games students build are private to the student and the teachers of their class. A student may share one with their class only: there is no public gallery and no public link. • No filter is perfect, and Askie does not replace teacher supervision. Askie is not an emergency service: if a student may be at risk, follow your school's safeguarding procedures.
For schools in the United States, Askie acts as a "school official" with a legitimate educational interest under FERPA (34 CFR § 99.31(a)(1)), under the school's direct control for the use and maintenance of student data. The school owns and controls its students' data. Parents and eligible students make requests to review, correct, export or delete student data through their school, and we help the school respond.
Askie for Schools relies on consent given by the school, or by a teacher acting for it, as COPPA permits for educational services a school authorizes. Student data is used only to provide the educational service to the school, and students are never asked for contact details or payment. • We collect only what the service needs, and students are never asked for an email address. • Student data is never used for advertising, never sold, and kept only for the school's retention period (section 10). • If a parent contacts us directly about their child's data, we refer them to the school and help the school respond.
• Student learning history older than the school's retention period is deleted automatically every week. The period is 90 days by default and can be set for each school between 7 and 365 days. • Voice session records are deleted automatically after 90 days. • Teachers can delete a student at any time. The student's history, pictures, voice records, apps, games and video clips are then deleted as described in our Schools Privacy Policy. • On the school's written request, or when the school's account ends, we delete the school's student data within 30 days, except where the law requires us to keep it. • School administrators can export the data of one student or of the whole school, and teachers can export the data of the students in their own classes, as a ZIP file of JSON records and media files.
We keep a written incident response plan for Askie for Schools, and we share a summary with any school on request. • Monitoring: automatic alerts for errors, outages and database problems in the schools product go straight to our team. • Who leads: our CEO leads the response to every incident, with a second senior team member as backup. • First steps: we contain the problem first, for example by blocking access or turning a feature off, and then work out which schools and what student data are affected. • Notifying schools: if a breach affected student data, we notify every affected school within 72 hours of confirming it, as described in section 12. • Records and review: we keep a written log of every incident and review it afterwards to prevent it from happening again. • Reporting a security concern: email askie@kidsai.app.
If we confirm a breach of security that led to unauthorized access to, or disclosure, loss or alteration of, student data, we will notify every affected school within 72 hours of confirming it. We will email the school's account holders and tell them: • what happened and when; • what student data was involved; • what we are doing about it, and what the school can do; • who to contact at Askie: askie@kidsai.app. We will keep the school updated as we learn more, and help it meet its own duties to notify families or authorities.
• Data is encrypted in transit (TLS) and at rest. • A teacher can see only their own students and the classes they teach or co-teach, and a school administrator only their own school. Every request is checked against the school. • Access to student data is restricted to the people who need it to run or support the service, and Askie's internal admin tools require a separate administrator role. • Students sign in with a personal login code or a Google account their school has imported. Sign-in is rate-limited and locks after repeated failed attempts. • Error and crash reports are collected with personal-data collection turned off.
• A Data Processing Agreement (DPA) is available on request, and we will sign a school's or district's data privacy agreement or addendum where required. • Questions, DPA requests and deletion requests: askie@kidsai.app. Send deletion requests from the email address of a school account holder. • Askie for Schools is operated by Askie Kids AI Limited (company number 16991192), registered in England and Wales.