CaviKin

How CaviKin handles children's information

Version of November 7, 2026

Families can add their children so a kid can check off chores, see the family calendar and add to the shopping list. This page explains what we keep about children, why, and what parents can do about it. It applies to every member a parent adds as a Kid, which is anyone under 18.

Draft. The company details below aren't final yet, and this page is waiting on a lawyer's review.

Who we are

CaviKin, [postal address]. Email [email protected]. We answer within 30 days.

We ask a parent first

A child can't use CaviKin until a parent who manages the household agrees. The parent adds the child in Settings → Sign-ins, enters the child's birth month and year (never the day), and confirms that they are the child's parent or legal guardian and agree to this notice. Until then the child sees only a waiting page, and nothing about them is saved. We record who agreed, when, and which version of this notice they saw.

We never ask a child for more information than they need to take part, and a child can't add contact details, photos or location to their own profile.

What we keep

  • The child's name, the email address they sign in with, and their birth month and year. We use the month and year only to tell whether they are under 13 or a teen (13 to 17), because the two get different limits.
  • What they do in CaviKin: chores they check off, items they add to the shopping list, their notification settings.
  • Records an adult shares with them. These stay the adult's records.
  • Sign-in records and a log of changes, so we can keep accounts secure.
  • The date they last used CaviKin, so we can delete accounts nobody uses.

What we don't do

  • We don't show ads, sell children's information, or share it with anyone for their own use.
  • Children can't link an email account. Children under 13 can't link a calendar; teens can link their own.
  • Nothing about a child is sent to an AI model, including our own.
  • Children don't get text messages. Notifications go only to their own device and carry no details.
  • A child can't see anything another member keeps private.

Who handles it for us

These companies process information only to run CaviKin for us, under contracts that limit them to that:

  • Hosting provider: running the app and its database
  • Clerk: signing in
  • Cloudflare: delivering the site securely
  • Apple, Google or Mozilla push services (whichever the device uses): delivering notifications, which carry no details
  • Amazon Web Services Simple Email Service: emailing parents before an unused child account is deleted

Children's information may be processed in the United States. For people in the EU and UK we rely on [the EU-US Data Privacy Framework / Standard Contractual Clauses] for these transfers.

How long we keep it

  • While the child uses CaviKin, we keep what's listed above.
  • If nobody signs in to a child's account for 12 months, we delete it. Parents get a notice in CaviKin and an email 30 days before. Signing in again keeps the account.
  • When a parent deletes the child's account, or the whole household, it's deleted from the live system at once (households after a 7-day grace period a parent can cancel).
  • Copies in our backups are overwritten within 14 days.
  • After deletion we keep only a record that a deletion happened, with no details about the child.

What parents can do

A parent who manages the household can, at any time and without contacting us:

  • See and download everything we keep about the child: Settings → Sign-ins → the child → Download their data.
  • Delete the child's account: Settings → Sign-ins → the child → Delete their account.
  • Withdraw consent: Settings → Sign-ins → the child → Withdraw consent. The child is signed out at once and nothing more is collected. Withdrawing doesn't delete what's already kept; use Delete for that.

Parents can also write to us for any of these. In the EU and UK, parents (and teens, as they get older) also have the rights to correct information, to restrict or object to its use, and to complain to their data protection authority.

The legal basis (EU and UK)

We process a child's information on the basis of their parent's consent (GDPR Articles 6(1)(a) and 8), and sign-in and security records on our legitimate interest in keeping accounts safe (Article 6(1)(f)).

Changes

If we change how we handle children's information in a way that matters, we'll tell parents in CaviKin and ask for consent again before the change applies to their child.

Children's privacy · CaviKin