Privacy
Two different things are described here, because they are genuinely separate: this website, and the app a tutor signs in to. They run on separate systems and hold different data.
This website
What we collect. If you join the waitlist: your email address, and optionally your name, how you came across us, and anything you write in the notes field. Nothing else. There is no account and no login on this site.
Analytics. We use PostHog, hosted in the European Union, configured so that it sets no cookies and stores nothing in your browser. Visitor counts come from a hash computed on PostHog's servers rather than from an identifier following you around. This is why you have not been asked to accept cookies — there are none to accept. PostHog also records anonymised session replays of pages on this site, with all form inputs masked, so what you type is never captured.
Why we are allowed to. You gave us your details in order to be contacted about the beta, and that is the only thing we use them for. We do not sell them, and we do not send anything unrelated.
How long we keep it. We keep your waitlist entry until the beta opens to you, or you tell us you are no longer interested — and in any case no longer than 12 months from the day you joined. We clear expired entries at least once a quarter.
Getting it back or deleted. Email us and we will send you everything we hold about you, or delete it, without asking why and without trying to talk you out of it.
The app
The app is where a tutor records sessions. It holds information about children, so it is described separately and held to a higher standard.
Children do not use Bloomate. Students have no account, no login and no way to type anything into the product. Everything recorded about a child is entered by their tutor. Screens a child might see are read-only. This is deliberate and it is load-bearing: it is what keeps collection outside COPPA's "from a child" trigger.
Consent comes first. A child's record exists on their parent's or guardian's consent, recorded per student — who consented, when, and how — and obtained before the record is created. We hold ourselves to COPPA's verifiable parental consent standard because it is the strictest of the regimes we operate under.
What is held. A student's profile — which may include an SEN profile, learning style and behavioural notes — and the sessions their tutor logs: what was covered, what the tutor observed, what they tried and whether it helped. We treat all of it as special-category data about a child, whether or not a particular jurisdiction requires that, and we collect the least that makes the next-step suggestion work.
What we never do with it. It is not sold, not used to train anyone's model, not used for advertising, and not shown in our marketing. There is no analytics or session recording anywhere in the app — the tool described in the section above runs on this website only, and never on a page displaying a child's record.
Who processes what
| Processor | What for | Where | Student data |
|---|---|---|---|
| Supabase | Storage and sign-in | Singapore | Yes, at rest |
| Render | Hosting the app and this website | Singapore | In transit only, never stored |
| Anthropic | Generating suggestions for the tutor | United States | Yes — profile and recent sessions are sent with the request. Their terms exclude training on it. |
| PostHog | Website analytics | European Union | No. This website only. |
| Notion | Our research library | — | No. One-way, out of Notion, carrying nothing about a student. |
That is the complete list. Adding to it is a recorded decision, not a quiet change.
What the software will not decide
Bloomate suggests; the tutor decides. Nothing the model generates reaches a parent or a child until the tutor has read it and can change or discard it, and it is labelled as a suggestion wherever it appears. It does not assess, diagnose, score or measure a student, and a pattern it spots is a hypothesis rather than a finding.
Bloomate is not safeguarding software and it does not discharge anyone's safeguarding duty. If something in a record suggests a child may be at risk, the product's only job is to get it to the tutor intact and quickly. It does not judge it, score it, escalate it, or route around them.
Your rights, and how to use them
A tutor can export or delete any student's record, or their whole account, from inside the app. A parent's request is answered by their tutor rather than by us directly — the tutor holds the relationship, and a whole-account export would contain other children's records.
For anything else, including a complaint about how we have handled data, contact our data protection officer at dpo@bloomate.education. You can also complain to your local regulator: the Privacy Commissioner for Personal Data in Hong Kong, or the Personal Data Protection Commission in Singapore.
Where we are
Bloomate is incorporated in the United States and operates in Hong Kong, Singapore and Taiwan. COPPA, the FTC Act, Hong Kong's PDPO, Singapore's PDPA and Taiwan's PDPA bind us. We additionally hold ourselves to the GDPR, the ICO's Children's Code and UN CRC General Comment No. 25 as a baseline, not because they apply to us, but because they are the strictest articulation of a position we hold anyway. Where COPPA is stricter, COPPA governs.
Changes
If this notice changes in a way that affects what we do with your data, we will say so here with a new date, and email anyone on the waitlist if the change concerns them.