Launch offer50% off your first year: $299.99 instead of $599.99 paying monthly, November only.Claim it →
elysianminds™ElysianMinds

Privacy Policy

Last Updated: October 29, 2026

1. Introduction

Welcome to Elysian Minds Innovations Limited ("Elysian Minds," "we," "us," "our," or the "Company"). We are committed to protecting the privacy of our users, especially the children who use our educational platform.

This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our educational platform designed for children aged 7-12. We operate on a parent-child model where parents (guardians) create and manage accounts for their children (students).

Please read this Privacy Policy carefully. By using our Service, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Parent, Guardian and Teacher Account Information

When a parent, guardian or teacher creates an account, we collect the following information:

Data TypeRequiredPurpose
Email AddressYesAccount identifier, sign-in, and communications for email-based accounts. An account may instead be created and secured with a phone number, in which case an email address may not be collected.
Full NameYesAccount personalization and communications
Account TypeYesWhether the account belongs to a parent or a teacher. It decides which packages we offer you and is shared with our CRM (Section 4.8).
PasswordConditional (hashed)Account security and sign-in for email-based accounts. Phone-based accounts are passwordless and no password is stored.
CountryYesLocalization, legal compliance, and tax purposes
Phone NumberConditionalAccount identifier and sign-in for phone-based accounts, and delivery of our parent messages over WhatsApp (with SMS as a fallback), covering one-time login and verification codes as well as account, billing, trial and re-engagement messages. Required for phone-based accounts; may otherwise be provided as a contact method.
LanguageYesLanguage preference (the Service is currently available in English)
TimezoneYesProper time display and scheduling

2.2 Student/Child Account Information

When a parent creates an account for their child, or a teacher creates one for a student, we collect the following information:

Data TypeRequiredPurpose
UsernameYesAccount identification and login
PasswordConditional (hashed)Sign-in with the child's own password, which a parent can turn off
First NameYesShowing the child's name in the app, in the voice greeting, and on the leaderboard and activity feed (Section 5.3). We ask for a first name only and do not collect a child's surname.
Date of BirthYesAge-appropriate content delivery (7-12 years)
CurriculumYesEducational content alignment (UK National Curriculum or United States state standards)
School YearYesPlacing the student in the correct school year for the selected curriculum (UK Years 3-8 or US Grades 2-7), derived from date of birth

2.3 Student Activity and Progress Data

We automatically collect the following data as students use the platform:

  • Lesson Progress: Tracking educational advancement
  • Answers to Questions: Educational assessment and content improvement
  • Experience Points (XP): Gamification tracking
  • Level and Badges: Achievement tracking
  • Streak Data: Engagement tracking (current and longest streaks)
  • Daily Quest Completions: Wellness activity tracking
  • Last Active Date: Activity monitoring

2.4 Avatar and Customization Data

To provide personalization features, we collect:

  • Gender selection for avatar appearance (stored as part of avatar data, not student account profile)
  • Customization choices (skin color, hair color, hair style)
  • Equipped items (clothes, accessories, effects)
  • Inventory of owned virtual items

2.5 Payment and Subscription Data

To run your subscription, we store:

  • Stripe Customer ID (reference for payment processing)
  • Stripe Subscription ID (subscription management)
  • Your package, billing period (monthly or yearly), price, billing currency, subscription status and trial end date (access control and billing)
  • Your renewal date, any package change waiting for renewal, and the date a cancellation takes effect
  • Your seats, and which child or student holds each one
  • The last 4 digits of your card, or the fact that you pay with Link
  • Records of each checkout: what you chose, whether it finished, the amount and tax charged, any promotion code used, and the referral ID if you arrived through a partner link
  • Records of payments, refunds and disputes, and the reason and comment you give if you cancel

We never see or store your full card details. You enter them on Stripe's own checkout page, and Stripe, our PCI-compliant payment processor, stores them.

2.6 Automatically Collected Information

When you use our Service, we may automatically collect:

  • Device information (browser type, operating system)
  • IP address (for security and localization)
  • Usage patterns and interactions with the platform
  • Error logs and diagnostic data (for service improvement)
  • Request metadata including IP address, user-agent, request identifiers, and diagnostic correlation IDs (for abuse prevention, debugging, and service reliability)
  • The date and time a parent last used the Service, recorded at most once per session so we can tell an active account from a dormant one and decide whether to message it
  • Product analytics events and session recordings of how our website and app are used, including by children. In recordings, form inputs, children's names, children's details on the parent dashboard, AI tutor conversations and any text a child types are masked before they leave the device. Recordings are deleted after 30 days and analytics events are kept for up to seven years; both are deleted when the account is deleted. None of this is used for advertising. See Section 4.6 and Section 4.7.

