What we collect, and what we will never do with it.

All of it comes from you setting the account up and your student using it. None of it is bought from anyone else or inferred about you from elsewhere.

Your account

Your name, your email address, and a password — which is stored as a hash, so nobody here can read it. Nothing else is required to create an account.

Each student profile

The name you give the profile, the language and course label you set for them, and — only if you choose to set one — a short PIN for quick sign-in on a family device. The PIN is stored hashed, the same way a password is.

Course material you upload

The files themselves — a syllabus, a vocabulary list, a study guide, a phone photo of a handout — along with the original file name, the file type and the size. We also store the summary the AI builds from each file, which is what the tutor teaches from.

What your student does in the product

Quiz answers and scores, flashcard results, conversation practice, writing and reading exercises, notes, and the progress records built out of all of it. This is the product working; it is also the part that tells you which concepts keep slipping.

Operational records

A daily count of how much AI work each course used, per student and model, so we can run the service and keep the price honest. Plus ordinary web server logs.

What we do not ask for

We do not collect a date of birth, a home address, a phone number, or the name of your student’s school. There is no field for any of them.

There are four uses, and this is the complete list.

To run the product. Reading your uploads into a course, generating practice and quizzes from them, building a study plan aimed at a date you gave us, and tracking what is and is not sticking.

To show you what is happening. The parent view — progress, weak spots, what is coming up — is built from your own student’s work.

To keep the account working and secure. Signing you in, recognizing a family device you have marked, and measuring AI usage so one account cannot exhaust the service for everyone else.

To email you about your account. Address verification, student invitations, password resets, and notices about this policy or about billing.

We do not build an advertising profile, we do not sell or rent anything to anyone, and we do not share your student’s work with other families.

LearnVai is built on Claude, made by Anthropic. Course material you upload, and the practice content built from it, is sent to Anthropic’s API so the tutor can work from your student’s real class rather than a generic curriculum. This is the core of the product; there is no version of LearnVai that does not do it.

The prompts are assembled from course material and practice content. Your name, your email address and your student’s profile details are not part of them.

Anthropic’s commercial terms state that material submitted through their API is not used to train their models.

AI output can be wrong. That is a product limitation rather than a privacy one, but it is worth saying on the same page: check anything that matters.

Three kinds of company, and no others.

Anthropic processes course material and practice content so the AI features work, as described above.

Microsoft Azure hosts the application, the database, and the uploaded files, and sends our transactional email through Azure Communication Services. Uploaded files sit in Azure Blob Storage, which the application reaches using its own managed identity — there is no account key and no shareable link that could leak one.

Authorize.net stores and processes all payment information. Payment information never goes through LearnVai's system.

There are no advertising networks, no analytics vendors and no data brokers in that list, and we do not intend to add any.

Two ordinary exceptions apply, as they do everywhere. We may disclose information if the law requires it, and if LearnVai is ever sold or merged, accounts would transfer with it — in which case this policy travels with your data until you are told otherwise.

LearnVai is built for middle and high-school students, and the account belongs to a parent or guardian. Students do not sign themselves up: parents create each profile, and we record the moment parents affirmed consent for it.

We keep your family’s data while the account is open, because that is what makes a course useful in March that you set up in September. When you want it gone, you do not have to ask us.

Delete one file and the stored original goes, along with the summary built from it.

Delete a student profile and their documents, quizzes, notes, plans and course links go with it.

Delete the account from your account settings and it removes you and every student only you oversee, together with everything attached to them. A student overseen by a second guardian stays with that guardian.

Your rights

You can see what is in your account, correct it, delete it, and ask us for a copy of it. Ask through the contact address below and we will not make it difficult.

Three, and this is genuinely the whole list.

The sign-in cookie keeps you signed in. It is shared between this site and the app, which is how the header here knows your name when you are already signed in over there.

The family-device cookie is set only if you mark a browser as a family device to enable PIN sign-in. It holds a random token; we store only a hash of that token, so the cookie is the key and we do not hold a copy of it.

The antiforgery cookie stops another site submitting a form to us as you.

No analytics cookies, no advertising cookies, nothing from a third party. That is why this site has never asked you to accept anything.

Passwords and PINs are stored as hashes and never in a form anyone here can read. The family-device token is stored only as a SHA-256 hash. Uploaded files live in Azure Blob Storage and are reached with the application’s managed identity rather than an account key or a shareable link. Everything travels over HTTPS.

No system is perfect, and we would rather write that down than claim otherwise.

If this policy changes or is updated, we will post the new version here with a new effective date. If a change materially affects what happens to your family’s data, we will email the account address rather than quietly swapping the page.