Last updated: 25 July 2026
Choremon turns household chores into screen time: a parent assigns a chore, the child marks it done, the parent approves it, and only then are play-time minutes added.
This policy describes exactly what the app stores and where it goes. It is written from the app's source code, not from a template. If a feature is not listed here, the app does not do it.
Choremon is made by Truc Pham Trung, an independent developer. For anything in this policy, write to hi@trucph.am.
| What | Where it goes | Why |
|---|---|---|
| An anonymous device ID generated by Firebase Authentication | Google Firebase | So two devices in the same household can be linked to the same family. It is a random string. It is not linked to your name, your email address or your Apple ID. |
| Your family: a family name, the members in it and their role (parent or child), the children and their play-time balance and daily limits | Google Firebase (Cloud Firestore) | So both devices see the same balance and the same rules. |
| Chores: the title you type, a category, the minutes it is worth, who it is assigned to, and when it was created, completed and approved | Google Firebase (Cloud Firestore) | This is the app. Note that the chore title is free text — if you type a person's name into it, that name is stored. |
| Requests for extra time: the number of minutes and a short message the child types | Google Firebase (Cloud Firestore) | So the parent can read the request and approve or decline it. This is also free text. |
| A six-digit pairing code | Google Firebase (Cloud Firestore) | Used once to link a child's device to the family. It expires after 15 minutes, and it is deleted as soon as a new code is issued. |
| Crash reports | Google Firebase Crashlytics | So we can fix crashes. A crash report contains device model, iOS version and a stack trace. It does not contain your chores or your family's data. |
To lock and unlock apps, Choremon uses Apple's Family Controls, Managed Settings and Device Activity frameworks. These give the app opaque tokens for the apps a parent has chosen to manage, and a count of minutes used.
That information is held only in a shared container on the device itself
(group.am.trucph.choremon). It is never uploaded to our servers, never written to
Firebase, and never shared with anyone. Deleting the app deletes it.
We also cannot see which apps you chose. Apple deliberately hands the app opaque tokens rather than app names, so even we do not learn what is on the device.
Choremon is designed to be used by a family. The person who sets the app up, links the devices and approves chores is a parent or guardian. A child uses a linked device to see their chores and mark them done.
We do not knowingly ask a child for personal information. The app does not request a child's name, age, email address, photo, contacts or location, and it does not let a child message anyone outside their own family. The only text a child can enter is a short note asking a parent for more time, which only that family's parent device can read.
If you are a parent and you believe your child has entered information you would like removed, email hi@trucph.am and we will delete it.
Data is stored on Google Firebase (Authentication, Cloud Firestore and Crashlytics), acting as our processor. Google's handling of it is covered by the Firebase Privacy and Security policy.
Access rules on our database limit reads and writes to devices that have been paired into the same family. Nobody else's device can read your family's chores.
We do not have any other third parties. We do not sell data. We would only disclose data if we were legally required to.
Deleting the app from a device removes everything stored on that device, including all Screen Time information. It does not by itself delete the family record stored in Firebase — email us for that.
Depending on where you live, you may have the right to ask for a copy of your data, to have it corrected, or to have it deleted. Because we hold no name or email address for you, we identify a request by the family it comes from — write to us from the device in question so we can match it.
Traffic between the app and Firebase is encrypted in transit using HTTPS. Database rules restrict access to devices paired into the same family. No system is perfectly secure, but we do not store passwords, payment details or contact information, so there is little to lose if something goes wrong.
If the app starts collecting something new, we will update this page and change the date at the top before the new version ships.
Questions, requests, or anything that reads wrong here: hi@trucph.am.