2.7 AI Chatbot Assistance Data

When students use the AI chatbot assistant, we collect:

  • Chat messages sent to and received from the chatbot
  • Chatbot session identifiers and conversation history
  • Lesson context (lesson slug, step, language, and school year) sent to the chatbot for relevant responses
  • Response metadata including sources and safety-filtering indicators

Chatbot conversation sessions are held in a temporary cache in our chatbot service for about 15 minutes and then removed. Before a child's message goes anywhere, we check it on our own servers for length, offensive language, email addresses, phone numbers, US social security numbers and attempts to manipulate the assistant; a message that fails these checks is blocked and never sent to any outside service. A message that passes is checked by OpenAI's moderation service for hate, harassment, self-harm, sexual and violent content, and only a message that passes that check too is sent to OpenAI to be answered. The checks do not detect names, home addresses or school names, so please remind your child not to share them. When a message is flagged for safety, for example a sign that a child may be at risk, we keep the message, the tutor's reply and the student's account ID as a safety record for 90 days so our staff can review it, with email addresses and phone numbers removed. When a student uses Report a problem, the note they write and the reply they reported are kept the same way. We keep a record longer only while a safeguarding case about it is open, and we delete these records when the student account is deleted. A serious flag alerts our staff straight away, and they decide whether to contact the parent; the child is encouraged to talk to a grown-up they trust. Chatbot data is used only to help the student learn and to keep them safe, and every reply passes through age-appropriate safety filters before the student sees it.

2.8 Voice Greeting Data

To provide personalized audio greetings, we process:

  • Student first name
  • Language
  • Voice preference selection
  • Generated audio greeting files

Voice greetings are generated through a third-party voice synthesis service (ElevenLabs) and stored on our infrastructure for playback. The audio files are deleted when the student account is deleted.

2.9 Support Ticket Data

When you contact us through our support system, we collect:

  • Email address
  • Message content
  • Language
  • Ticket status (open/closed) and timestamps

Support data is used for responding to your inquiries and follow-up communications. Confirmation and closure emails are sent to the provided email address.

2.10 Virtual Economy Data

Our platform includes a virtual coin economy. We track:

  • Coin balance
  • Coin transaction history (earned, spent, and refunded coins)
  • Virtual item purchases

Each coin transaction is deleted 12 months after it is made. A child's current coin balance and the items they own are kept while the account exists.

2.11 Push Notification Data

We store push subscription data on two separate tracks. On the parent track, when a parent allows notifications in their own browser so we can tell them about their family's progress. On the student track, when a parent has allowed learning reminders and the student then turns notifications on for their device. For each subscribing device we collect and store:

  • The push subscription the browser creates for that device (a unique endpoint address and the encryption keys the browser generates for it)
  • The device's browser user-agent string, to identify the subscribing device
  • Whether the one-time notification reward has already been granted to the student (student track only)

This information exists only to deliver notifications to that specific device. The two tracks are stored separately, so a parent and a student can use the same physical device without one affecting the other. Notification contents are encrypted in transit, and the push delivery services that relay them (see Section 4) cannot read them. The student track is off by default, a parent can withdraw it at any time, and turning notifications off on either track deletes the stored subscription for that device.

2.12 Feedback

We occasionally ask how things are going. Answering is always optional and skipping it changes nothing about the Service. We store:

  • A parent's rating, given by tapping one of a few options in a message we send or a prompt in the app
  • A student's rating of how they are finding their lessons, given by tapping one of three faces in the app
  • The account the rating came from and the date it was given

Neither prompt accepts free text, so a child cannot type anything into it and nothing a child writes is collected here. A parent's rating may be attached to their contact record in our CRM (see Section 4.8) so that support can follow up. A student's rating stays within the Service and is never shared with the CRM or any advertising system. A parent can ask us to delete either at any time under Section 6.

2.13 Sign-in Sessions and Devices

