Privacy
How Dobbin treats your family's data
Last updated November 10, 2026.
The short version
Dobbin handles private family-care records without advertising, ad tracking, data sale or paid AI services. You can turn off account-linked app analytics at any time. Our service providers are Cloudflare for hosting and email, PlanetScale for account metadata, Apple and Google for sign-in, purchases and notifications, Sentry for crash and error reports, and PostHog for app and website analytics.
What the app handles, and why
Apple- or Google-derived account identifiers, email addresses from sign-in and an optional account field, device sessions, household membership, caregiver and child profiles, and the records you log: feeding, sleep, pumping, diapers, routines, milestones, growth, health observations, notes and photos you choose to attach. These support sign-in, household access, history, trends, exports and native Watch and widget features. We may send service emails to everyone with an email address. Product updates require opt-in and include an unsubscribe link. Cloudflare Email Service sends transactional service emails.
Push‑notification tokens associate notifications with your signed‑in device: Apple Push Notification service tokens on iPhone and Apple Watch, and Firebase Cloud Messaging tokens on Android. Background notifications carry a refresh hint (on Android, the household's ID, its revision number and the time it was sent), and your phone then fetches the change from our server itself. Live Activity updates on iPhone contain the timer's display state so the lock screen can update while the app is suspended.
On Android, notifications are delivered through Google's Firebase Cloud Messaging, and only once you're signed in and a household is open. To do that, Google's messaging library creates a random Firebase installation ID for this install of the app and sends it to Google with basic device details (Android version, device model and brand, the store that installed the app, and the app and library versions). Google handles this as our service provider, to deliver notifications from Dobbin. Dobbin doesn't use Firebase Analytics, Crashlytics or your advertising ID.
Where it is stored
Family records, notes and health data stay in Cloudflare Durable Object databases, and photos in Cloudflare R2. PlanetScale Postgres processes account metadata: email, account and household IDs, analytics IDs, membership, caregiver and child counts, platform, dates, trial and purchase status, purchase store, test-purchase status, and product-update preferences. Contact preferences and analytics IDs also live in the Account Durable Object. Requests use HTTPS and require household membership. Devices keep a protected household cache for offline history. This is server-side storage, not end-to-end encryption.
Crash and error reports
When the iPhone or Android app crashes or freezes, or our server hits an unexpected error, a report goes to Sentry (Functional Software, Inc.), which processes it for us in the United States. Test and development builds send nothing.
A report from the app holds technical details only: where in the code it failed (the stack trace) and a cleaned‑up error message, the app version, your device model and system version, and the device's state at the time, such as memory, storage, battery, language and time zone. For a small sample of launches it also records how long the app took to start and to load screens. To count crash‑free sessions, the Sentry library creates a random identifier for the app installation. A report from our server holds the error, the kind of request and its route with identifiers removed.
Reports are cleaned before they leave your device or our server: no names, child or caregiver details, health entries, notes, photos, account or household IDs, email addresses, tokens, screenshots or screen recordings, and IP addresses aren't stored with them. They aren't linked to you or your account, and they're used only to find and fix crashes and errors, never for tracking, advertising or usage analytics. Sentry keeps them for at most 90 days, then deletes them.
App analytics
The iPhone and Android apps use PostHog’s SDK for account-linked usage analytics, processed for us in the United States. The Apple Watch, widgets and Wear OS send no analytics themselves. Development builds, tests and sample data send nothing.
What is sent: when the app is opened; how far setup got (sign-in, naming the household, the free-trial step) and whether you created a household, joined one or signed in to an existing one; that an entry was logged, its kind, only as feeding, sleep, diaper, pumping, solids or other (every health, growth, milestone and routine entry is “other”), and where: in the app, a widget, Siri or Shortcuts, a notification or a Quick Settings tile; which main screens you open (Activity, History, Trends, Account, Settings, Privacy, Export, Import, Unlock); a few features (CSV, PDF or backup export, starting an import, creating an invitation, starting or stopping a timer); when the trial or unlock offer is shown and what opened it; that a trial started, the unlock was bought or the purchase was cancelled; and when a save, sync, purchase, import or export fails, with only a general reason (network, server or other). Each event carries the app version and build, the platform and its major system version, the app's language without your region, whether the household has one caregiver or more, and whether the app came from the App Store, TestFlight or Google Play.
With Share usage enabled, the iPhone app also asks Apple’s AdServices API whether an install came from an Apple Ads tap. If it did, we record the campaign, ad group, keyword and ad IDs, country and conversion type in PostHog, linked to your account, to measure which keywords lead to trials and purchases. The attribution token goes only to Apple. We do not request tracking permission or use IDFA, share this data with data brokers or use it for cross-app ads. Event properties do not include names, notes, photos, amounts, durations, entry times, your child’s age, health details, prices or error messages. Entries logged from a widget, Siri or a notification are noted on your phone by kind and source, then sent when you open the app. A random analytics ID kept by the Dobbin server links usage across your signed-in devices to your account. The SDK also processes technical session and device details. Your IP address is not stored or used for location lookup.
Turn off Share usage in Account → Privacy to stop analytics. Sending stops and queued events are dropped. PostHog keeps events for up to a year. Account deletion requests removal of your PostHog person and events.
Sign in and sessions
Sign in with Apple (iPhone) or Sign in with Google (Android) establishes your identity. The server verifies the provider's credential, derives an account ID from its stable identifier and keeps the email address supplied at sign-in (verified for Google), including Apple's private relay address when used. It stores hashes of device session tokens. Tokens live in the Keychain on Apple devices and in private app storage on Android. The Watch receives its own session from the signed-in iPhone.
Dobbin never holds a Google access token: it checks the one-time sign-in token and keeps the sign-in email described above. Apple and Google accounts are separate, so the same person signing in on both gets two Dobbin accounts that can belong to the same household.
Purchases and the free trial
On iPhone, the 14‑day free trial and the one‑time household unlock go through the App Store. Apple handles payment; Dobbin never sees payment details. To start a trial or unlock a household, the app sends the App Store’s signed transaction to our server, which keeps the transaction and original transaction IDs, product, store environment, whether it was bought or family-shared, which member started the trial or bought the unlock, and when.
On Android, the free trial starts without any store transaction; the server records which member started it and when. The unlock is bought through Google Play, and Google handles payment: Dobbin never sees payment details. The app sends the Google Play purchase token to our server, which checks it with Google Play and keeps the order ID, a one-way hash of the token (the token itself only until Google confirms the purchase), product, test-purchase status, purchasing member and time. An unlock covers every caregiver in the household on iPhone and Android.
These records are used only to unlock the household, show who paid, honour refunds and stop one purchase from unlocking many households. Deleting the purchaser's account removes their account from the record, and the household stays unlocked. Deleting the household deletes its record. A separate link from the purchase to the household holds no account data and is kept, so a restore can move the purchase to the purchaser's next household. Refunds go through Apple or Google Play, whichever store you bought from.
Who can see it
Only members of your household. Owners control invitations and membership; participants can leave. Removing access blocks future reads and writes. A disconnected device may keep a cache until it reconnects or is cleared. Signing out on your device does not erase another parent's household.
Exports and deleting records
You can export CSV, PDF or a full backup to a destination you choose; exported copies are outside the app’s retention controls. Deleting an individual record keeps a small tombstone so retries cannot resurrect it. Deleting a household is owner-only and removes its operational records and photos. Nightly backups of household data are kept for 30 days. Deleted data, including photos and backups, is fully removed within 30 days.
Bringing history from another app
If you choose to upload Nara or Huckleberry CSVs, Dobbin sends their contents and filenames to its import service on Cloudflare, together with your chosen time zone. The service reads child profiles and activity records to show a preview, including a summary of your family's own history: totals, daily and monthly patterns and the latest day. That preview is shown only to the browser tab you uploaded from and, through your link, to the Dobbin app. Uploading alone cannot change a household.
Finish in Dobbin is a private, single-use link. Its secret is in the part of the link after the #, which browsers don't send to servers. The first signed-in Dobbin app to open the link claims the upload for its household, after you agree in the app, and only the app can import it. The website then shows only that the upload was opened and how the import is going, never which family opened it, and you can stop it there. You choose where each child's history goes in the app before anything is added.
An unfinished upload expires after 24 hours. Discarding its preview removes the temporary profile and activity data, including the summary. Once imported, the records and their original source fields are kept with your household, so you can inspect details that do not fit Dobbin's usual fields. Entries you leave out are not added to the household; keep your original CSVs as a backup. Stopping a running import keeps the activities already added.
The website keeps a private upload-session token in this tab's session storage to let you return to the preview or progress. It expires after 24 hours and is never put in a web address. The website does not save your CSV contents in browser storage. Keep your Finish in Dobbin link to yourself. Import records follow the household access and deletion rules above.
Deleting your account
Anyone can delete their account in the app: Account → Delete Account, on iPhone or Android. On iPhone, Apple first confirms it's you. If you can't open the app, you can ask us to delete your account by email. The server then:
- deletes every household where you are the only member, including its records and photos;
- for a shared household you own, hands ownership to the longest-standing remaining member, then removes your membership; for a shared household you joined, removes your membership. Records you logged in a shared household stay with it, because they are part of the other caregivers' history;
- revokes every phone and Watch session, deletes push-notification registrations, contact preferences, the analytics ID and account metadata and household memberships, and requests deletion of the PostHog person and events. Deleting a household also deletes its account metadata and memberships;
- asks Apple to revoke Dobbin's Sign in with Apple tokens, so Dobbin no longer appears as connected to your Apple Account. If that step can't be completed, your account is still deleted and the app explains how to stop using Sign in with Apple in iOS Settings. A Google account has nothing to revoke, because Dobbin never holds a Google token; you can still remove Dobbin from your Google Account's third-party connections if you like.
The server doesn't keep your Apple or Google identifier in readable form: your account ID is a one-way digest of it. Hashes of the deleted sessions are kept, for seven days, so an interrupted deletion can report that it finished. The identifiers needed to retry deletion are kept until those requests succeed. Your devices then sign out and clear their session, cached household copies, widgets and the Watch credential.
Want to keep a copy? Export a backup, CSV or PDF before you delete. Exported files stay wherever you saved them.
This website: analytics, launch sign-ups and feedback
This website has no ads. Like any site, requests pass through Cloudflare, which processes technical data such as IP addresses to deliver and protect it. The free tools run in your browser and send nothing to a server.
Analytics. We use PostHog to see how people use this website, such as which pages they visit and which buttons they tap. It doesn't use cookies, store anything on your device or build a profile of you, it doesn't store your IP address, and it never receives your files or anything you type. It doesn't run on pages that carry an invitation or import code, or when your browser sends Do Not Track or Global Privacy Control. PostHog processes this data for us in the United States and keeps it for up to a year. The app's own account-linked analytics are described above.
Cloudflare Web Analytics. Cloudflare, which hosts this website, also counts page views and measures how quickly pages load. It doesn't use cookies, store anything on your device or build a profile of you. It sees the page address without anything after a “?” or “#”, the page you came from, your browser and device type and the page's loading times, and shows us only totals. It's blocked on invitation pages, and the Dobbin app doesn't use it.
Launch sign-ups. If you ask to hear when Dobbin reaches the App Store or Android, we store your email address, which launch you asked about, the page you signed up on, the date, and the country Cloudflare reports for the request. It's used only to send that announcement.
Feedback form. If you send feedback from the support page, we store the type you chose (bug, idea or question), your message, your email address if you add one, the date, a shortened version of your browser's user-agent string and the page the form was on. Your IP address isn't stored with it; to slow down spam, a one-way hash of it is kept for about ten minutes. Feedback is used only to reply to you and to improve Dobbin.
Feedback from the Android app. Send feedback in the app's Account screen uses the same form, so the same details are stored. Your message also includes the app version, Android version and phone model, so we can reproduce problems; nothing about your account, household or entries is sent with it. Diagnostic logs are never uploaded: if you choose to include them, they're attached to an email you send from your own email app.
Both are kept in Cloudflare Workers KV. No automatic deletion period has been set yet. To have a sign-up or a message deleted, email support@dobbin.app and include the address you used.
Medical use
The app records caregiver observations. It does not diagnose, prescribe or make clinical claims.
Contact
Questions about privacy, or a request to access or delete your data: support@dobbin.app. Help with the app is on the support page.