Privacy Policy

Last updated: November 2, 2026

Primatech Paper Co. LLC ("we", "us", or "our") operates the KidTab mobile application (the "App"). This Privacy Policy describes what the App stores, what it sends to us, and what you can delete. The website section below also covers kidtab.app.

1. Family Sync, and What It Changes

KidTab keeps your family's records in a database on your device. That database is what the App reads and shows you. Family records are not uploaded to our Firebase project until a guardian turns on Family Sync, which is off when you install the App and is turned on in Settings under Family Sync. Each device decides separately whether to turn it on. Crash reports, described in section 4, are separate: they are sent whether or not Family Sync is on, and they contain no family records.

Family Sync copies your family's records to our Google Firebase project so that other guardians and other devices see the same family. Turning it on uploads the family already on the device. After that, every change made in the App is sent as it happens.

Family Sync needs an account. You sign in with Apple. You can also add an email address and a password to the same account, which is how you sign in to KidTab on Android. A child's own iPad is the one exception: it signs in without a name, email address, or password, as section 5 describes.

2. What We Receive When Family Sync Is On

With Family Sync on, we receive:

• Your family name and the currency you use.
• The name of every guardian and every child, along with any email address or phone number you entered for them. Email and phone are optional fields; we receive them only if you filled them in.
• Every ledger entry: the amount, whether it was earned or spent, whether it is pending, approved, or denied, the note and any link attached to it, the time, and the name of the person who recorded it. Money one child sends to another is recorded as a pair of entries, one on each child, linked to each other.
• Chores, their reward amounts, and their schedules.
• Wishlist items, their prices, notes, and links.
• The account identifier your sign-in produces, and the email address attached to it. If you use Apple's Hide My Email, that is the relay address Apple gives us, not your own.
• For a child's own iPad, the identifier of the anonymous account it signs in with and which child the iPad belongs to. That identifier is also attached to each chore the child marks done on that iPad.
• An identifier the App generates for each device the first time you use it and keeps from then on. It is attached to every record that device writes, so that devices can tell each other's changes apart. It is not an advertising identifier.

We use all of it for one purpose: running Family Sync. We do not sell it, and we do not use it to advertise to you or to build a profile of you.

3. Where the Data Is Stored

Records you sync are stored in Cloud Firestore, and your sign-in is stored in Firebase Authentication. Both are Google services. Google runs them for us and holds the data on our behalf, which makes Google our subprocessor. The Firebase project is named kidtab.

The Firestore database holding your family's records is located in us-central1 (Iowa, United States).

The copy on your device stays there and remains the copy the App reads. If you back up your device through iCloud Backup or through the Finder, that backup includes the App's local database. We have no part in that backup and no access to it.

4. Crash Reports, Analytics and Tracking

When the App crashes, or runs into certain errors we have chosen to record, it sends a crash report to us through Firebase Crashlytics, a Google service. A report contains where in the App's code the problem happened, error codes, the App version, your device model and operating system version, the device's free memory and storage, a random identifier that Firebase creates for this installation of the App, and a random identifier for the session in which it happened.

A crash report never contains your family's records: no names, amounts, notes, email addresses, phone numbers, or your account. It is not linked to your account, so we cannot tell whose device sent it. Crash reporting is always on, including when Family Sync is off, and the App has no setting to turn it off. Google keeps crash reports and their identifiers for 90 days and then starts removing them from its live and backup systems.

KidTab contains no advertising SDK, no analytics SDK, and no cross-app tracking. We serve no advertisements, and the App's privacy manifest declares that it does not track you.

The other Firebase software we use also reports its own technical diagnostics to Google. The Firebase Authentication, Firestore, Installations, and Messaging components, and Google's data transport library, each declare in their own privacy manifests that they collect diagnostic data. That happens inside Google's software; we do not receive those diagnostics and cannot see them.

5. Children's Data

KidTab is set up and run by adults. A guardian enters a child's name, and optionally an email address and a phone number, and a guardian decides whether to turn on Family Sync. A child never gives KidTab a name, email address, phone number, or password.

A child uses KidTab in kid mode on a guardian's device, or on their own iPad. To set up a child's iPad, a guardian with Family Sync on shows a code from their phone and the child scans it with the iPad. The iPad then signs in to Firebase Authentication anonymously: the account has an identifier but no name, email address, phone number, or password. It joins the family as a member and, like any synced device, keeps a copy of the whole family's records, but the App on it shows only that child's screens.

