Baby-in-Car — Privacy Policy
Effective date: 8 August 2026 Last updated: 8 August 2026
This Privacy Policy describes how the Baby-in-Car mobile application (the “App”), developed by Pham Gia (“we”, “us”), handles information when you use the App. By using Baby-in-Car you agree to the practices described below.
Baby-in-Car exists to remind you that a child is in the car. Doing that means the App holds details about your family — names, ages, photos, where you drive. All of it stays on your device. We have no server, no account system, and no way to read any of it.
1. Information you enter, and where it stays
Everything below is stored only on your device, using the operating system’s app storage. It is never uploaded, never synced, and never visible to us:
| What | Examples |
|---|---|
| About your children | Name, birth year, boy/girl, avatar colour, and a photo if you add one |
| About you | The name you enter for yourself, and the name of an emergency contact (a name only — no phone number or email) |
| About your car | The Bluetooth name and identifier of the car you pair with |
| Trip history | Start and end times, which children rode along, how many reminders were sent, whether you acknowledged one, and — if you allow location access — the coordinates where each trip started and ended |
| Settings | Alert loudness, repeat counts, which detection methods are on |
Uninstalling the App deletes all of it. There is no copy anywhere else.
2. Device permissions and why the App asks
The App asks only for what the reminder actually needs. Each is optional in the sense that you can refuse it — but refusing some of them means the App cannot detect trips, which is its whole purpose.
- Location (While Using and Always) — used to detect when a drive has started and ended, and to stamp each trip in your history with where it began and finished. “Always” is required on iOS so detection keeps working when the App is not on screen. Coordinates are written to your trip history on your device and are not transmitted to us or to anyone else.
- Motion & Fitness / Physical activity — used to recognise that you are driving, as an alternative to Bluetooth detection.
- Bluetooth — used to notice when your phone connects to or disconnects from your car, which is how the App knows a trip started or ended.
- Notifications — used to deliver the reminder. This is the point of the App; without it there is nothing to alert you.
- Camera and Photos — used only if you choose to add a picture to a child’s profile. The image is saved into the App’s own storage on your device. It is not uploaded anywhere.
The App does not record audio, does not access your contacts, and does not read your messages, call history, or files.
3. Information collected by third-party services
While your family’s data stays on your device, the App does include services from Google that collect limited technical information:
| Category | Examples | Source |
|---|---|---|
| Device & app info | Device model, OS version, app version, language, country | Firebase Analytics |
| Automatic app events | App opened, session length, screen views, app updated | Firebase Analytics |
| Crash diagnostics | Stack traces, app state at the time of a crash, an anonymous device identifier | Firebase Crashlytics |
| Advertising identifiers | Advertising ID (Android), IDFA (iOS — only if you allow tracking) | Google AdMob |
| Coarse advertising signals | Approximate location derived from your IP address, ad interaction events | Google AdMob |
We do not send any custom events describing your children, your car, or your trips. Analytics reports only the standard app lifecycle events listed above.
Note that the approximate location AdMob derives from your IP address is separate from, and much coarser than, the GPS coordinates in your trip history — those never leave your device.
4. Third-party services
Baby-in-Car uses the following services. Each has its own privacy policy that you should review:
- Google Firebase Analytics — anonymous usage analytics so we can understand how the App is used. Firebase Privacy Information
- Google Firebase Crashlytics — automatic crash reporting so we can fix bugs. Firebase Privacy Information
- Google Firebase Remote Config — lets us turn features on or off without shipping a new release; collects no personal data.
- Google AdMob — shows ads inside the App. AdMob may collect an advertising identifier and basic interaction data. Google Ads Privacy & Terms
These services act as our data processors under applicable privacy law (GDPR, CCPA).
5. Advertising
Baby-in-Car is free, and ads are what pays for it. The App shows a banner above the tab bar and, on some launches, a full-screen ad while it opens. Ads never appear during setup, and never on the first screen you reach after finishing setup.
- On Android, ads use your device’s Advertising ID. You can reset it or opt out of personalised ads at any time: Settings → Google → Ads → Reset advertising ID / Opt out of Ads personalisation.
- On iOS 14.5+, we ask once for App Tracking Transparency (ATT) consent. If you decline, ads are still shown but in non-personalised form (no IDFA), and the App behaves identically in every other way.
You can opt out of personalised advertising from major ad networks at youradchoices.com (US) or youronlinechoices.eu (EU).
6. Children’s privacy
Baby-in-Car is designed for parents and carers, not for children. The App is not directed to children and is not intended to be used by them.
The App does hold information about children — a name, a birth year, a photo — because that is what a reminder needs in order to be useful. That information is entered by an adult, stored only on the device, and is never transmitted to us, to Google, or to any advertiser. We have no access to it and cannot retrieve it.
Ads served in the App are configured for a general audience. We do not use audience targeting intended for children.
If you believe a child has used the App and provided information in a way that concerns you, contact us at the address in Section 10 — although in practice, deleting the child’s profile in the App, or uninstalling the App, removes the data completely, because there is no other copy.
7. Data retention
- Local data (children, car, trip history, settings, photos) lives on your device for as long as the App is installed. Deleting a profile removes it immediately; uninstalling the App removes everything.
- Analytics and crash data is retained by Google according to Firebase defaults (typically 2 to 14 months) and then deleted.
8. Your rights
Depending on where you live (EU/EEA, UK, California, etc.), you may have rights to access, correct, or delete the data held about you, and to opt out of analytics and advertising.
For everything you entered into the App, you can exercise those rights directly: edit or delete a child’s details from within the App, or uninstall it to remove all of it at once.
For the technical data collected by Firebase and AdMob, we do not collect identifiers tied to your identity (no email, no account), so we cannot single out your records. Uninstalling the App stops that collection from your device. You can also limit it in device settings:
- Android: Settings → Google → Ads and Settings → Apps → Baby-in-Car → Permissions
- iOS: Settings → Privacy & Security → Tracking and Settings → Privacy & Security → Apple Advertising
9. Data transfers
Firebase and AdMob are operated by Google and may transfer data to servers located in the United States and other countries. Google maintains Standard Contractual Clauses for EU/EEA data transfers.
Data you enter into the App is not transferred anywhere, because it never leaves your device.
10. Changes to this policy
We may update this Privacy Policy from time to time. The “Last updated” date at the top will reflect the change. Continued use of the App after a change constitutes acceptance of the revised policy.
11. Contact
If you have questions about this Privacy Policy or your data, email:
mobileapps.dp@gmail.com