Privacy policy

This is also the direct notice shown to a parent before a child account is created.

Last updated 2 August 2026.

Myntley is a private family points and rewards service. A parent creates and manages the family. The service contains no advertising, does not sell personal information, does not build advertising profiles, and has no public child profiles.

The short version. We collect the least we can to run a chores-and-rewards app for your family. No other family or public visitor can see your children. There are no ads and no third-party analytics tied to a child. A parent can delete a child's data, or the whole family's, from inside the app.

Information we process

  • Parent account information — email address, display name, authentication and security records, and family settings.
  • Child account information supplied by a parent — display name, avatar, colour, family-scoped username, and PIN-derived authentication credentials. We do not ask for a child's email address, phone number, birthdate, or location.
  • Family activity — tasks, completions, behaviour discussions, point ledger entries, rewards and redemptions, and optional display-only allowance ledger entries.
  • Optional reward content — kid or parent reward ideas, product URLs, extracted page titles and images, and parent-selected reward artwork.
  • Parent subscription information — the parent account identifier sent to RevenueCat, product and entitlement status, store platform, paid-through date, and minimal billing-event records. We do not receive or store card or bank details.
  • Basic operational information needed for authentication, security, reliability, and support.

The app does not transfer money. Any cash value or allowance balance is a note for the family and does not represent funds held or moved by Myntley.

Why we process it

To authenticate family members, operate the rewards service, calculate append-only balances and history, protect accounts, diagnose service failures, and respond to support requests. We do not use child information for advertising or unrelated profiling.

Sharing and service providers

Information is available only to authenticated members of the same family, subject to role-based database controls. Child accounts receive a limited view needed for their experience. Supabase provides hosted authentication, database, and serverless function infrastructure and processes data on our behalf. RevenueCat verifies and synchronises a parent's optional Myntley Plus subscription and provides subscription reporting. It receives the parent's account identifier and store purchase history, but is never initialised with a child account identifier. Apple and, when offered, Google process subscription purchases under their own store terms. Expo may relay notification tokens and messages when cross-device push notifications are enabled. We do not sell family or child information.

Reward links and external websites

Adding or refreshing an optional reward link asks the linked website for preview metadata and may also use the device operating system's link-preview service. That website or platform can receive ordinary connection information such as an IP address. Myntley stores the submitted URL and a bounded snapshot of the suggested title and image so the family can recognise the reward. Opening View website leaves Myntley and is then governed by that site's privacy practices. Parents decide whether a suggested linked reward is approved and visible to the family.

Parent notice and consent

Before creating a child account, the app shows this direct notice and requires the signed-in parent to confirm that they are the child's parent or legal guardian (or are otherwise authorised by one) and consent to processing the child account data for this service. Acceptance of the versioned notice is recorded. A parent can withdraw consent by permanently deleting the child account.

Retention and deletion

Family data remains while the relevant account or family is active. A parent can:

  • archive a child while preserving history;
  • permanently delete a child account and that child's completion, behaviour, points, redemption, and allowance history;
  • permanently delete their own parent account.

Parents are peers. If another active parent remains, deleting one parent preserves the family and shared records, with that parent's historical attribution removed. If the last active parent deletes their account, all child accounts and the entire family dataset are deleted. Active database records are removed immediately. Encrypted disaster-recovery backups may retain copies for up to 30 days before ageing out; they are not used to restore individual deleted accounts.

Security and parent rights

The service uses authenticated accounts, family-scoped row-level security, and server-authorised ledger operations. Parents can review family data in the app and request access, correction, or deletion through the support contact below. Subscription purchases and refunds are managed by the applicable app store; deleting a Myntley account does not by itself cancel an app-store subscription. No system is perfectly secure, but access is limited to what is needed to operate the service.

Children's privacy

Myntley is designed for families and is set up and administered by a parent. We keep child information to the minimum the service needs, use no advertising or third-party analytics SDKs tied to a child's identity, and provide no public profiles, feeds, or communication with anyone outside the family. If you believe a child account was created without a parent's authorisation, contact us and we will delete it.

Changes to this policy

If we make a material change we will update the date at the top of this page and, where the change affects how child information is handled, ask parents to review the notice again in the app.

Contact

Myntley is operated by its independent developer. For privacy questions, or to make an access, correction, or deletion request, email support@myntley.com. Most requests are faster to action yourself from inside the app — see Help.