Privacy

How Chore Manager handles your data

This is a product copy draft. Update to match your deployment, hosting, and legal review before publishing.

What we collect

  • Account info you provide: username (required), first/last name (optional), email (required for admins/parents; optional/empty for child accounts), and password (stored as a hash).
  • Household data: household name/description, invite codes, memberships/roles.
  • In-app activity: chores, due dates, status timestamps, points, streaks, rewards, notifications, and optional photos for verification.
  • Integrations (optional): Home Assistant notify targets if you configure them. Email/SMS/push are not implemented yet.
  • Cookies: Django session cookie for authentication; no tracking pixels or ad cookies are built into the app.

Children and household accounts

  • Child accounts can be created without an email address. The app does not collect additional data from children beyond what admins/parents enter.
  • Household admins/parents control what they enter for children and are responsible for any required consent under local laws.

What we don’t do

  • No ads or third-party marketing trackers are included in the codebase.
  • We don’t sell your data.
  • No analytics SDKs are shipped by default.

Security and access

  • Passwords are stored as hashes using Django’s defaults.
  • Household access is invite-based; admins control memberships and roles.
  • API auth is not implemented in the current code—limit deployments accordingly until authentication is added.

Retention and removal

Data is retained while accounts/households exist. Define and document your deletion and export process for production deployments, and honor requests sent to the contact address below.

Questions or requests

For privacy questions or to request data deletion/export, email ljmerza@gmail.com.