Privacy Policy
This policy covers Proud Jar: Chores & Rewards (“Proud Jar”), the app for parents, the Proud Jar Kids app for children, and the Proud Jar service that keeps them in sync. Proud Jar is operated by AppXLab, an independent software studio run by Said Aazzou, Casablanca, Morocco (“we”). Contact us about privacy at privacy@appxlab.io.
What we collect and why
| Data | Where it comes from | Why |
|---|---|---|
| Parent email address, and your name if you give it (or Apple / Google share it) | Sign in with email code, Apple or Google | To sign you in and identify your account |
| Children’s first names and birth years | Entered by a parent | To show each child their own tasks and suggest age-appropriate ones |
| Household membership and roles | Created when you set up or join a household | To decide who can see and change what |
| Tasks, notes, rewards, decisions, tokens and ledger history | Created by parents and children in the apps | The core service |
| Screen-time sessions: minutes bought with tokens, when, the number of apps behind the gate, and whether screen time is turned on for the phone | Proud Jar Kids on iPhone and Android | To run the token-for-screen-time economy on the child’s phone. We never learn which apps are behind the gate or used: on iPhone Apple gives the app only sealed references, and on Android the list stays on the child’s phone. |
| Photo proofs (optional, with parent consent) | Proud Jar Kids camera | So a parent can check a task. Encrypted on the child’s phone before upload; only your approved devices hold the keys. |
| Device and installation identifiers, push notification tokens, device public keys | Each app | Pairing, device trust, sync notifications and parent alerts |
| Free-trial check: on iPhone, a one-time Apple DeviceCheck token (Apple keeps a single “trial used” flag for the phone; we store nothing about the device); on Android, a one-way hash of the app’s device identifier, kept only as a further keyed hash | The parent app, once, when a new family starts its free trial | To give each family one free Household trial and prevent repeated trials. Never used for advertising, tracking or anything else. |
| Plan status, free-trial dates and App Store transaction identifiers | Our service, and Apple when a parent subscribes on iPhone | To give your household the Household plan. We never receive your payment card details. |
| Optional parent-app usage statistics (off unless you turn them on) | Proud Jar parent app on iPhone and Android | Which screens are used and whether a task was approved, never names, photos or balances, and not linked to your account |
| Google Play email address and the app to test (Android beta sign-up only): yours, or for the Kids app the one used on your child’s phone | The Android beta form on proudjar.com and proudjar.app, filled in by a parent or other adult | To confirm the sign-up, add the address as a tester in Google Play, email installation instructions and beta news, and announce when Proud Jar is available on Google Play |
| Security and operations logs (request time, path, error codes; IP addresses only as a keyed hash for rate limiting) | Our servers | Keeping the service secure and working |
We do not collect location, contacts, messages, browsing history or advertising identifiers, and we do not sell or share personal data for advertising. The kids’ apps contain no analytics or advertising code. Android Kids includes Firebase Cloud Messaging for authenticated family synchronization.
Screen time on Android
If a parent turns on screen time in Proud Jar Kids on an Android phone, after an in-app explanation and the parent’s agreement, the app uses Android’s accessibility service for one purpose: to know which app is open, so it can cover the apps the parent chose and count paid minutes while one of them is open. It does not read what is on the screen, what is typed, or which websites are visited. The list of chosen apps and which app is open stay on the child’s phone and are never sent to us; our servers only learn how many apps are behind the gate, whether the service is on, and the minutes bought with tokens. Settings, the phone app and emergency apps are never blocked. It can be turned off at any time in Android settings, and the parent app then shows that it is off.
Our website
proudjar.com and proudjar.app count page views and taps on the download buttons, with the page, the store button, your browser’s language and a random session number held only in memory for the visit. This goes to the same self-hosted Aptabase server. There are no cookies, no advertising, no fingerprinting and nothing stored on your device, and it is turned off when your browser sends Do Not Track. The Android beta form sends what you enter straight to our mailing list server; the website itself does not keep it or count it.
Android beta sign-up
The Android beta form asks for a Google Play email address and whether you want to test the Parent app, the Kids app or both. It is for parents and other adults. The Kids app only works together with the Parent app: to test it, a parent enters the Google Play email used on the child’s phone, and that choice stays with, and is the responsibility of, the parent, as for the rest of Proud Jar Kids.
We email a link to confirm the address; nothing more happens until it is confirmed. Confirming does not enrol anyone in Google Play testing: when tester places are ready, we add the address to the tester list of the chosen app in Google Play Console and email installation instructions. The address then goes to Google as part of the testing program, under Google’s own terms and privacy policy. We also use it to tell you when Proud Jar is available to everyone on Google Play. We use it for nothing else, never for advertising, and we do not sell or share it. We do not record your IP address when you confirm, and we do not track whether a particular person opens our emails or clicks their links. Every email has an unsubscribe link, and you can ask us to remove an address at any time at privacy@appxlab.io.
Children’s privacy (COPPA and GDPR)
This section explains how we handle children’s information under the US Children’s Online Privacy Protection Act (COPPA) and the EU and UK General Data Protection Regulation (GDPR). The parent is the account holder; a child never has an account of their own. The parent gives consent by signing in to Proud Jar: Chores & Rewards, creating the household, adding the child, and pairing the child’s phone with a code shown in the parent app. A child’s information is either entered by the parent or created on the child’s phone after the parent has paired it, and photo proofs stay off until the parent turns them on.
What we keep about a child is limited to: their first name and birth year, entered by the parent; their tasks, tokens and rewards; and, only if the parent turns them on, photo proofs that are end-to-end encrypted on the child’s phone. Proud Jar Kids also uses the technical data listed above (device and push notification identifiers, and on a phone with screen time turned on, the minutes bought with tokens) to work. Proud Jar Kids contains no analytics and no advertising, and we do not use a child’s information for anything other than running the family’s Proud Jar.
A parent can review their child’s information in the parent app at any time. To delete it, the household owner can delete the household in the app (Family → Our Family → Delete household), which erases the children, tasks, tokens, rewards, photos, devices and pairing codes; see Delete your account. To delete one child’s data, email privacy@appxlab.io. A parent can also stop further collection by removing the child’s phone from the household or turning off photo proofs, and can email privacy@appxlab.io from the address they sign in with to get a copy of their child’s information. We verify the request before acting on it.
Proud Jar Kids is set up by a parent, who pairs the child’s phone with the household. Children use an anonymous installation session connected by a parent, not an email or social sign-in account. They have no subscription checkout. External help links and connection settings are behind a parent check. A parent can see and delete their children’s information at any time. A child’s information is added by, and stays under the control of, a parent: we only collect it after a parent has created the household and paired the child’s phone. In the European Economic Area and the UK we process it to provide the service the parent asked for, and optional photo proofs only after the parent turns them on. In the United States, Proud Jar relies on the parent setting up and controlling every child profile, and a parent can review, change or delete their child’s information at any time, or ask us to. If a parent signs a child’s phone up for the Android beta, the parent enters that phone’s Google Play email and remains responsible for it (see Android beta sign-up).
Photos
Photo proofs are encrypted on the child’s phone and can be opened only on devices the household has approved. Photos expire after the period your household chooses (7, 14, 30, 90 or 365 days; 30 by default). Connected viewers recheck access and clear it on expiry, revocation or backgrounding. Previously downloaded information on an offline device cannot be remotely recalled; screenshots or other copies cannot be recalled. After expiry, new server access is refused; erasing the stored copy is retried until it succeeds, which can take longer if storage is briefly unavailable. Photos are never added to a photo library. If every approved device and your recovery kit are lost, earlier photos cannot be opened by anyone, including us.
Who processes data for us
| Provider | Purpose |
|---|---|
| OVHcloud, Gravelines, France (EU) | Runs the Proud Jar API and database |
| Amazon Web Services (Amazon S3), Frankfurt, Germany (EU) | Stores encrypted photo proofs, and sealed records of deletions (identifiers and times only) so that deletions can be re-applied if a backup is ever restored |
| Amazon Web Services EMEA SARL, AWS region EU (Paris), France | Stores encrypted backups of the Proud Jar database, the deletion records, the Android beta mailing list and the usage statistics |
| Resend, which sends through Amazon Simple Email Service | Sends sign-in codes and Android beta emails |
| listmonk mailing list, self-hosted by AppXLab at hello.proudjar.com on OVHcloud in France (EU) | Keeps Android beta sign-ups, confirms them and sends beta emails |
| Apple | Sign in with Apple, push notifications, App Store purchases, Screen Time on the child’s device |
| Sign in with Google if you choose it; Firebase Cloud Messaging for Android synchronization and optional parent alerts. Android screen time runs entirely on the child’s phone and sends Google nothing. Google Play testing, for the Android beta testers we invite. | |
| Aptabase analytics, self-hosted by AppXLab at insights.appxlab.link | Optional parent-app usage statistics (iPhone and Android), and anonymous statistics for this website; never in the kids’ apps |
We share personal data only with the providers above, and only what each one needs for the purpose listed. Our service providers (OVHcloud, AWS, Resend) process data only on our instructions under data-processing terms that require protection consistent with this policy. Apple and Google process data under their own privacy terms. listmonk and Aptabase are self-hosted by AppXLab, so the data they hold is not shared with another company.
How long we keep it
- Photo proofs: until the household’s retention period ends, then erased.
- Household records: while the household exists. Deleting the household erases its records, photos and pairing codes.
- Accounts: until you delete your account. Deleting it also revokes a linked Sign in with Apple authorisation.
- Android beta sign-ups: until you unsubscribe or ask us to remove the address. We keep them after the beta so we can tell you when Proud Jar is available on Google Play. Google keeps tester lists in Google Play under its own terms.
- Usage statistics (the optional parent-app statistics and this website’s statistics, held on our self-hosted Aptabase server): kept no longer than 14 months, then deleted automatically.
- Encrypted backups: encrypted on our server before they are stored with AWS in Paris, and kept for up to 30 days to recover from failures, then deleted and fully erased from storage within a further 6 weeks; a restored backup re-applies deletions made after it was taken before the service reopens.
- Deletion records (sealed identifiers and the time of each deletion, no names, emails or photos): kept for 90 days so that a restored backup can re-apply deletions, then deleted and fully erased from storage within a further 7 weeks. Copies inside encrypted backups follow the backup period above.
- Free-trial records: one keyed hash per parent account and per Android phone, with no email, device identifier or family data, kept after household or account deletion so the same phone or account cannot start another free trial.
- Subscription records: minimal transaction identifiers and opaque purchase-binding records may be kept after household deletion to prevent a subscription being attached twice. They are kept only while needed for that, and for up to 7 years where tax or accounting law requires it.
Your choices and rights
You can review your family’s data in the app, ask us for a copy of it, turn off analytics and notifications, shorten photo retention, remove devices and co-parents, and unsubscribe from Android beta emails with the link in any of them, delete your household (Family → Our Family) or your account (Family → Household settings → Account) in the app or as described on Delete your account. Depending on where you live you may have further rights, for example to access, correct or object to processing, and to complain to a data protection authority. Contact privacy@appxlab.io.
Security
Traffic is encrypted in transit. iPhone sign-in credentials use Keychain. Android local credentials and records are encrypted using Android Keystore; Android app backups are disabled. Photo-device private keys require supported secure hardware. Photos are end-to-end encrypted between approved family devices. No system is perfectly secure; tell us about any concern at support@appxlab.io.
Changes
We will post changes here and, for significant changes, tell you in the app before they apply.