alai Privacy Policy
Last updated: November 4, 2026 · Version: 2026-11-04
Joining the waitlist
When you join the waitlist, we keep your chosen contact (email address or phone number), signup time, and a record that you asked for early access and launch updates in our waitlist database (Convex). Phone signup requires your agreement to launch texts; message and data rates may apply. Joining does not create an alai account. We use a short-lived counter keyed by a hash of your IP address to limit signup abuse; it expires after 20 minutes. Waitlist entries are kept until you ask us to remove them. To leave the waitlist or request deletion, email support@tryalai.app. The waitlist is for people 13 and older.
This policy explains what information alai collects, what we do with it, who helps us process it, how long we keep it, and what you can do about it. "We" and "us" means Aiden Guan and Allen Hsieh, the alai team. alai is a note-taking app with a live handwriting tutor, Ally, at tryalai.app and in our iPad app.
The short version
- We collect what we need to run alai: your email, your notes and handwriting, what you ask Ally, basic usage and error information, and, if you buy a plan, the plan and whether it's paid.
- To read your handwriting and talk with you, Ally sends your work to Anthropic (the AI), your voice to Inworld (speech to text, with ElevenLabs and Deepgram as backups), and the text of Ally's replies to Inworld (Ally's voice). We list every company that handles your data below.
- We don't sell your data, we don't show ads, and we don't use your content to train AI models. Our AI providers don't either, under the terms we use them on. Ally does learn from your own work to help you, with your name and email left out, and that stays with your account.
- We don't store the page snapshots Ally checks, or recordings of your voice. They are processed and then dropped.
- If you buy a plan, Stripe takes the payment. You give your card and billing details to Stripe, not to us: we never see your card number, and we keep only your plan and Stripe's reference numbers for it.
- Your work (handwriting, notes, images, PDFs) is saved on your device. When you're signed in, it's also copied to your account so it follows you between devices.
- You can download or delete your data from the Account page at any time, back it up on the iPad to a folder of your own (such as iCloud Drive, Google Drive, Dropbox or OneDrive), or ask us for a copy, a correction or deletion: support@tryalai.app.
- Anyone 13 or older can use alai. A child under 13 can use it only after a parent or guardian agrees (section 8).
1. What we collect
Information you give us
| What | Details | Where it's kept |
|---|---|---|
| Account | Your email address (you sign in with Apple or Google, a one-time code we email you, or a password you choose), the display name you choose, your age range (we ask your age only to work out the range, and keep only the range), and your profile picture choice (one of Ally's built-in pictures; no photo uploads). If you continue with Apple or Google, they tell us your email address (with Apple, it can be a private relay address) and an account ID; Google may also send your name and profile picture address. We also keep a record of when you agreed to our terms, this policy and sending your work to Ally's AI, and which version you agreed to. | Our database (Supabase) |
| Billing, if you buy a plan | On Stripe's own page, you give Stripe your name, billing address and card (or other payment method). We give Stripe your email address and an internal account ID, so the payment matches your account. Stripe tells us which plan you chose, how many learners it covers, whether it's paid, and when it renews or ends. | Stripe keeps your payment details; we never see your card number. Our database (Supabase) keeps only the Stripe customer and subscription IDs, the plan, its status, the number of learners, and when it renews or ends. Nothing about a child is ever sent to Stripe. |
| Your notes and handwriting | Pen strokes, typed text boxes, images you add, PDFs you import, paper style, homework boards, and class recordings you make in a note. | On your device, and copied to our database and file storage when you're signed in so it follows you between devices. The pictures, PDFs and handwriting files in our file storage are also copied every night to a backup with Cloudflare. Class recordings stay on the device they were made on. |
| Your library | Folder names, file titles, the subject Ally works out a file is about, and how they're arranged. | On your device, and copied to our database when you're signed in so it follows you between devices |
| Settings | Theme, light or dark mode, whether Ally speaks aloud, whether a finger can draw, and sorting prompts. | On your device and in our database when signed in |
| What you ask Ally | Questions you type or say, what you say aloud while you work with Just talk on, problems you add by writing, speaking or photographing them, worksheet photos, and lesson topics you ask for. | Sent to our servers and AI providers to get Ally's answer (see section 3). The conversation is kept on your device for the session. |
| Your voice | While you hold the talk button, while Just talk is on (it listens while you work with Ally, and turns itself off after 2 minutes with no words), or when you add a problem by voice. | Not stored by us. The audio goes to Inworld (or to ElevenLabs or Deepgram, our backups when Inworld fails or is slow) to be turned into text, and the text comes back to you. Live speech (Hold to talk as you speak, and Just talk) streams from your device straight to Inworld or ElevenLabs. Ally's spoken replies are made by Inworld from the text of the reply. |
| Messages to us | Anything you email us. | Our email |
| Feedback from the app | What you write in a bug report or feedback, up to three pictures of your screen if you choose to add them, and the app's build, your device model, its system version, the window size and which screen you sent it from. If you test the alai app through TestFlight, Apple passes us the feedback, screenshots and crash reports you send there. If you let your device share crash data with app developers, Apple also passes us the alai app's crash reports. In a test copy of the iPad app (TestFlight), when a note's page stops answering touches, the app sends us a short bug report by itself: what was open over the page, the page's settings, and the last few things the app did (tools picked, menus opened, leaving and coming back), never what you wrote, typed or said and never a picture; at most three a day. | Our database, our team chat (Slack) and a private issue in our code repository (GitHub, your words only, never the picture). Deleted when you delete your account. Feedback sent through TestFlight, with its screenshots and crash logs, stays with Apple and also reaches our team chat (its words and any crash log reach a private issue too); it isn't linked to your alai account, so email us to have it deleted. |
Information created as you use alai
| What | Details | Where it's kept |
|---|---|---|
| Page snapshots | While Ally is watching, the app sends images of your page (and a close-up of your newest writing) for Ally to check. Notes pages may also be sent so search can find the words in them. | Not stored by us. Held in memory for the length of the request, then dropped. The text Ally reads back for search stays on your device. |
| Short-term session memory | For each tutoring session: the last hint Ally gave, the code for any open mistake, whether the problem is solved, a simplified copy of the last line you wrote (so Ally doesn't repeat herself), which kind of hint is being tried, which account and learner the session is for, your device's time zone, and whether you're on the web or the app. | Upstash Redis, deleted automatically 6 hours after your last check (which account and learner it's for: 12 hours after the session starts) |
| Learning history | Events such as "problem started", "mistake seen" (a short code, like a sign error), "hint shown" (that Ally gave a hint, not its words), "fixed it", "solved", the method you used (e.g. "factoring"), the topic, and the hint style that helped. Used so Ally remembers what helps you next time. Never handwriting, transcripts or images. | Our database, with your account |
| Learner model | A summary of how you're doing per topic and which mistakes recur. Never handwriting, transcripts or images. | Our database, when this feature is on |
| What Ally knows | Short facts about you, like your classes and goals: ones you type, and ones Ally suggests from your notes or from another assistant's memory you paste in. Ally uses only the ones you keep. Suggestions you turn down are remembered so Ally doesn't suggest them again. | On your device, and copied to our database when you're signed in so it follows you between devices |
| Usage counts | Per day: sessions, minutes, checks, questions, problems and notes pages. To hold each plan's time with Ally: how many minutes of Ally each learner used each month, and in all. Counts only, never content. | On your device, and our database when signed in (Ally's minutes are kept only in our database) |
| Technical information | Your IP address (seen by our hosting provider and used, as a one-way hash, for rate limits); browser and device type; request times, status codes, costs and IDs in our server logs. | Vercel logs; Upstash for rate limits (minutes to 2 days) |
| Error reports | When something crashes: the error, where in the code it happened, browser and OS type, and the page address without its query string. Our error reports are set up to strip out your notes, what you said or typed, request contents, cookies, IP address and account details. | Sentry |
| Visit and product analytics | Visit counts with no cookies: the page, the site you came from (its domain), your country and your device and browser type. In the app, only for learners 13 and over: which pages you open and when you leave them, and a few steps as codes: starting sign-up (and how), making your first profile (an age range, and whether it's for you or a child), each welcome screen you reach, finishing the welcome (with the answers you picked there, as codes: your role, subjects, goals, where you take notes now and how you heard about alai), how many notes came in when you brought them from another app in the welcome (counts only, never their names), Ally checking your work (the mode and the result), seeing an upgrade message (which feature) or the plans, starting, finishing or cancelling a checkout (the plan and whether it's monthly or yearly), and how many days since your last visit. Steps taken before we know the learner's age range wait on the device and are sent only once we know it. These never run for a learner under 13, nor on the home and waitlist pages of a device an under-13 learner uses. Visitors in the EU, the EEA, the UK and Switzerland are asked first: PostHog runs on the home and waitlist pages, and in the app for learners 13 and over, only after you tap Accept on the cookie banner. One answer holds for both in that browser, and if you tap No thanks it stays off. A learner under 13 is never asked, because PostHog never runs for them. Visit counts with no cookies still run. In the app there are no session recordings and no record of what you click or type. On the home and waitlist pages: clicks, where on the page people click and scroll, page speed, campaign tags and ad click IDs in the link you came from (like utm_source, gclid or fbclid), and session recordings of the page, with everything typed hidden and the waitlist form left out entirely. Everywhere: browser and device type, and your country (worked out from your IP address, which PostHog then discards). Page addresses are cut to their path, so codes and searches in them are never sent (campaign tags are kept on their own). When you're signed in, these are tied to your account by an internal ID, never your name or email. Never your notes, handwriting, voice or anything you write. | Vercel Web Analytics; PostHog |
| Cookies and local storage | Your sign-in session; your work and settings on the device; a copy of the app's pages, so it opens with no connection; where PostHog runs, a random analytics ID, so visits from the same browser count once, and on a device an under-13 learner uses, a note that keeps PostHog off; and if you were asked about cookies, your answer, so you're asked only once. No advertising or cross-site tracking cookies. Stripe's checkout and Manage plan pages are on Stripe's own site and use Stripe's cookies, under its privacy policy. | Your browser |
We don't collect your precise location, contacts, or photos you haven't chosen to add. Your card details go to Stripe, never to us.
2. How we use it
- To run alai: save and sync your work, sign you in, let Ally read your handwriting, answer your questions, speak aloud, find words in your notes, and sort your files.
- To personalise tutoring: Ally uses your learning history and learner model to choose hints that have helped you before.
- To keep alai working and safe: fix bugs, prevent abuse, enforce daily usage limits, and control costs.
- To improve alai: understand which features get used (counts and learning events, not the content of your work), and read feedback you send. When we look at totals across learners, we leave out any group smaller than 10 people, so no one can be picked out.
- To bill you for a plan you buy: to start, renew, change or end it, to show it in the app, to remind you before a yearly plan renews (Stripe sends that email), and to keep the records tax and accounting law requires.
- To contact you about your account and your plan, changes to these policies, or if alai shuts down.
- To follow the law and protect our users and ourselves.
We don't use your information for advertising, we don't build profiles of you for anything other than tutoring you, and we don't sell it or share it for cross-context behavioural advertising.
3. Who processes your data
We use these companies (our "service providers") to run alai. They may use your data only to provide their service to us.
| Provider | What they do for us | What they receive |
|---|---|---|
| Anthropic (Claude) | The AI behind Ally: reads handwriting, checks steps, replies, reads worksheets, plans lessons, reads notes for search, makes study tools (summaries, cards and quizzes) from your notes, turns handwriting you select into typed text, suggests folders and facts for What Ally knows, and checks what you say or write for signs you might want to hurt yourself, so Ally can point you to help | Page and handwriting images, worksheet photos, notes pages, the text of your questions (typed or transcribed), recent conversation with Ally, the problem you're working on, your folder names (for sorting), lesson topics, the text of your notes (for study tools and What Ally knows suggestions), any memory from another assistant you paste in, the facts you keep in What Ally knows, and a summary of your learning profile |
| ElevenLabs | Live speech to text (with Inworld), and a backup for speech to text and Ally's voice when Inworld fails or is slow | Audio recorded while you talk to Ally; the text of Ally's replies, when it stands in for Inworld |
| Deepgram | Speech to text and Ally's voice, as our last backup when ElevenLabs or Inworld fails or is slow | Audio recorded while you talk to Ally; the text of Ally's replies |
| Inworld | Speech to text (your voice, including live speech streamed from your device) and text to speech (Ally's spoken voice) | Audio recorded while you talk to Ally; the text of Ally's replies, to read aloud, which can mention what you wrote or asked. Never your pages or your account details |
| Convex | Waitlist database | Your chosen signup contact (email or phone), signup time, and launch-update consent |
| Supabase | Database, file storage and sign-in | Your account, library, settings, usage counts, what Ally knows, learning history and learner model; your notes and homework boards, with the pictures and PDFs in them, when you're signed in; sign-in emails and one-time codes; a one-way hash of your password, if you set one; your plan and Stripe's reference numbers for it |
| Postmark | Sends sign-in emails, and the notice a parent gets when their child asks to use alai | Your email address and the one-time code in it; for the parent notice, the parent's email address and the notice, with delivery records (sent, delivered or bounced) |
| Stripe | Takes payment for paid plans: the checkout page, renewals, and the Manage plan page where you change or cancel a plan; and runs the card check a parent passes before a child under 13 can use alai | About the adult who pays (a parent or guardian, for a child's plan): their email address and an internal account ID, from us; the name, billing address and card details they enter on Stripe's own pages, which we never see; and the plan's payment records, and the card check's payment and refund records. Nothing about a child. Stripe also uses payment details to prevent fraud and to meet its own legal duties, under its own privacy policy |
| Vercel | Hosts the website and servers | All requests pass through it; it keeps server logs (IP addresses, request IDs, timing, status) and counts visits with Web Analytics (page, referring domain, country, device type; no cookies) |
| PostHog | Product and marketing analytics: how the app is used and which campaigns bring people, so we know what to fix | Pages opened and left, with addresses cut to their path; the app steps listed in section 1, as codes; on the home and waitlist pages only, clicks, campaign tags and recordings with typing hidden; browser and device type; IP address, used to work out your country and then discarded; a random ID, and an internal account ID when signed in. Never names, emails, recordings of the app, or your work, and nothing at all from a learner under 13 |
| Upstash | Short-term memory and rate limits | Session memory (up to 12 hours), hashed device, network or account IDs with request and cost counters; a scrambled copy of a parent's email address for a day, so the same address isn't emailed again and again |
| Sentry | Error reports | Scrubbed error reports (see section 1) |
| Cloudflare | Domain name (DNS) for tryalai.app, and the nightly backup of our file storage (Cloudflare R2) | Standard DNS lookups; backup copies of the pictures, PDFs and handwriting files in your notes when you're signed in |
| Zoho Mail | Team email | Emails you send to an @tryalai.app address, and our replies |
| Apple and Google | Sign in with Apple or Google, if you choose it; for our apps, the App Store and TestFlight | That you're signing in to alai. They send us back your email address and an account ID. TestFlight testers' email addresses are matched to our invite list |
| Slack | Our team chat, where feedback and bug reports reach us | Your feedback's words, the app's build and your device type, and any screen picture you added (pictures sent in the app only from adults who don't look after or teach a minor), and the words, screenshots and crash logs of feedback sent through TestFlight, under a made-up tester tag, never your name or email; never anything you didn't send as feedback, except a test copy's report of a page that stopped answering touches |
| GitHub | Where we track bugs to fix | The words of your feedback, the app's build and your device type, under a made-up tester tag, in a private issue only our team can see; never your screen picture, name or email; for TestFlight feedback, its crash log too, and a test copy's report of a page that stopped answering touches. For TestFlight testers, an hourly job on GitHub matches their email addresses to our invite list |
| Microsoft | Only if you import notes from OneNote | You sign in to Microsoft in your browser and your browser fetches your notes from it directly. Your Microsoft sign-in and the OneNote pages never pass through our servers |
Backups you turn on
On the iPad, you can choose to have alai keep a copy of your work in a folder of your own, in iCloud Drive or another storage app on the iPad, such as Google Drive, Dropbox or OneDrive. It's off until you turn it on. The copy is the same as "Download everything": your notes as PDFs, the pictures and PDFs you added, your homework, your learning history and what Ally knows about you. alai updates it now and then while backups are on.
- The copy goes from your iPad straight into alai's own folder in your iCloud Drive ("Back up to iCloud"), or into a folder you pick in the Files app. alai never sees your password for that service, and can reach only that folder, not your other files. The copy uses your storage with that service, not alai's.
- That service isn't one of our service providers: you choose it, and the account is yours. Once a copy is there, the service's own terms and privacy policy cover it, not this policy.
- Turn backups off in Settings on the iPad at any time. alai then stops adding to the copy. It doesn't delete a copy that's already been made, and neither does deleting your alai account: you can delete it in that service.
- Backups aren't available for children under 13 yet. When they are, a parent will allow them as a separate choice, when they agree to their child using alai (section 8).
We may also share information if the law requires it, to protect someone's safety, to investigate abuse, or as part of a merger or sale of alai (we'd tell you first, and this policy would still apply to your data).
4. Does my data train AI models?
No. We don't use your content to train AI models, and we've set up our providers so they don't either:
- Anthropic: we use Claude through Anthropic's commercial API. Anthropic's Commercial Terms state that "Anthropic may not train models on Customer Content from Services."
- Deepgram: every request we send to Deepgram (speech to text and text to speech) opts out of Deepgram's Model Improvement Program, so Deepgram doesn't keep your audio or text to improve its models.
- ElevenLabs: turns your voice into text during live speech (alongside Inworld), and stands in for Inworld, turning your voice into text and Ally's replies into speech, when it can't. We don't store the audio, but ElevenLabs may keep it for a time under its own privacy policy. Our ElevenLabs account is set so that ElevenLabs doesn't use your audio or text to train or improve its models.
- Inworld: turns your voice into text and Ally's replies into speech. We don't store the audio, but Inworld may keep it, and the text of Ally's replies, for a time under its own privacy policy. Inworld says it never uses the audio it turns into text for training, and its terms of service say it doesn't use the non-public material customers send it to train its models.
Ally learns from your own work, for you. Ally uses your past work, your conversations with Ally and your learning history to tailor its help to you: the hints that have worked for you, what you've already covered, and where you tend to slip. Your name and email are left out of what Ally uses. This stays with your account: it isn't used to help other students or to train AI models, and you can clear it at any time with Reset Ally's memory on the What Ally knows page.
If we ever want to use real student work to improve Ally (for example, to test how well Ally reads handwriting), we'll ask you first, separately, and only use work you choose to share.
5. How long we keep it
| Data | How long |
|---|---|
| Page snapshots sent to Ally | Not stored by us; dropped when the request ends |
| Your voice recordings | Not stored by us; Inworld or ElevenLabs (or Deepgram, when it stands in) may keep them for a time under its own privacy policy |
| The text of Ally's replies, sent to be spoken | Not stored by us; Inworld (or ElevenLabs or Deepgram, when they stand in) may keep it for a time under its own privacy policy |
| Copies held by Anthropic | Anthropic deletes API inputs and outputs within 30 days by default; content its safety systems flag may be kept up to 2 years |
| Session memory (Upstash) | 6 hours after the last check (the account and learner: 12 hours after the session starts) |
| Rate-limit counters | From 2 minutes (per-minute limits) to 2 days (daily limits) |
| Account, library, settings, usage counts | Until you delete them or your account |
| A child's profile (under 13) and everything in it | Until a parent deletes it, or 12 months after anything in it was last opened, made or changed, when we delete it. A record of the parent's consent stays, without the child's name, age or work |
| Your plan and Stripe's reference numbers for it, in our database | Until you delete your account |
| Billing records at Stripe (your Stripe customer record, invoices and payments) | Deleting your account deletes your Stripe customer record, so no card stays saved. Invoices and payments are kept by Stripe after a plan ends or you delete your account, for our tax and accounting records and Stripe's own legal duties, as long as the law requires |
| What Ally knows, learner model | Until you delete them, reset Ally's memory (on the What Ally knows page), or delete your account |
| Files you delete | Moved to Recently deleted, where you can bring them back for 30 days. They still count toward your storage there. After 30 days, they're removed from our database along with their version history. Delete for good, inside Recently deleted, removes a file straight away, with its backup copies and the pictures and PDFs no other file of yours uses. Deleting a folder moves what's in it up a level. Earlier versions of any file are kept for 30 days. Pictures and PDFs from other deleted files are removed from our file storage after that, unless another file of yours still uses them. |
| Backup copies of your files (Cloudflare) | Copied every night. A copy is deleted when its file leaves our file storage, and when you delete your account or a child profile. |
| Conversations with Ally (if we start saving them to your account) | Until you reset Ally's memory or delete your account, so Ally can remember what you've worked on together |
| Learning history | Until you reset Ally's memory or delete your account |
| Server logs (Vercel) | Up to 30 days, as long as Vercel keeps them under our plan |
| Error reports (Sentry) | Up to 90 days |
| Analytics (Vercel Web Analytics, PostHog) | As long as each provider keeps it under our plan |
| Work stored on your device | Until you delete it, erase the device's data from the Account page, clear your browser data, or delete the alai app |
| Emails with us | As long as needed to help you, then deleted |
| Feedback and bug reports | Until we've dealt with them, and no longer than your account; deleted when you delete your account |
| Waitlist sign-ups | Until you ask us to remove you |
When you delete your account, we delete your data from our database within 30 days. Database backups roll off within 30 days after that. The backup copies of your files are deleted along with your account. Deleting your account also cancels any paid plan straight away and deletes your customer record at Stripe, so no card stays saved; Stripe keeps its invoices and payment records for our books.
6. Security
- Your connection to alai is encrypted (HTTPS), and our database and hosting providers encrypt the data they store.
- Our database uses row-level security: each account can only reach its own rows, enforced by the database itself, not just the app.
- You sign in with Apple or Google, a one-time code sent to your email, or a password. If you choose a password, our sign-in provider keeps only a one-way hash of it, so nobody at alai can read it.
- Server keys are never sent to your browser. Snapshots and voice aren't stored, which means there's less to lose.
- Card details go straight to Stripe, which is certified to the card industry's security standard (PCI DSS). They never reach our servers.
- Our logs and error reports are designed never to include your notes, handwriting, voice or what you said.
No system is perfectly secure. If a breach affects your personal information, we'll tell you without unreasonable delay and as the law requires.
7. Your choices and rights
You can:
- See and get a copy of your data. Save any notes page as a PDF, or download all your files, what Ally knows, your practice queue and your learning history from the Account page on the web or Settings in the iPad app ("Download everything"). For anything else, or if that doesn't work for you, email us.
- Correct your name, age range and settings in the app, or ask us to fix anything else.
- Delete your data. Clear what Ally knows and has learned about you, on every device, from the What Ally knows page ("Reset Ally's memory"). Erase what's on a device from the Account page ("Erase everything on this device"). Delete your account and our server copies from the Account page too ("Delete my account"); in the iPad app, both are in Settings. If that doesn't work for you, email us from your account's address.
- Turn off Ally's voice in Settings. Ally only listens while you hold the talk button, while Just talk is on (it turns itself off after 2 minutes with no words), or when you add a problem by voice.
- Cancel or change a paid plan at any time with Manage plan, and update your billing details there (the Terms, section 10).
- Stop using alai at any time.
Email support@tryalai.app. We'll confirm the request comes from your account's email, and respond within 30 days. We won't treat you differently for using these rights.
California residents
If you live in California, the California Consumer Privacy Act (CCPA) gives you the right to know what personal information we collect, use and disclose; to delete it; to correct it; and to opt out of its sale or sharing; and to not be discriminated against for exercising these rights. We give these rights to every user, wherever you live.
- Categories we collect (CCPA terms): identifiers (email, random IDs, IP address); customer records (name, email, and for a paid plan, the billing address and card details Stripe holds for us); commercial information (the plan you bought and its payment history); characteristics (age range); internet activity (usage counts, logs); audio information (your voice while you talk to Ally, not stored); inferences (learning profile: which topics and hint styles suit you); and the content of your notes and messages to Ally.
- Sources: you, your device, and our service providers.
- Purposes and recipients: sections 2 and 3.
- Sale and sharing: we have not sold or shared (for cross-context advertising) personal information, and we won't. We don't knowingly sell or share the data of anyone under 16.
- Sensitive personal information: we use your account sign-in only to sign you in, and card details (held by Stripe) only to take payment for your plan. We don't use any sensitive information to infer characteristics about you.
- Global Privacy Control: we don't sell or share, so there's nothing to opt out of, but if your browser sends the signal, PostHog analytics stay off for it, on our pages and in the app.
- Authorised agents may make requests for you with your written permission; we may ask you to confirm.
8. Children
A child under 13 can use alai only after a parent or guardian agrees. The child gives us a parent's email address, which we use once to send the parent the notice below. We don't keep it, apart from a scrambled copy for one day so the same address isn't emailed again and again. We collect nothing else from the child until the parent signs in at tryalai.app/parent, agrees, and passes a card check. Parents look after their children's profiles on that page. This is what we tell a parent before they agree:
What we collect about your child, once you agree
- The first name and age you give us. We never ask for a birth date, an email address or a photo of your child.
- Their work in alai: handwriting, typed notes, pictures and PDFs they add, homework boards and the problems on them.
- What they say to Ally, typed or spoken, and Ally's replies. Spoken words are turned into text; we don't store the audio. Recordings made with a note stay on the device they were made on and are never sent to us.
- Their learning history (which problems they tried, the hints they used, what they solved) and short notes Ally keeps about how they like to learn. You can clear these with Reset Ally's memory in alai's settings while your child's profile is allowed, or by deleting the profile.
- Usage counts, such as how many sessions they have had, so we can keep within daily limits.
How Ally uses it
Ally learns from your child's own work, for your child: it uses their past work, their conversations with Ally and their learning history to tailor its help to them, such as the hints that have worked and where they tend to slip. Their name is left out of what Ally uses. It stays with your child's profile: it isn't used to help other students or to train AI models.
What we never do
- No advertising, and we never sell or rent your child's information.
- No analytics or tracking for children: product analytics never run for a learner under 13.
- Your child can't publish anything or message other people in alai.
- The companies below may not use your child's work or voice to train their AI models.
Who receives it, and why
- Anthropic (Claude), to read your child's work and write Ally's replies. Anthropic deletes these within 30 days, except content its safety systems flag, which may be kept up to 2 years.
- Inworld, to turn your child's speech into text and Ally's replies into speech. We don't store the audio.
- ElevenLabs, for live conversation and to stand in when Inworld is down, and Deepgram as a last backup. Both turn speech into text and Ally's replies into speech.
- Supabase, which stores the account and your child's work, and Vercel, which runs the app.
- Cloudflare, which keeps a nightly backup copy of the pictures, PDFs and handwriting files in your child's notes, deleted when the files are.
- Upstash, which holds short-lived notes about the current tutoring session (the last hint, a simplified copy of the last line written, which kinds of hints are working, and the account's ids) for up to 12 hours.
- Sentry, which receives error reports when something crashes, with your child's work, words and account details stripped out.
- Postmark sends our emails to you, and Stripe runs the card check. Neither receives anything about your child.
Backups to a cloud service
alai doesn't back up a child's work to iCloud Drive, Google Drive, Dropbox, OneDrive or any other cloud service. You can download all of your child's work at any time (below).
If your iPad backs itself up to iCloud, that backup includes alai's files on the iPad. That's an iPad setting under your Apple account, not something alai controls.
How long we keep it
Your child's work, their learning history and Ally's notes about them are kept until you delete them, delete your child's profile, or delete your account.
Files you delete stay in Recently deleted for 30 days, then are removed. Deleting your child's profile removes it right away. Copies in our database backups are gone within about 30 days after that.
If your child's profile isn't used for 12 months (nothing in it is opened, made or changed), we delete it and everything in it, as if you had deleted it.
When a child's profile is deleted, we keep only a record of your consent: your login, when you agreed or withdrew it, your card check, and which version of this notice it was under. It never includes your child's name, age or work.
Your choices
- See your child's work at any time, and download all of it.
- Withdraw your consent at any time. alai then stops saving or sending anything from your child, and Ally won't open for them, until you allow it again. What they write in the meantime stays on their device.
- Delete your child's profile and everything in it. Deleting it can't be undone. Copies on a device stay there until alai's data is erased on it.
- You can agree to alai collecting and using your child's information without agreeing to it being shared further: we only share it with the companies above, to run alai.
How to agree
Open tryalai.app/parent, sign in with your email, and confirm with a card. We charge your card 50¢ and refund it straight away, so you'll see the charge disappear or show as refunded within a few days. The card check shows us that a parent is agreeing; we never see your card number.
Questions
alai is run by Aiden Guan and Allen Hsieh. Write to support@tryalai.app with any question about your child's information. Our full privacy policy is at tryalai.app/privacy.
If a parent buys a plan that covers a child's profile, the parent pays through Stripe, which receives only the parent's details, never the child's.
9. Where your data is processed
alai is run from the United States, and our providers process data mainly in the United States. alai is intended for users in the US.
10. Changes to this policy
We'll update this policy when alai changes. If a change is significant, we'll tell you by email or in the app before it takes effect, and ask again where the law requires it. The date at the top shows the latest version.
11. Contact
Aiden Guan and Allen Hsieh · support@tryalai.app