When a child signs in, we store what is needed to keep them signed in and to let a parent see and control it:

  • For each device a child is signed in on, a device label taken from the browser (for example "Windows, Chrome"), when the session started and when it was last used. Parents can see this list.
  • Sign-in requests a child sends to a parent, QR pairing codes, and whether a parent chose to trust a device. Requests and codes expire after two minutes.
  • The daily session length and break length a parent sets, and when the current session or break ends.

3. How We Use Your Information

We use your and your child's information to provide the learning service you signed up for, under our contract with you, and for analytics and service improvement on the basis of our legitimate interests, which you can object to at any time. Specifically, we use it for the following purposes:

3.1 Service Delivery

  • Providing access to educational content and features
  • Personalizing learning experiences based on age and school year
  • Tracking progress and achievements
  • Enabling avatar customization and game features, including the leaderboard and activity feed described in Section 5.3

3.2 Account Management

  • Creating and maintaining user accounts
  • Processing authentication and authorization
  • Managing subscriptions and billing
  • Communicating important account-related information

3.3 Communication

We send messages to parent accounts for the purposes below. These are delivered by email for email-based accounts, and over WhatsApp (with SMS as a fallback) for phone-based accounts. We never send messages of any kind to a student account:

  • Account activation and verification
  • One-time login and verification codes. For phone-based accounts these are delivered over WhatsApp with SMS as a fallback, and message and data rates may apply.
  • Password reset requests (email-based accounts)
  • Password change notifications (email-based accounts)
  • Account deletion confirmations
  • Billing notices: checkout confirmations, receipts, trial reminders, a reminder before each renewal, notices about package changes, failed payments and unfinished checkouts
  • Sign-in requests when your child asks to sign in on a device, delivered in the app, as a push notification, and over WhatsApp for phone-based accounts
  • Messages about getting started and your family's use of the Service, such as a message each day in your first week reporting what your children did, reminders to choose a package if you have not yet, a note when a seat on your package has no child on it, notices before a discount ends, a weekly digest for teacher accounts, prompts to come back after a period of inactivity, and a welcome-back offer after you cancel. These are timed to your local morning and evening and refer to your own children's or students' activity.
  • Progress digests, homework summaries, and product updates

The first seven categories above are transactional and always reach you, because they concern the security, access and billing of your account. The last two are engagement messages. You can turn any category off, and turn off a whole channel (email or WhatsApp), from Communication Preferences in your account settings, and every message carries an unsubscribe route. Turning everything off does not affect the security and billing notices.

3.4 Service Improvement

  • Analyzing usage patterns to improve content and features
  • Identifying and fixing technical issues
  • Developing new educational content

3.5 Security

  • Protecting against unauthorized access
  • Detecting and preventing fraud
  • Enforcing our Terms of Service

3.6 Push Notifications

To a parent, once they allow notifications in their own browser, we may send updates about their family's learning, such as a lesson finished or a badge earned, and requests from a child asking to sign in on a device. To a student, with a parent's opt-in consent and only after the student turns notifications on, we may send occasional reminders that support their learning, such as a nudge to continue a lesson or pick up where they left off.

These notifications are educational or informational in purpose and are not advertising. The student track is off by default, limited in how often it is sent, respects quiet hours, and can be turned off at any time by the parent in Settings or by the student on their device. A parent can turn their own notifications off in their browser's site settings at any time.

3.7 Advertising Measurement

We advertise to adults on Facebook, Instagram and Google. To see whether those adverts work, our website and the parent and teacher pages of our app use the Meta Pixel. The Meta Pixel tells Meta when a visitor views a page, signs up, verifies their account, starts a trial, goes to checkout or subscribes, with the plan price and currency for a purchase. It also reports some button clicks and page details on its own.

Meta may link these events to a Facebook or Instagram account on the same browser and use them to measure and improve the delivery of our adverts. The Meta Pixel is never loaded on pages children use, and we never use it to advertise to children. You can block it with your browser's settings or an ad blocker, and you can manage how Meta uses this data in your Facebook or Instagram ad settings.

4. Third-Party Services

We work with the service providers below to run our platform. Each one handles personal information only to provide its service to us, under its terms with us, which include data protection commitments.

