JaiPrivacy Policy
In short: Jai has no account. Your baby’s records live on your family’s phones. The developer has no copy of them and cannot read them, including when they travel through the server for “Sync away from home”. There is no advertising, and usage statistics are only sent if you say yes.
1. Who is responsible
Rui Pedro Correia, an individual developer based in Portugal, is the data controller for the limited data described in this policy. Contact: alpetraapps@gmail.com.
Jai is made for parents and caregivers. It does not ask for your name, email or phone number.
2. Records you enter
You may enter information about your baby: name, date of birth, optional gender and photo, feeds, bottles, diapers, sleep, growth measurements, pumping, medicines, solid foods, milestones and notes. Some of this can reveal health information, so please treat it with the same care as any family record.
These records are stored in the App on your phone. They are not sent to the developer. They leave your phone only in the ways described in Section 3.
The name you give a phone, such as “Mom”, is shown to the other phones in your family next to the entries it logged.
Photos you add to milestones, chosen with your phone’s photo picker, stay on the phone where you added them. They do not sync, and they are left out of backup files and of the operating system backup.
3. When records leave your phone
a) To the other phones in your family, on Wi‑Fi
Once you pair phones with a QR code, they exchange records directly on your local network, encrypted with AES‑256‑GCM using a key known only to your family’s phones. This does not go through any server.
b) Through the server, if you turn on “Sync away from home”
This Premium option is off by default. When it is on, records are encrypted on your phone with a key derived from your family’s secret, and placed in a mailbox on Google Firebase (region: Belgium, europe‑west1) until the other phones pick them up. The secret never reaches the server, so neither the developer nor Google can read the contents.
The server does handle the following, which it needs in order to work:
- the encrypted packets, a random mailbox identifier and an identifier for each sending phone;
- for each phone, a push token and its platform (Android or iOS), used to send a silent wake‑up with no content;
- an anonymous Firebase sign‑in identifier and an App Check result that shows the request came from the genuine App;
- technical data seen by any internet service, such as IP address and the time and size of each request.
Packets and mailboxes are deleted automatically about 90 days after the mailbox’s last activity. To remove them sooner, use Settings › Your data › Delete the data on the server. This turns the option off for the whole family, and every phone keeps its entries.
c) To your phone’s own backup
The operating system can include the App’s records in your personal backup: Android’s backup to your Google account, and the iPhone’s backup to iCloud or to a computer. These backups belong to your account and are controlled in your phone’s settings. The developer has no access to them. The family’s secret and the milestone photos are not included.
d) To files you export or share
You can export a full copy (JSON) or a table (CSV), and share a monthly card. These files are not encrypted, and you choose where they go. Once a file leaves the App, it is your responsibility.
4. Data the App collects automatically
a) Usage statistics, only with your consent
The App asks during setup whether you want to share anonymous usage statistics. If you do not say yes, they stay off. You can change your answer at any time in Settings › Your data.
When on, Firebase Analytics receives which screens and features are used, such as “an entry of this type was logged”, along with the plan, ranges for the number of phones and babies, the theme, and technical details such as device type, operating system, app version and an app instance identifier. It never receives names, times, amounts, notes or any record you entered. Advertising ID collection and ad personalisation are turned off.
b) Crash reports
Firebase Crashlytics receives technical crash reports: the error, device model, operating system, app version, the App’s internal data versions and an installation identifier. These reports are always sent, because they are how problems get found and fixed. They contain no names, times, amounts or records.
5. Purchases
Purchases are processed by the Apple App Store or Google Play. The developer never sees your card details or your name. RevenueCat keeps the status of the purchase under a random family identifier, so that one purchase can cover all of your family’s phones. It does not receive your baby’s records.
6. Permissions
| Permission | Why |
|---|---|
| Camera | Only to read another phone’s QR code. The images are processed on your phone and not stored. |
| Local network | To find and sync with your family’s phones on your Wi‑Fi. |
| Notifications and alarms | Special days, summaries, reminders and timers, all scheduled on your phone, and the background sync notice on Android. |
The App does not use your location, contacts or microphone.
Widgets, the lock screen timer and notifications can show information on your lock screen. You can turn them off in your phone’s settings.
7. Third‑party services
| Service | Purpose | Data involved |
|---|---|---|
| Google Firebase Firestore, Cloud Functions and Authentication | Encrypted mailbox for “Sync away from home” | As listed in Section 3b. Only when the option is on |
| Firebase Cloud Messaging and Apple Push Notification service | Silent wake‑up for that sync | Push token. Messages have no content |
| Firebase App Check, with Play Integrity and App Attest | Confirm that requests come from the genuine App | Device and app integrity signals |
| Firebase Analytics | Usage statistics, with your consent | As listed in Section 4a |
| Firebase Crashlytics | Crash reports | As listed in Section 4b |
| Google ML Kit (Android) | Read the QR code on your phone | Images stay on your phone. The library may report technical information about its own use to Google |
| RevenueCat | Keep the status of a purchase across the family’s phones | Random family identifier, purchase status and purchase data |
| Apple App Store and Google Play | Distribution, payments and the review prompt | Handled under your store account |
Personal data is not sold, and it is not shared for advertising. These providers may process data outside the European Economic Area under their own safeguards. See the Google, Apple and RevenueCat privacy policies.
8. Legal bases (EU and UK)
- Usage statistics: your consent, which you can withdraw at any time.
- Crash reports: the legitimate interest in keeping the App working.
- “Sync away from home” and purchases: providing the service you asked for.
9. Retention and deletion
- On your phone: until you delete it. Settings › Your data › Delete this phone’s data erases everything on that phone. This does not affect your family’s other phones, or the encrypted packets on the server.
- On the server: about 90 days after the last activity, or until you delete them as described in Section 3b.
- A phone removed from the family, or that leaves it: keeps the records it already has, but receives no new ones.
- Usage statistics and crash reports: kept for a limited period under the providers’ retention settings.
- Backups: under the control of your Google or Apple account.
10. Your rights
Depending on where you live, you may have rights under laws such as the GDPR or the CCPA, including access, correction, deletion, restriction, objection and portability. Most of them you can use directly in the App, where you can edit, export and delete your records. For anything else, write to the contact above. Because the App has no account and uses random identifiers, the developer may need your help to find data related to you, and cannot read the encrypted records.
In the EU you may also complain to your data protection authority. In Portugal this is the CNPD.
11. Children
Jai is intended for adults. It is not directed at children, and children are not meant to use it. Records about a baby are entered by parents or caregivers, who should have the authority to do so.
12. Security
Records in transit between phones and through the server are encrypted, and the family’s secret is kept in the phone’s secure storage (Android Keystore or iOS Keychain). Records stored on the phone are protected by your phone’s lock. Anyone who has your unlocked phone, or a phone in your family, can see them, so use a screen lock and remove phones that are lost. No method of storage or transmission is completely secure.
13. Changes to this policy
This policy may be updated when the App or its services change. The “Last updated” date above shows the latest version. Significant changes will be announced in the App or on this page.
14. Contact
Rui Pedro Correia
Email: alpetraapps@gmail.com