Privacy Policy

Privacy Policy

Last updated: 1 August 2026 Β· Applies to the Boba (Bocah Bahagia) Android app, package com.bocahbahagia.app

Boba is a chore and reward app used by one family at a time. This policy describes exactly what the app stores, why, and how to get rid of it. It is written to match what the app actually does β€” not a generic template.

The short version. Boba stores the family content you create (children, chores, rewards, coin history) plus your Google account name and email so you can sign in. It contains no advertising, no analytics and no tracking SDKs. Nothing is sold or shared for marketing. You can have everything deleted at any time β€” see Delete your account and data.

1. Who we are

Boba (Bocah Bahagia) is an independent Android app. For privacy questions, data access requests and deletion requests, contact bobaprodaps@gmail.com.

2. What we collect

2.1 Parent account

A parent signs in with Google Sign-In. We never see or store your Google password. From that sign-in we store:

2.2 Child profiles

Children do not have accounts. A child profile is created by a parent and contains only what the parent enters plus in-app progress:

No email address, phone number, contact list, location or advertising identifier is collected from a child β€” ever.

2.3 Family content

2.4 Proof photos (optional)

Only if a parent switches on β€œrequire a proof photo” for a chore. The child may then attach a photo from their gallery or camera. Photos are compressed on the device, uploaded to Google Cloud Storage, and shown to the parent for approval. They are deleted automatically 7 days after upload by a scheduled job. Boba never uploads a photo the child did not explicitly attach.

2.5 Subscription (Boba Pro)

If you buy a Pro subscription, payment is handled entirely by Google Play. We never receive or store your card, bank or billing details. We store your family's subscription status β€” whether it is active, which plan, and when it expires β€” and a one-way hashed reference to the Google Play purchase, used to make sure one purchase unlocks one family.

2.6 What we do not collect

3. Why we use it

PurposeData used
Sign you in and keep you signed inGoogle account identifier, name, email
Let both parents manage the same childrenFamily membership, roles, invite codes
Run chores, rewards, coins and the level journeyFamily content, child profile progress
Let a child sign in on their own devicePairing code, PIN hash
Notify a parent when a child finishes a chorePush token, chosen language, notification records
Show a parent the proof of a finished choreProof photo (max 7 days)
Unlock Pro features for your familySubscription status, hashed purchase reference

We do not use your data for profiling, advertising, or automated decisions that affect you legally.

4. Who processes it

Boba runs on Google Firebase. Google LLC acts as our processor for authentication, database storage, file storage and push delivery, and Google Play processes subscription payments. Data is stored in Google Cloud in the asia-southeast1 region.

We do not sell your data and we do not share it with advertisers, data brokers or analytics providers. We disclose data only where the law requires it.

5. How long we keep it

DataRetention
Proof photosDeleted automatically 7 days after upload
A deleted child profileTheir chores, redemptions, coin ledger, notifications and pairing entry are deleted with the profile
Your account and familyKept while you use Boba; deleted on request β€” see below
Subscription recordsKept while the subscription is active, and afterwards only as long as needed for billing and refund handling

6. Children's privacy

Boba is designed to be set up and supervised by a parent. A child never creates an account, never provides an email address, and never signs in with an identity provider. Everything on a child profile is either typed in by their parent or generated by using the app.

Boba shows no advertising, uses no ad SDKs and does no personalised profiling, which is how we comply with children's privacy rules including the US Children's Online Privacy Protection Act (COPPA) and the child-specific provisions of the EU GDPR. A parent can view, correct or delete any child profile at any time from inside the app, and deleting a profile also disables that child's pairing code so their device can no longer sign in.

Nothing in the child experience sells anything. A subscription can only be started from a parent's own Google-authenticated account on the parent side of the app. The screens a child sees contain no price, no plan name, no purchase button, no link out to a store or website, and no message asking them to get an adult to buy anything. Where a feature is switched off for a family, the child is simply told it is not currently available and that a parent controls it.

7. Your rights

You can ask us to give you a copy of your data, correct it, or delete it. Most of it you can already edit or delete yourself inside the app. For anything else, email bobaprodaps@gmail.com and we will respond within 30 days. Depending on where you live you may also have the right to object to processing, to restrict it, or to complain to your local data protection authority.

8. Deleting your data

Full instructions, including exactly what is removed and what is kept, are on the Delete your account and data page.

9. Security

One limitation we would rather state plainly than bury. A child's device deliberately has no account: it signs in with a pairing code and a PIN, which keeps us from having to collect an email address or any other identifier from a child. The trade-off is that the records a child's device needs to read β€” child profiles, chores and rewards β€” are not protected by a password on that device, so they should not be treated as private against a determined attacker. This is why those records deliberately hold as little as possible: a first name or nickname chosen by the parent, a cartoon avatar, and in-app progress. There is no email address, phone number, address, date of birth, photo of a child, location or advertising identifier anywhere in them, and PINs are only ever stored hashed. Treat a pairing code as a secret, and recreate a child profile if one leaks.

10. Changes

If this policy changes we will update the date at the top of this page. If a change materially affects how we use your data, we will also say so in the app.