4.1 Stripe (Payment Processing)

  • Purpose: Taking payment on Stripe's hosted checkout page, billing subscriptions, working out tax, issuing invoices, and preventing fraud
  • Data Shared: Your name and email address (where available; phone-only accounts may not have an email, in which case receipts may be issued without one), your account ID, the package, plan, subject and currency you chose, and a referral ID if you arrived through a partner link
  • Data Processed by Stripe: Card details or Link account details, billing address, an optional tax ID for teacher accounts, the result of any 3D Secure check with your bank, and device, browser and IP address information that Stripe Radar uses to detect fraud. You enter card details on Stripe's page, and they never reach our servers.
  • Compliance: PCI DSS Level 1. For Link and for fraud prevention, Stripe also acts as an independent controller under its own privacy policy.
  • Privacy Policy: https://stripe.com/privacy

4.2 Amazon Web Services (AWS)

  • Purpose: File storage and content delivery
  • Data Stored: Avatar images, educational content (videos, audio), badge images
  • Privacy Policy: https://aws.amazon.com/privacy/

4.3 Postmark (Email Service Provider)

  • Purpose: Transactional email delivery (account verification, password reset, deletion confirmation, subscription notices, and support replies)
  • Data Processed: Parent email addresses and the contents of the transactional emails we send to them, which can include a child's first name. Postmark keeps sent messages for about 45 days.
  • Privacy Policy: https://postmarkapp.com/eu-privacy

4.4 Voice Generation Service (ElevenLabs)

  • Purpose: Generating personalized audio greetings for students
  • Data Shared: Student first name, language, and voice preference
  • Data Processed: Text-to-speech synthesis of greeting audio

Generated audio files are stored on our infrastructure. The voice generation service processes the student's first name only for the purpose of creating a personalized greeting.

4.5 AI Tutor (Our Chatbot Service and OpenAI)

  • Purpose: Providing the AI tutor that helps students with their lessons
  • Data Shared with OpenAI: The student's message after it passes our privacy filter, the last few turns of the conversation, the lesson context (lesson, step, language and school year), the child's age band, level and streak, and a random account ID. We never send OpenAI a child's name.
  • Data Processed: Checking messages for safety, finding relevant lesson material, and writing the tutor's replies. Our chatbot service does this on our own servers and uses OpenAI's models for the AI steps.
  • Privacy Policy: https://openai.com/policies/privacy-policy/

Chat sessions are held in a temporary cache for about 15 minutes and then removed. Safety records are kept for 90 days, or longer only while a safeguarding case is open, and are deleted with the student account (see Section 2.7). OpenAI may keep the data it receives for up to 30 days to monitor for abuse and then deletes it, and does not use it to train its models. Every reply passes through age-appropriate safety filters before it reaches the student.

4.6 Sentry (Error Tracking and Performance Monitoring)

  • Purpose: Capturing application errors and performance traces so we can diagnose and fix issues affecting our users
  • Data Shared: Error and exception details, stack traces, browser and device metadata, request identifiers, user role (parent or student), and a random account ID. When a parent or teacher uses a "Report a problem" or feedback form, the text they type and a screenshot of the screen are sent to Sentry with the report. Nothing a student writes is sent to Sentry, and Sentry records no session replays.
  • Data Processed: Error reports and performance metrics, stored in the EU (Germany). We do not send passwords or full personal profiles to Sentry. Reports are deleted automatically after 90 days.
  • Privacy Policy: https://sentry.io/privacy/

4.7 PostHog (Product Analytics and Session Recording)

  • Purpose: Understanding how parents and students use our Service so we can improve features, measure adoption, and operate feature flags
  • Data Shared: A random account ID for each parent and student, linked to a family ID; for parent accounts, the parent's name and email address or phone number; navigation and interaction events, including what you search for in our help centre; device and browser details; an approximate location (country and city) worked out from your IP address; and session recordings. We do not send a child's name or username to PostHog.
  • Data Processed: Product analytics events and session recordings, stored in the EU (Germany). In recordings, form inputs, children's names, children's details on the parent dashboard, AI tutor conversations and any text a child types are masked on the device before anything is sent. Card details are entered on Stripe's checkout page, outside our Service, and are never recorded. Data reaches PostHog through a relay at j.elysianminds.org that PostHog runs on Cloudflare's network in the EU, so Cloudflare handles the data and your IP address in transit.
  • Privacy Policy: https://posthog.com/privacy

PostHog is used only for product analytics and reliability, never for advertising. Session recordings are deleted after 30 days and analytics events are kept for up to seven years. When an account is deleted, we delete its analytics profiles with their events and session recordings (see Section 7.2).

