♥ LittleLog

Privacy Policy

Last updated: May 16, 2026

LittleLog (“the app”) is built to help parents track their baby's daily life. We take your privacy seriously. This policy explains what data the app handles, where it lives, what third-party services are involved, and what permissions it uses.

TL;DR

What data we handle on-device

The following is stored locally in the app's private storage and is never transmitted to any server we control:

• Baby profile info you enter (name, date of birth, optional sex, optional birth weight/length, optional photo)
• Daily logs you record (diapers, bottles, breast feeds, sleep, solids, temperature, custom categories, free-text notes)
• Photos you attach to logs, milestone months, or baby profiles
• Medication schedules and dose history
• App preferences (theme, custom categories, alarm sounds, active baby)

All of this lives in a local SQLite database and the app's private files directory. Other apps on your device cannot read it.

Advertising (Google AdMob)

LittleLog displays a single banner ad at the bottom of the screen, served by Google AdMob. To serve and measure ads, AdMob — not LittleLog — may collect:

• Your Android Advertising ID (a resettable, non-permanent identifier)
• Approximate (IP-based) location, not GPS
• Device info (model, OS version, language, screen size)
• Ad interaction data (impressions, clicks, viewability)

This data is handled by Google under Google's Privacy Policy. We never receive personal identifiers from AdMob — we only see anonymous, aggregated revenue reports.

You can reset or opt out of personalised ads at any time:

• Android: Settings → Google → Ads → “Delete advertising ID” or “Opt out of Ads Personalisation”.
• iOS: Settings → Privacy & Security → Apple Advertising → turn off Personalised Ads. (LittleLog requests App Tracking Transparency permission on iOS; if you deny it, only non-personalised ads are shown.)

Crash reports (Firebase Crashlytics)

LittleLog uses Firebase Crashlytics to report crashes so we can fix bugs. When the app crashes, the following technical data is sent to Google:

• Crash stack trace and last few debug log lines
• Anonymous Crashlytics Installation UUID (a random identifier, not linked to you)
• Device model, OS version, app version, build number
• State of the app at the time of the crash (which screen was open, etc.)

We do not include your baby's name, photos, logs, medication info, or any free-text notes in crash reports. Crashlytics data is retained by Google according to their data-retention policy (90 days for crash data).

Permissions and why we need them

Permission	Why we ask
Camera android.permission.CAMERA	To let you take photos for events, milestone months, or baby profile pictures. The camera is used only when you tap an “Add photo” or “Camera” button.
Photo picking (gallery)	Photo selection uses the system Android Photo Picker (Android 13+) or document picker (older). You select each photo manually, and the app receives access only to that file. We do not request READ_MEDIA_IMAGES or storage permissions.
Advertising ID com.google.android.gms.permission.AD_ID	Required by the Google Mobile Ads SDK on Android 13+ to deliver the banner ad. You can reset or disable this identifier in your device settings (see the Advertising section above).
Post notifications	To show medication-dose reminders and timer notifications.
Schedule exact alarm / Use exact alarm	To fire medication alarms at the exact scheduled time.
Full-screen intent	To show the medication alarm screen on top so you don't miss a dose.
Foreground service / Foreground service media playback	To keep the alarm sound playing reliably when the screen is off.
Receive boot completed	To re-arm scheduled medication alarms after the device restarts.
Vibrate, Wake lock	So the alarm vibrates and wakes the screen when it fires.
Request ignore battery optimizations	Optional — you may grant this if alarms are being killed by aggressive battery saving.
Internet	Used for fetching banner ads from AdMob, sending crash reports to Firebase Crashlytics, and — only if you enable it — uploading your backup to your own Google Drive.
Google Sign-In + Google Drive (drive.appdata)	Optional. Only requested if you turn on Google Drive backup, so the app can store and restore a backup in a hidden, app-private folder in your own Drive. Not requested otherwise. See “Backups & Google Drive” above.

Backups & Google Drive

Manual file backup. LittleLog can export your data as a single file (a ZIP that bundles your logs, medications, milestones, and photos, or a legacy per-baby JSON). The export is created locally and only goes somewhere if you tap Share and pick a destination. We never receive a copy.

Automatic Google Drive backup (optional). You may sign in with your Google account and turn on automatic backup. When enabled, LittleLog uploads a backup snapshot of your LittleLog data directly from your device to a hidden, application-private folder in your own Google Drive (the Drive “Application Data folder”).

• Scope requested: only https://www.googleapis.com/auth/drive.appdata (Google Drive — app data). This scope can access only the hidden folder LittleLog itself created. It cannot read, list, modify, or delete any of your other Google Drive files, and it cannot see your Google profile, contacts, or email content.
• What is stored there: a snapshot of your babies, daily logs, medications and dose history, milestones, custom categories, and the photos you attached — the same data the app stores on-device.
• Where it goes: directly from your device to your own Google Drive over an encrypted connection. LittleLog has no server and never receives, stores, or processes a copy. We only keep the 5 most recent snapshots in your Drive; older ones are deleted automatically.
• Your control: backup is off until you enable it. You can turn it off, delete all backups from inside the app (Backup & restore → Clear all backups), or revoke LittleLog's Google access entirely at Google Account → Third-party access.

LittleLog's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data obtained via the drive.appdata scope is used only to provide the user-facing backup and restore feature, is never transferred to others, is never used for advertising, and is never read by humans.

Milestone collages can be shared as PNG images via the share sheet — same model: we hand the file to your share sheet and step out of the way.

Children's privacy

LittleLog is designed for parents and caregivers to track their own child's data. The app is not directed to children under 13, and we do not knowingly collect any data from children. The Google AdMob banner is configured to show non-personalised, family-friendly ads.

Data deletion

Because LittleLog has no account or server, deleting your data is immediate and local:

• Delete a single baby (and all its events, photos, meds, and milestones) from Profile → tap the baby → “Delete baby”.
• Uninstall the app to remove everything on-device in one step. Android will purge the app's private storage as part of uninstall.
• Delete all Google Drive backups from inside the app: Backup & restore → “Clear all backups”. You can also revoke LittleLog's Google Drive access at Google Account → Third-party access; uninstalling does not automatically delete data already in your Drive's app folder.

For Crashlytics or AdMob data held by Google, follow Google's deletion process via Google Account → Data & privacy.

Changes to this policy

If we change this policy we will update the “Last updated” date at the top. Material changes (e.g., adding a new third-party SDK) will also be announced in the app's release notes.

Contact

Questions about this policy or your data? Email allen07edwarddev@gmail.com.