Your child's questions stay between them and Wobo.
This page says exactly what we hold, where it lives, who can see it and how to delete it. No jargon without a plain-words line beside it, and no claim we can't show you.
Every row here has a purpose, a shelf life and a delete button.
If something isn't on this list, we don't collect it.
email, name, class, board
questions, answers, drawings, progress
what you say to Wobo
card or UPI details
app version, crashes, screen size
Locked in transit, locked at rest, and opened only by the person it belongs to.
Encrypted on the way
Every connection uses TLS 1.2 or newer.
In plain words: nobody on the same Wi-Fi can read it.Encrypted where it sits
The database and its backups are encrypted at rest, keys managed by the hosting provider and rotated.
In plain words: a stolen disk is unreadable.Only your own rows
Access rules live inside the database itself, so a row is scoped to the learner it belongs to rather than to whoever asks for it.
In plain words: the lock is on the drawer, not just the door.Built carefully
Secrets never live in the code: every key is an environment variable and the service refuses to start in production without them. Types are checked and the test suites run on every push. Branch protection and dependency scanning are on the list and are not set up yet.
Built for a child on their own, so the rules are stricter than the law asks.
Neutral by design: no politics, no religion, no ads, no nudges to buy. When a question strays outside school, Wobo says so kindly and comes back to the lesson.
Consent, and what is not built yet. India's DPDP Act asks a parent's verifiable consent for a child, COPPA asks it under 13 in the United States, and the GDPR asks it at the age each European country sets. Wobo has no consent gate today. We are not going to draw a tick beside one until it works.
- What a parent gets. A weekly note by email with the week's lessons and what to nudge. A parent has no login of their own yet, so that note is the whole picture, and it never carries a child's typed questions word for word.
- The erase button. On You, under Settings. It clears what Wobo remembers about you, your saved boards and threads, and the parent link. Deleting the account itself is done by a person when you write to support@heywobo.com.
- No profiling for advertising. There is no advertising in Wobo, so there is nothing to profile for.
- No training on a child's data. A child's questions and drawings are never used to train models unless a parent turns that on, explicitly, and it can be turned off again.
Four kinds of people, one honest table.
Six lines we'd put in a contract.
The laws we are built to, and how the data is protected.
The laws we are built to
- India · Digital Personal Data Protection Act 2023. No profiling of a child for advertising, and erasure of the learning on request. There is no parental consent gate in Wobo today, and until there is we do not claim one.
- United States · COPPA. Under 13 needs a parent, and the parent may see, correct or delete everything we hold.
- Europe and the United Kingdom · GDPR, including the rules for children. Access, correction and erasure. A copy of what we hold is assembled by hand when you write to us; there is no download button and no consent gate yet, and we will not print either until it exists.
- California · CCPA and CPRA. Know what is held, have it deleted, and never have it sold, because we do not sell it to anyone.
How it is protected
- Storage we do not run ourselves. The database is a managed service and its encryption at rest is the provider's, not ours. We have not audited that configuration, so we describe it rather than certify it.
- TLS 1.2 or newer in transit. Every connection between a device, Wobo and anything behind it.
- Access rules inside the database. A row is scoped to the learner it belongs to by the database itself, not only by the app that asks for it.
- Secrets never live in the code. Every key is an environment variable, and the gateway refuses to boot in production without the ones it needs. Branch protection and automated dependency scanning are not set up yet.
Where a claim needs an outside auditor to be worth anything, we would rather show you the control than print a badge we have not earned.
What an outsider has not checked yet.
Every line below is scheduled, and each one moves up with the date it landed. Ask us for the current status any time.
The companies that touch data on our behalf, by role.
We name the roles here and the companies in the document you can request below. If a sub-processor changes, account holders get 30 days' notice by email.
Found something? Tell us and we'll answer within 72 hours.
Researchers who report responsibly get our thanks in public and never a legal letter. Families with a worry get a person, not a form.
support@heywobo.comThe paperwork, in plain words first.
These are drafts. We wrote them ourselves and a lawyer has not reviewed them yet, and each one says so at the top with the questions still open on it. We would rather you read that from us than find it.
Want the full security overview?
The named sub-processors, the region map, the incident-response plan and the current audit status, as one document. Written plainly, and readable by anyone.