4.8 GoHighLevel (Customer Relationship Management and Message Delivery)

  • Purpose: Managing parent and teacher contacts and account lifecycle, and sending our emails to parent and teacher accounts, such as trial reminders, re-engagement messages and product updates. GoHighLevel does not send our WhatsApp messages or one-time codes; those go through Meta (Section 4.12).
  • Data Shared: Parent or teacher name, email address (if provided), phone number (if provided), country, timezone, account type (parent or teacher), lifecycle status (trial, active, cancelled, etc.), whether a checkout was left unfinished, whether you have chosen a package, whether a seat has no child on it, your message preferences, whether WhatsApp messages can be delivered to your phone number, any one-time discount code we send you, and any rating you give us when we ask how things are going. About your children, the contact record holds only counts, such as how many children are on your account. The messages we send you can name your child by first name and describe their recent activity, so a child's first name appears inside the text of those messages, never as a field on the contact. We do not share student passwords, dates of birth, lesson content, or detailed activity logs with the CRM.
  • Data Processed: Contact records, segmentation tags, support conversations, and outbound email workflows directed to parent accounts only. GoHighLevel sends email through its own email providers (LC Email and Mailgun). The chat widget on our website is also run by GoHighLevel: it collects the name, email address, phone number and message you type into it, and GoHighLevel records your IP address, browser details and the page you came from.
  • Privacy Policy: https://www.gohighlevel.com/privacy-policy

GoHighLevel is never used to communicate directly with children. All marketing and lifecycle communications are sent only to parent accounts. Phone messages, including one-time codes, are sent by us directly over WhatsApp (operated by Meta) with SMS as a fallback, not through GoHighLevel; message and data rates may apply. If you start signing up but never verify your email or phone, only the email or phone number you entered is added to our CRM, so we can help you finish. If your account is deleted, we keep only a minimal contact: your email address or phone number and the tags that mark the account as deleted, with your name, country and every message between us removed (see Section 7.2). We keep it on the basis of our legitimate interest in recognising returning customers and not contacting you by mistake; you can object, or ask us to erase your data, and we will delete it.

4.9 Rewardful (Affiliate Program Management)

  • Purpose: Tracking affiliate referrals, attributing conversions to affiliates, and calculating commissions for our affiliate program
  • Data Shared: When you arrive through a partner's link, Rewardful's script records a referral ID in a cookie on our website and app. We pass that ID to Stripe at checkout, and Rewardful reads the resulting subscription (start date, plan and amount) from Stripe to credit the partner. Personal information about the referred parent is not shared with affiliates beyond aggregate, non-identifying conversion counts.
  • Data Processed: Affiliate dashboards, commission calculations, and referral cookie tracking on the affiliate's promotional links
  • Privacy Policy: https://www.rewardful.com/privacy

4.10 Web Push Delivery Services

  • Purpose: Relaying push notifications to a parent's or a student's device. The delivery service is determined by the browser in use (for example, Apple for Safari, Google for Chrome, Mozilla for Firefox); we do not choose or control it.
  • Data Shared: An encrypted notification addressed to the endpoint that browser provides. Because the notification is encrypted, these services cannot read its contents.

We do not maintain accounts with these services or send them identifying information about parents or students; they act only as the transport layer the browser already uses.

4.11 Google (Sign-In)

  • Purpose: Allowing parents to sign in using their Google account, and to link a Google account to an existing Elysian Minds account
  • Data Shared: When you sign in with or connect Google, we receive your name, email address, and a Google account identifier
  • Data Processed: Verification of your Google sign-in and matching it to your Elysian Minds account
  • Privacy Policy: https://policies.google.com/privacy

4.12 Meta (Facebook Sign-In and WhatsApp Message Delivery)

  • Purpose: Allowing parents to sign in using their Facebook account, and delivering our parent messages to phone-based accounts over WhatsApp. WhatsApp carries one-time login and verification codes, requests from your child to sign in, and account, billing, trial and re-engagement messages, all sent under message templates approved by Meta.
  • Data Shared: When you sign in with Facebook, we receive your name, email address, and a Facebook account identifier. For WhatsApp delivery, your phone number and the contents of the message are processed so it can reach your device. Where a message refers to your family's activity, the values filled into the template (such as a child's first name or a lesson count) are processed with it.
  • Data Processed: Verification of your Facebook sign-in, and transport of our parent messages over WhatsApp with SMS as a fallback. Meta is a delivery channel only and does not use these messages to build a profile of you.
  • Privacy Policy: https://www.facebook.com/privacy/policy/

