Last updated: [DATE] · Effective: [DATE]
Chore Champions is a chore chart that families use at home. It is run by [COMPANY LEGAL NAME] (“we”, “us”), and this policy explains exactly what the app stores, why, how long it keeps it, and how to make us delete it.
Chore Champions is designed for children, so it is treated as a service directed to children under 13 and is operated to comply with the U.S. Children’s Online Privacy Protection Act (COPPA) and the FTC’s COPPA Rule. The short version: we collect as little as we can get away with, we show no advertising, we run no analytics or tracking, and we do not sell or share anyone’s information.
A parent sets up the chart and enters everything in the first group below. Children only tap chores on and off.
| What | Why | Who enters it |
|---|---|---|
| A child’s first name or nickname | So a child can find their own chart | Parent |
| An avatar emoji, colour, and theme | To make each child’s chart their own | Parent or child |
| Chores, their point values and schedules | The chart itself | Parent |
| Prizes and their point costs | The prize shop | Parent |
| Chore completions — which chore, which date, points earned, and a timestamp | To total up points and show progress | Child (by tapping) |
| Family chore check-offs — which shared family chore, which date, who did it (a child or “a grown-up”), and a timestamp | To show the family’s progress toward its weekly prize, and who pitched in | Child or parent (by tapping) |
| Prize redemptions — which prize, cost, timestamp | To subtract points when a prize is claimed | Parent (PIN-approved) |
| A parent PIN | To keep children out of the parent view. Stored only as a salted cryptographic hash — we cannot read it | Parent |
| A household access code | Identifies which family’s chart a device may open | Generated by us |
Your browser keeps your household access code in a secure cookie (so the kitchen tablet isn’t asked for it every time). It is sent only to this app’s own server, only over HTTPS, and the app’s pages can’t read it; it exists solely to keep the device signed in, never to track anyone. Your browser also remembers, for each child, which prize they are currently saving toward; that never leaves the device. Both are cleared when you log out of the device or clear your browser data.
Our hosting provider, Microsoft Azure, records standard web-server logs — including the IP address of the connecting device, the time, and which page or API route was requested. These exist to keep the service running and secure. We do not use them to build profiles and we do not combine them with a child’s chart.
From Parent → Settings → Send Feedback, a parent can send us a message. We receive exactly what they type, the kind of message they picked, the household’s internal ID (so a bug report can be traced to the right chart), and — only if they enter one — an email address so we can reply. Nothing from the chart is attached: no child’s name, chores, or points, and not the household’s name or access code. Sending feedback needs the parent PIN, so children cannot use it.
When the app’s server hits an unexpected fault, it records a technical description of it — the kind of error, where in our code it happened, and which part of the app was being used — so we can fix it. Error reports contain no child’s information and no household identifier; any data an error message quotes is removed before the report is recorded.
The app currently loads its typefaces from Google Fonts. That means your browser makes a request to Google’s servers, which necessarily discloses your device’s IP address to Google. We send Google nothing else, and no child’s information is involved. If you would rather this did not happen, we intend to serve the fonts ourselves in a future release.
We do not ask for, and the app has no field for, any of the following about a child:
And we do not, in any circumstance:
The household access code and the internal ID assigned to each child are persistent identifiers under the COPPA Rule. We rely on the Rule’s support-for-internal-operations exception, and to be specific about what that means here, they are used for exactly two things and nothing else:
They are never used for behavioural advertising, never used to recognise a user across any other website or service, and never disclosed to a third party. We enforce this by not integrating any advertising, analytics, or tracking service at all, so there is no recipient to disclose them to.
No one, other than the infrastructure that runs the app. Family data is stored in Microsoft Azure (Blob Storage and Static Web Apps), which processes it on our instructions in order to host the service. Feedback and error reports (§ 1) go to Mission Control, an operations dashboard we run ourselves on [HOSTING — e.g. Microsoft Azure]; it is not a third-party service and receives nothing else. Beyond that, we disclose information only where we are legally compelled to, or to protect someone’s safety.
Everyone who has your household access code can see your family’s whole chart. Treat it like a house key: share it only with people you want to have it, and rotate it under Parent → Settings → Household Access if it ever gets out.
This section is our written retention policy, published as the COPPA Rule requires.
| Information | Why we keep it | How long |
|---|---|---|
| Chore completions and prize redemptions | To calculate points, streaks, badges, and prize progress | 24 months, then automatically deleted. Only an anonymous running total per child survives, so deleting the detail never costs a child points or a badge they earned. |
| Family chore check-offs | To show this week’s and last week’s family progress | 8 weeks, then automatically deleted. They carry no points, so nothing is kept in their place. |
| A child’s name, avatar, colour, and theme | To display their chart | Until a parent deletes that child, or the household is deleted |
| Chores and prizes | The chart’s configuration | Until a parent deletes them, or the household is deleted. A one-time chore is also deleted automatically once the completions for its date have been (a little over 24 months after that date). |
| Parent PIN (hashed) and household access code | Access control | Until changed, or the household is deleted |
| Backup copies of the chart and of the household list (each change keeps the copy before it) | To undo a mistake or recover from a fault | Up to [CONFIRM — e.g. 60 days: a 30-day version lifecycle rule plus 30-day soft delete], then permanently deleted. A backup holds whatever the chart held at the time, so this is also how long something deleted from the chart can remain in a backup. |
| Feedback a parent sends us, including any reply email | To read, act on, and reply to it | [CONFIRM — e.g. deleted 12 months after it is closed] |
| Error reports | Finding and fixing faults | [CONFIRM — Mission Control retention for this app, e.g. 90 days] |
| Server logs | Operating and securing the service | [CONFIRM AZURE LOG RETENTION — e.g. 30 days] |
We keep a child’s information only as long as is reasonably necessary for the purpose it was collected for. We never retain it indefinitely, and we do not keep it in case it is useful later. When a parent deletes a child from the chart, that child’s completions, redemptions, family chore check-offs, and carried totals are deleted along with them. Backup copies that still contain them are deleted on the schedule above.
As the parent or guardian, you may at any time:
To make a request, contact us at [CONTACT EMAIL]. We will verify that you are the parent for that household before acting, and respond within [NUMBER — e.g. 30] days.
We maintain reasonable procedures to protect the information in the app: everything travels over
HTTPS; parent PINs are stored only as salted scrypt hashes and never in readable form;
repeated wrong PIN entries lock the parent view for a rising period; and access to family data
requires a household access code on every single request.
No system is perfectly secure. The household access code is a shared secret appropriate for a family chore chart, not for sensitive records — please don’t store anything in the app that would be harmful if someone else read it.
Information is stored in [AZURE REGION, e.g. the United States]. If you use the app from outside that country, you are asking us to transfer it there.
If we change this policy, we will update the date at the top. If a change materially affects what we collect from children or how we use it, we will obtain parental consent again before that change applies to information already collected.
[COMPANY LEGAL NAME]
[MAILING ADDRESS]
[CONTACT EMAIL]
[PHONE, if you want to list one]