Privacy Policy
Boomph is a children’s app · Effective 3 August 2026 · v1.5
Boomph is a chore game designed for children and controlled by a parent or guardian. A grown-up creates the account, sets things up, and stays in charge. This policy explains what we collect, why, and the choices you have. We’ve written it in plain English on purpose.
1. Who we are
Boomph is made by Rough Studio Ltd (Edinburgh, United Kingdom), the “data controller” for your family’s information. Questions, requests or concerns: hey@rough.ink.
2. Our approach
Privacy by design. We build to the principles of the UK Children’s Code, the US Children’s Online Privacy Protection Act (COPPA) and the UK/EU GDPR. That means: we collect as little as possible, keep high-privacy defaults, and never show ads, never use third-party ad-tracking, and never sell your data.
3. What we collect
Parent account: an email address (to sign in and reach you) and a password (stored securely by our authentication provider — we never see it).
Founding-family applications: a parent email address, a broad child age range, the Apple device available, and which part of chores causes the most friction. We don’t ask for a child’s name, diagnosis, photo or private family story. We use this only to select and contact the small founding-family cohort.
Child profile: a first name or nickname and an age. We don’t need — and don’t ask for — a child’s real identity, surname, address or contact details.
Task details: mission titles, completion status, rewards and any short task note a parent chooses to add. Please don’t put diagnoses, contact details or other sensitive information in a task note.
Photos: pictures a child takes of the task — the mess before, and the tidy-up after — so the game can check the job’s done. See the next section on how we keep people out of these.
Minimal technical data: basic, security-related information (such as rate-limiting signals) needed to run the service safely. No behavioural profiling.
4. No identifiable people — scenes and jobs only
Photos of people aren’t allowed. Boomph asks for the scene (the space) and the task only — never a person. Every photo passes an automated check before it’s stored, and the photo is rejected and never saved if it shows either of two things: a face (anyone’s, at any size, including a reflection) or anyone undressed (nudity, underwear or swimwear, a bare torso, or a bath, shower or toilet setting). If the check can’t run, we reject the photo rather than risk it.
The check is deliberately not a “no human pixels” filter. A hand steadying a bin lid, or a foot at the edge of a shot of a tidied floor, is neither identifiable nor sensitive, so it isn’t rejected — blocking those achieved nothing for privacy and stopped children finishing ordinary chores. The check sometimes mistakes posters or framed photos for real people, so a parent (never a child) can confirm “no one’s really in it” and upload anyway — we record that confirmation. Please still keep faces and anything identifying out of shot.
5. How we use what we collect
Only to run the game: to set up missions, and to check a task photo against the task. Photo checks are performed by Google’s Gemini AI acting as our service provider. Requests use our Google Cloud project in its London region through Gemini Enterprise Agent Platform (Vertex AI), under Google Cloud’s data-processing terms. Project-wide Gemini in-memory caching is disabled, and Google does not use your images to train its models without our permission. We do not use your data for advertising or profiling, ever.
6. Who we share it with
Only the service providers that make the app work, each acting on our instructions: hosting and private photo storage (Supabase), our web host (Vercel), photo-checking AI (Google Gemini), transactional email (Resend), and subscription and purchase management (Apple and RevenueCat). No advertisers. No data brokers. No sales.
7. Keeping and deleting data
We keep source and proof photos for 30 days after a mission finishes so a parent can review what happened, then remove the photo files and their mission references automatically. Photos uploaded to a draft but never attached to a launched mission are removed after seven days. Mission text and outcomes can remain in family history. Seen messages are removed after 30 days and AI usage records after 90 days. Expired family invites are removed, and short-lived security rate-limit records are removed after two days. A parent can delete their founding-family application at any time by emailing us; applications are removed automatically after 90 days. A parent can deleteeverything sooner — every photo and all family data, with no undo — from Settings, or by emailing hey@rough.ink. We action verified deletion requests promptly. We may keep limited records where the law requires it, such as purchase or consent records.
8. Parental rights & control
The account is yours to control. You can access, correct or delete your family’s data, and withdraw consent at any time (which ends the service for that child). To exercise any right, use Settings or email us. You can also complain to the UK’s Information Commissioner’s Office (ico.org.uk).
9. Children’s privacy & consent
Boomph is intended to be set up and run by a parent or guardian, who provides consent on behalf of their child. We design the experience to be age-appropriate. If you believe a child created an account without a parent’s involvement, contact us and we’ll remove it.
10. Security
Data is encrypted in transit and at rest. Photos live in private storage and are served only through short-lived, signed links to the right family. Access is scoped so one family can never see another’s data.
11. Where data is processed
We’re UK-based. Some service providers may process data outside the UK; where they do, we rely on appropriate safeguards for international transfers.
12. Changes & contact
We’ll update this policy as Boomph grows and post the new date here. Anything unclear? hey@rough.ink.