4.13 Meta Pixel (Advertising Measurement)

  • Purpose: Measuring whether our adverts on Facebook and Instagram lead to sign-ups and purchases (see Section 3.7)
  • Data Shared: The page address, your browser and device details, IP address, Meta's own cookies, the events listed in Section 3.7, including the plan price and currency when you subscribe, and some button clicks and page details the Pixel records on its own
  • Data Processed: Advert measurement and delivery in Meta's systems. Meta may link these events to a Facebook or Instagram account on the same browser.
  • Privacy Policy: https://www.facebook.com/privacy/policy/

The Meta Pixel runs on our website and on the parent and teacher pages of our app only. It is never loaded on pages children use.

4.14 Vercel (Website and App Hosting)

  • Purpose: Hosting and serving our website and our web app
  • Data Processed: Every request to our website and our app passes through Vercel, including the app's requests to our servers. Vercel handles your IP address, browser details and the pages you request in order to serve them.
  • Privacy Policy: https://vercel.com/legal/privacy-policy

4.15 Other Service Providers

We also use these providers, which may handle a limited amount of personal information:

  • Google Workspace: our company email. Anything you write to us by email is held there.
  • YouTube: plays help and walkthrough videos in privacy-enhanced mode. When a video loads, YouTube receives your IP address and device details.
  • Anthropic: provides the AI model behind an internal assistant our staff use. Staff with full access can use it to look into an account, and the parent and child details it reads are then sent to Anthropic to answer the question. Anthropic does not use this data to train its models.
  • Notion: our internal task board. Staff may record the details needed to follow up a support request there, such as a parent's email address or phone number.

5. Children's Privacy (COPPA Compliance)

We take children's privacy very seriously. Our platform is designed with the following protections in compliance with the Children's Online Privacy Protection Act (COPPA):

5.2 Parental Controls and Rights

Parents have full control over their children's accounts and can:

  • View all student activity and progress
  • Activate or deactivate student accounts
  • Change student passwords
  • Delete student accounts at any time
  • See each device a child is signed in on, end any device session, or sign the child out everywhere
  • Turn off the child's password sign-in
  • Approve or deny a child's sign-in request, sign a child in with a QR code, or sign them in from the parent's own device
  • Set a daily session length and a break length
  • Decide when a session ends: children cannot sign themselves out, so a session ends when a parent ends it, when the device limit is reached, or when another child signs in on the same browser
  • Request access to their child's personal information
  • Request deletion of their child's personal information

5.3 Data Minimization

  • We collect only information necessary for educational purposes
  • We do not engage in behavioral advertising to children
  • We do not let children post personal information publicly. The app has a leaderboard and a live activity feed that only signed-in users can see: parents, teachers and students with an account. They show a child's first name, avatar, level and XP, country and school year. The activity feed shows what a child just did, such as finishing a lesson, reaching a new level, keeping a streak or getting a new item. Neither is shown to visitors who are not signed in, and children whose account is paused do not appear. Every child with an active account appears; there is no option to hide a child. We tell you this before you add a child, as part of the consent you give.
  • Children cannot access or change other children's data, apart from seeing the leaderboard and activity feed described below

5.4 No Direct Marketing to Children

We do not send marketing or advertising communications to children. With a parent's opt-in consent, we may send non-marketing educational reminders as push notifications to a student's device; these are off by default and can be turned off at any time. All subscription and marketing communications are sent only to parent accounts.

6. Data Security

We implement robust security measures to protect your information:

6.1 Security Measures

  • All data transmitted between your device and our servers is encrypted
  • Passwords are securely stored using industry-standard hashing algorithms
  • Secure authentication mechanisms to protect your account
  • Protection against brute force attacks and unauthorized access attempts
  • Comprehensive validation to protect against common security threats
  • Strict access controls and session management
  • Data is stored securely with appropriate encryption and access controls

7. Data Retention and Deletion

7.1 Data Retention Periods

