← Back to Chore Champions

Privacy Policy

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.

1. What the app stores

A parent sets up the chart and enters everything in the first group below. Children only tap chores on and off.

WhatWhyWho enters it
A child’s first name or nicknameSo a child can find their own chartParent
An avatar emoji, colour, and themeTo make each child’s chart their ownParent or child
Chores, their point values and schedulesThe chart itselfParent
Prizes and their point costsThe prize shopParent
Chore completions — which chore, which date, points earned, and a timestampTo total up points and show progressChild (by tapping)
Prize redemptions — which prize, cost, timestampTo subtract points when a prize is claimedParent (PIN-approved)
A parent PINTo keep children out of the parent view. Stored only as a salted cryptographic hash — we cannot read itParent
A household access codeIdentifies which family’s chart a device may openGenerated by us

Stored on your own device

Your browser keeps your household access code (so the kitchen tablet isn’t asked for it every time) and, for each child, which prize they are currently saving toward. This never leaves the device and is cleared when you clear your browser data.

Ordinary server logs

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.

Fonts served by Google [SEE NOTE — FIX OR KEEP]

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.

2. What the app does not collect

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:

3. Persistent identifiers and internal operations

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:

  1. Authenticating and authorising requests — deciding which family’s chart a request is allowed to read or change.
  2. Maintaining the service and personalising content within it — attaching a completion to the right child so their own points, badges, streaks, and theme appear on their own chart.

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.

4. Who we share information with

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. 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.

5. Data retention policy

This section is our written retention policy, published as the COPPA Rule requires.

InformationWhy we keep itHow 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.
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
Parent PIN (hashed) and household access code Access control Until changed, or the household is deleted
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, and carried totals are deleted along with them.

6. Parents’ rights

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.

7. Security

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.

8. Where information is held

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.

9. Changes

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.

10. Contact us

[COMPANY LEGAL NAME]
[MAILING ADDRESS]
[CONTACT EMAIL]
[PHONE, if you want to list one]