In kid mode or on their own iPad, a child can add wishlist items with prices, notes, and links; mark a chore done; and send money from their balance to a sibling with a note of up to 60 characters. These are stored like any other record and, with Family Sync on, are uploaded as section 2 describes. Guardians see every transfer and can undo it. Beyond what a child enters this way, we collect nothing from a child.

When Family Sync is on, the children's details and the whole ledger for each child are stored in our Firebase project along with everything else.

6. Third-Party Services

The App uses three outside services: Google Firebase, for Family Sync as described above; Firebase Crashlytics, for crash reports as described in section 4; and Sign in with Apple, for signing in. A child's iPad signs in through Firebase Authentication's anonymous sign-in, which is part of Google Firebase.

KidTab connects to no bank, card network, payment processor, or other financial institution. No real money moves through the App, and you never enter a payment instrument.

7. Data Security

The copy on your device is protected by your device: its encryption, its passcode or biometric lock, and the iOS application sandbox.

The copy in Firestore is reached over encrypted connections and is guarded by Firestore security rules that allow a family's records to be read and written only by accounts that are members of that family. Every member of a family can read and write that family's records, including the ledger, so add a guardian only when you mean to give them that. A child's iPad is a member too: the App on it shows only that child's screens, but the security rules do not yet tell it apart from a guardian's device.

8. Turning Sync Off, and Deleting Your Data

These are four different actions and they do different things.

• Turning Family Sync off stops sending changes and signs the device out. It does not delete anything already in the cloud. Your family's records stay in our Firebase project.
• Reset Local Data, or deleting the App from your device, removes the copy on that device. It does not delete the cloud copy or your account.
• Removing a child's iPad, by tapping Parent on the iPad and then Remove this iPad, signs the iPad out and erases the family's records from it. When the iPad is online, it also deletes the iPad's membership in the family. If the iPad is offline, it finishes anyway and the membership can be left behind. The child's records stay in the family either way. If the iPad is lost, or was removed while offline, email us and we will remove its membership.
• Settings, then Family Sync, then Delete Account is the one that removes the cloud copy. It asks you to sign in again to prove the account is yours. If you are the only guardian in the family, it deletes the family's records from our project. If there are other guardians and you are not the guardian who created the family, it removes your own guardian record and your membership and leaves their family intact. If you created the family and other guardians are still in it, the App refuses to delete your account until you remove them or they leave, because KidTab cannot yet hand a family to another guardian; the sign-in prompt names this when it happens. A child's iPad counts as a member here, so remove it first. It then revokes the Sign in with Apple token and deletes the account itself. The records on your device are untouched, so use Reset Local Data as well if you want those gone too.

None of these affects crash reports. They are not linked to your account, so turning sync off does not stop them and deleting your account does not remove reports already sent; they expire as section 4 describes.

9. How Long We Keep It

We keep your family's records for as long as Family Sync remains on and the account exists. There is no automatic expiry, and turning sync off does not start one. Deleting the account, as described above, is what removes the records.

Two things about deletion are worth knowing. When you delete a record in the App, we mark the row deleted rather than removing it, so that every device agrees it is gone. That marker stays. And a guardian's name is copied onto each ledger entry when they record it, so old entries keep that name even after the guardian has left the family.

Removing a child's iPad does not delete the anonymous account it signed in with. That account holds an identifier and no personal details, and it stays in Firebase Authentication until you email us and we delete it, along with any membership an offline removal left behind.

Invite codes and links carry their own expiry and stop working when they expire. Crash reports are kept for the 90 days described in section 4.

10. This Website

Cloudflare hosts kidtab.app and processes connection information, including IP addresses, to deliver and protect the site. Cloudflare Web Analytics measures visits and page performance without analytics cookies or cross-site tracking. Fonts, screenshots, and the demo video are served from this site; we do not embed a third-party video player.

This website does not set analytics cookies or assign its own visitor identifiers. We use Cloudflare Web Analytics for visits and page performance; custom download-click and demo-action counters are currently disabled.

Cloudflare’s handling of hosting and Web Analytics data is described in Cloudflare’s privacy policy and Web Analytics documentation. Clicking an App Store link opens Apple’s service, which has its own privacy policy. Emailing us sends the details you choose to share so we can respond; please do not include children’s financial records unless they are needed to resolve your request.

11. Changes to This Policy

We may update this Privacy Policy. If we make material changes, we will update the "Last updated" date at the top of this page. We encourage you to review this policy periodically.

12. Contact Us

If you have questions about this Privacy Policy, please contact us at:

Primatech Paper Co. LLC
926 Madison Ave
Redwood City, CA 94061
[email protected]