Data TypeRequiredPurpose
Parent and Teacher Account DataN/AKept while the account exists
Student AccountsN/AKept while the parent or teacher account that created them exists, and deleted with it. A parent can delete a child's account at any time. The account is then switched off at once and held for 30 days, so it can be brought back with its progress by adding the child again with the same username or by asking our support team, and after that it is deleted for good.
Activity and Coin HistoryN/AEach entry, such as a lesson finished, a level reached, a streak kept or coins earned or spent, is deleted 12 months after it is recorded. A child's current progress, level, XP and coin balance are kept while the account exists.
Unverified Parent AccountsN/AAutomatically deleted after 90 days if the account's email or phone number is never verified. The matching contact in our CRM (Section 4.8) is kept, without your account data.
Dormant AccountsN/AIf an account has had no sign-in and no subscription for 24 months, we send a notice 30 days before deleting it. If nobody signs in by then, we delete the account and its children's accounts as described in Section 7.2.
Student Sign-in Sessions and Device RecordsN/AKept while the session is active; deleted when a parent ends it or it is replaced, and in any case when the student account is deleted. Sign-in requests and pairing codes expire after two minutes.
AI Tutor Safety RecordsN/AKept for 90 days, longer only while a safeguarding case about the record is open, and deleted when the student account is deleted (Section 2.7)
Product AnalyticsN/ASession recordings are deleted after 30 days. Analytics events are kept for up to seven years, the retention our analytics provider applies, and are deleted when the account they belong to is deleted.
Server LogsN/AOur server logs, which include IP addresses and account IDs, are deleted automatically within 12 months
Database BackupsN/ADeleted data can remain in our encrypted database backups for up to 7 days before the backups are overwritten
Payment and Refund RecordsN/AKept for seven years after the end of the tax period they belong to, as UAE tax law requires, including after the account is deleted. Stripe keeps its own records under its privacy policy.

7.2 Account Deletion

Parent Account Deletion:

  • You can request account deletion through your account settings
  • A confirmation with a verification link or code is sent to the account's registered channel (by email for email-based accounts, or over WhatsApp with SMS as a fallback for phone-based accounts)
  • The deletion verification link is valid for 1 hour
  • One-time verification codes used during account actions expire after 5 minutes
  • Once you confirm, we delete your account and your children's accounts. The only data we keep is listed under "What We Keep" below

What We Delete:

  • Parent profile data
  • All associated student accounts and profiles
  • All lesson progress, activity history and achievements
  • Avatar configurations and inventory
  • Your children's voice greeting audio files
  • Your children's AI tutor safety records
  • The product analytics of you and your children: your analytics profiles with their events and session recordings
  • Your subscription is cancelled and your customer record at Stripe is deleted

What We Keep:

  • Our server logs, until they are deleted on their 12-month schedule (Section 7.1)
  • A minimal contact in our CRM, GoHighLevel (Section 4.8): your email address or phone number and the tags that mark the account as deleted. We remove your name, country and every message between us. We keep it so we recognise you if you come back and so we do not contact you by mistake, and we delete it if you ask us to erase your data.
  • Payment and refund records, for as long as the law requires (Section 7.1)
  • Copies our service providers hold until their own retention period ends: error reports in Sentry (90 days), sent emails at Postmark (about 45 days), and messages delivered through WhatsApp, which Meta may keep for up to 30 days.

8. Your Rights

Depending on your location, you may have certain rights regarding your personal information:

8.1 Access and Portability

You have the right to ask for a copy of the personal information we hold about you and your children. Contact our support team and we will send it to you as a data file.

8.2 Correction

You can update your account information at any time through your account settings, or contact us to request corrections.

8.3 Deletion

You can delete your account and your children's accounts as described in Section 7.2. If you also want us to delete your contact in our CRM, ask our support team to erase your data and we will delete it.

8.4 Objection and Restriction

You may object to certain processing of your data or request that we restrict processing in certain circumstances.

8.5 Exercising Your Rights

To exercise any of these rights, please contact us at support@elysianminds.org. We will respond to your request within 1 week.

9. International Data Transfers

We are based in the Dubai International Financial Centre (DIFC). We store the personal information in our own systems on Amazon Web Services in the European Union (Ireland). Our product analytics (PostHog) and error tracking (Sentry) are hosted in the EU (Germany).

Some of our service providers process personal information in the United States or in other countries: Stripe, OpenAI, GoHighLevel and its email providers, Postmark, ElevenLabs, Rewardful, Meta (Facebook sign-in, WhatsApp and the Meta Pixel), Google (sign-in, Workspace and YouTube), Anthropic and Notion. Vercel serves our website and app from its global network, from the location nearest you, and runs our server-rendered pages in the United States (Washington, D.C.). WhatsApp messages are processed by Meta in its data centres, mainly in the United States. Cloudflare relays analytics data through its EU network on its way to PostHog.

DIFC law recognises the United Kingdom and the European Union as giving personal information adequate protection, so what we keep in Ireland and Germany needs no further safeguard. For providers in the United States and other countries, we rely on the data protection terms in our agreements with them, including standard contractual clauses where the provider offers them.

You can ask us for more information about these safeguards using the contact details in Section 13.

10. Cookies and Tracking Technologies

We use essential cookies and similar technologies to operate our Service. Parent and teacher accounts sign in with token-based (JWT) authentication. Student accounts sign in with a secure, HttpOnly session cookie that our servers set and that the app cannot read. On our website and the parent and teacher pages of our app we also use analytics, advertising and referral cookies. These include:

  • Authentication Tokens and Session Cookies: JWT tokens for parent accounts, and a first-party HttpOnly session cookie plus a device cookie for student accounts, which keep each child signed in on that browser
  • Request Protection Cookies: A CSRF token cookie that protects your requests from forgery, and essential cookies for administrative interfaces
  • Preference Cookies: To remember your timezone and theme settings
  • Security Cookies: To prevent fraud and protect against unauthorized access
  • Device Storage: This browser keeps, in local storage, the username, first name, avatar and family reference of children who signed in on it, so they can tap their picture to switch. It holds one family at a time. It also keeps the name and email or phone of the last parent who signed in, so that parent can sign back in with a password or code. This stays on the device and is cleared when a parent signs out.
  • Analytics Cookies: PostHog sets a first-party cookie holding a random ID so we can count visits and record sessions, with form inputs, children's names and text children type masked
  • Advertising Cookies: The Meta Pixel sets cookies (such as _fbp) and reads Meta's own cookies so we can measure our adverts on Facebook and Instagram, as described in Section 3.7
  • Referral Cookies: When you arrive through a partner's link, Rewardful sets a cookie that records the referral so the partner can be credited

We use the Meta Pixel to measure our adverts to adults, as described in Section 3.7. It is never loaded on pages children use, and we never use cookies or any other tracking technology to advertise to children. Our product analytics, including event tracking and session recording with form inputs, children's names and text children type masked, are used only to understand and improve the Service. These technologies are described in Section 4 (Third-Party Services).

11. Guest Mode

You can try a limited set of sample lessons in guest mode without creating an account. This section explains what we do and do not collect when you use guest mode.

What we do not collect

  • We do not ask for or collect account information from guests, such as your name, email address, username, or password.
  • We do not save your guest lesson activity, answers, or progress to an account. Guest session state stays in your browser during the visit and is not stored on our servers.
  • We do not collect payment information in guest mode.

What we do collect

  • We collect anonymous product analytics about how guest mode is used, for example which lessons are tried, how far visitors get, and where they choose to sign up, so we can understand and improve the Service.
  • This analytics data is handled by our analytics provider (PostHog) and is linked to an anonymous identifier, such as a cookie or device identifier, rather than to your real-world identity.
  • As described in Section 4 (Third-Party Services) and Section 10 (Cookies and Tracking Technologies), analytics may use cookies and may include session recordings in which text you type is masked.

If you later create an account, the information you provide at sign-up is governed by the rest of this Privacy Policy.

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We post every change on this page and update the "Last Updated" date. When a change is material, for example a new purpose, a new kind of data or a new provider that receives your data, we also tell you by email, or by WhatsApp for a phone-based account, no later than when it takes effect.

For material changes that affect how we process children's personal information, we will provide additional notice and obtain parental consent where required.

We encourage you to review this Privacy Policy periodically for any changes. Your continued use of the Service after changes are posted constitutes acceptance of the updated Privacy Policy.

13. Contact Information

If you have questions, concerns or requests about this Privacy Policy or how we handle personal information, contact us using the details below. Elysian Minds Innovations Limited is the controller of the personal information this policy describes.

Elysian Minds Innovations Limited

Innovation 1, DIFC, Dubai, UAE

Email: support@elysianminds.org

For concerns about children's privacy or to exercise parental rights, please use the email above with "Children's Privacy" in the subject line.