Privacy Policy - Doppio

Last updated: September 2026

Doppio is a caffeine tracking application for iPhone. This Privacy Policy explains what data the app stores, what data may be shared with third-party services, how that data is used, and what choices you have.

Doppio is designed to keep your caffeine, brewing, coffee, symptom, and Health data on your device and in your own private iCloud. The app does not require an account, and the developer operates no server that receives your data.

Summary

Your caffeine log, brewing sessions, saved brew recipes, coffee shelf, detox plan, withdrawal symptoms, metabolism profile, and app preferences are stored on your device.
Some of that data (your caffeine log, coffee shelf including photos, and saved brew recipes) also syncs through your own private iCloud so it is available on your other devices. It is stored in your personal iCloud account, not on any server run by the developer.
Doppio does not require a user account.
HealthKit data is accessed only with your permission and is not sent to the developer, Firebase, or any advertising service.
Doppio uses Firebase Analytics for optional usage analytics. Analytics is off by default and can be turned on or off in the app at any time.
Analytics events do not include caffeine amounts, drink names, notes, symptom types, symptom severity, HealthKit data, sleep durations, or onboarding health-profile answers.
In-app purchases are processed by Apple through the App Store. Doppio uses Apple’s StoreKit directly and no third-party purchase or subscription service.

1. Data You Create in the App

Caffeine Entries

When you log caffeine, Doppio stores information such as drink name, caffeine amount, timestamp, optional notes, an optional 1–5 rating, and an optional link to a coffee product on your shelf.

This data is stored on your device using SwiftData and also syncs through your private iCloud (see Section 3). It is not sent to the developer or to Firebase.

Brewing Sessions and Saved Brew Recipes

When you use the brew tools, Doppio may store brew-related information such as brew method, dose, ratio, grind, roast, water temperature, timer usage, lever-pull settings, and caffeine estimates.

If you save a brew recipe, Doppio stores that configuration and an optional “favorite” flag. Saved brew recipes are stored on your device, sync through your private iCloud, and are also copied into a private on-device App Group container so the Home Screen widget can start them.

This data is not sent to the developer or to Firebase.

Coffee Shelf

If you add coffee to your shelf, Doppio stores the bag’s name, roaster/manufacturer, whether it is whole bean or pre-ground, grind size, roast level, Arabica/Robusta ratio, packing and opening dates, your notes, and an optional photo of the bag.

This data is stored on your device and syncs through your private iCloud (photos included, as iCloud assets). It is not sent to the developer or to Firebase.

Detox Plan and Withdrawal Symptoms

If you use the detox feature, Doppio may store your caffeine reduction plan, daily targets, progress, and any withdrawal symptoms you log (type, intensity, duration, notes).

This data is stored on your device only (in local storage, not SwiftData) and does not sync through iCloud. It is not sent to the developer or to Firebase.

Metabolism Profile

If you complete the onboarding questionnaire, Doppio stores your estimated metabolizer type, sensitivity level, personalized caffeine half-life, and the answers you gave.

This data is stored on your device only and does not sync through iCloud. It is not sent to the developer or to Firebase.

App Preferences

Doppio stores settings such as theme, notification preferences, daily caffeine limit settings, Health sync settings, selected tab preferences, hidden drinks, drink ordering, brew timer state, and other app preferences.

These settings are stored on your device using local Apple storage mechanisms and do not sync through iCloud.

2. Apple HealthKit

Doppio can optionally integrate with Apple Health. HealthKit access is disabled unless you grant permission, and each type is requested separately.

Permission	What it is used for
Write caffeine to Apple Health	Saves caffeine entries you log in Doppio to Apple Health. Doppio can also remove entries it previously wrote.
Write headache symptoms to Apple Health	Saves headache symptoms you log during a detox plan.
Read sleep analysis from Apple Health	Shows recent sleep information alongside your caffeine insights.

Doppio does not request read access to caffeine data. It does not import caffeine logged by other apps or devices.

HealthKit data is handled on-device and through Apple Health. Doppio does not send HealthKit data to the developer, Firebase, advertising services, or data brokers, and does not use it for advertising, tracking, analytics profiling, or marketing.

You can revoke HealthKit permissions at any time in the iOS Settings app under:

Privacy & Security → Health → Doppio

3. iCloud Sync

Doppio uses Apple’s CloudKit to keep part of your data in sync across the devices signed in to your Apple Account. This is on automatically whenever you are signed into iCloud; if iCloud is unavailable, the app works normally with on-device storage only.

Your data is stored in your own private iCloud database. It is not shared with anyone, it is not visible to the developer, and it counts against your iCloud storage rather than the developer’s.
The developer operates no server and cannot access the contents of your private iCloud database.

What syncs through iCloud:

Your caffeine log
Your coffee shelf, including bag photos
Your saved brew recipes

What stays on the device only (never sent to iCloud):

Your detox plan and withdrawal symptom log
Your metabolism profile
Appearance, daily limit, and reminder settings
Drink order and brew timer state

You can turn off syncing by signing out of iCloud, or by disabling iCloud Drive for Doppio in iOS Settings → [your name] → iCloud.

4. Analytics

Doppio uses Firebase Analytics, provided by Google LLC, to understand general app usage and improve the product.

Analytics is turned off by default. No analytics events are sent until you explicitly enable it in:

Doppio → Settings (gear icon on the Home screen) → Privacy → Analytics

When analytics is disabled, Doppio sends no analytics events and Firebase collection stays switched off. The app functions identically either way.

When analytics is enabled, Firebase may also collect, for its own operation:

A device identifier (not the advertising identifier; Doppio does not access the advertising identifier and does not ask to track you).
Coarse, city-level location derived from your IP address.
Product-interaction and diagnostic data associated with the events described below.

Doppio does not use Firebase Crashlytics or any other crash-reporting service. There is no automatic crash or stack-trace upload.

Firebase’s use of data is governed by Google’s privacy terms, including:

5. What Analytics Events Include

When analytics is enabled, Doppio sends limited usage and operational events to measure feature usage, app flows, subscription state, and technical errors.

Screen and Navigation Events

The name of a screen you view (for example: home, history, sleep, detox, settings, brew, add caffeine, coffee shelf, day detail, onboarding, metabolism profile — this list is not exhaustive).
The selected tab name and the chart time window you choose.

Settings Events

Whether a setting was enabled or disabled — for example daily limit, daily reminder, evening check-in, detox notifications, sleep suggestion, coffee-freshness alert, HealthKit sync, sleep sync, circular timer display, or automatic brew logging.
The selected theme name and the selected separated-tab preference.

Onboarding Events

Whether onboarding started, was declined, or was completed.
Whether the optional fourth onboarding question was answered.
The question number for answered or skipped onboarding questions.
The onboarding step a user navigated back from.
Whether an onboarding suggestion was toggled, and which suggestion field was applied (such as daily limit or minimum threshold).

Doppio does not send onboarding answer values such as metabolizer type, sensitivity level, caffeine half-life estimate, or other health-profile answers.

Caffeine Events

That a caffeine entry was added, edited, or deleted.
For added entries, whether the entry was synced to Apple Health.

Doppio does not send drink names, caffeine amounts, timestamps, or notes.

Brewing and Saved-Recipe Events

That a brew was calculated, a brew timer started or stopped, or a brew was saved to the log (with whether it was synced to Apple Health).
That a saved brew recipe was created, started, deleted, or set as the favorite, and the source a recipe was started from (app, widget, or Siri).

Doppio does not send brew method, caffeine amount, dose, ratio, grind, roast, timer duration, or notes.

Detox and Withdrawal Events

That a detox plan was created, paused, resumed, cancelled, completed, or reset.
For pause, resume, cancel, and completion events, general progress values such as the current day number or total number of days.

Doppio does not send the starting caffeine target, ending caffeine target, reduction curve, symptom type, symptom severity, symptom notes, or caffeine log details.

Symptom Events

That a symptom was added or deleted.
For added symptoms, whether the symptom was synced to Apple Health.

Doppio does not send symptom type, severity, duration, timestamp, or notes.

Coffee Shelf Events

That a coffee product was added, edited, or deleted. For added products, the roaster/manufacturer name you entered (truncated) and whether the coffee is whole bean, are included.
That a brew was rated, including the numeric 1–5 rating and the screen it was rated from.

Doppio does not send the coffee’s own name, your notes, blend ratio, or the bag photo.

Sleep and Streak Events

That the sleep insights screen was viewed.
When a sleep-based morning suggestion is scheduled: a one-word tone label and your derived sleep score for the night (an integer from 0–100).
When you reach an under-limit streak milestone: the number of days.

Doppio does not send sleep start/end times, sleep stages, or sleep durations.

Drink Management Events

That a drink was hidden, shown, reordered, or that the drink list was reset.

Doppio does not send the drink name.

Subscription and Purchase Events

That the subscription system was initialized.
That a product fetch from the App Store started, succeeded (with whether any products were returned and how many), or failed (with a technical error message, code, domain, and type).
That a purchase started, succeeded (with whether Pro access is now active), or failed (with a technical error message).
That a restore-purchases action started, succeeded, or failed.
That the Pro entitlement status was updated (active or not, and the source).
That the Pro upgrade screen was shown or dismissed, and which surface it was shown from (Settings, the one-time post-onboarding screen, or a specific locked feature).
That a locked Pro feature was reached (with the feature’s identifier).

These events may include the App Store product identifier and a technical error message, code, domain, or type. They do not include payment details, your Apple Account, caffeine logs, HealthKit data, symptoms, notes, drink names, or onboarding health-profile answers.

Error Events

Doppio may send technical error events to help diagnose app problems. Error events may include:

An error category, such as HealthKit, sleep data, notification, SwiftData, widget, or network.
An error message and error type.
A general operation label, such as storekit_purchase or storekit_restore_purchases.

Error events are intended for technical diagnostics. Doppio does not intentionally include caffeine logs, notes, HealthKit data, symptom details, or personal messages in error events.

6. What Analytics Events Do Not Include

Doppio analytics events do not include:

Caffeine amounts, drink names, or caffeine log notes
Brew parameters or brew notes
The coffee product name, coffee notes, or bag photos
Symptom type, severity, or notes
HealthKit data
Sleep start/end times, sleep stages, or sleep durations
Onboarding health-profile answers (metabolizer type, sensitivity level, half-life estimate)
Detox plan targets or reduction curves
Personal account information, email address, or name
The advertising identifier
Payment card or Apple Account details

Doppio does not use analytics data for advertising, and does not track you across other companies’ apps or websites. The app’s privacy manifest declares no tracking, and Doppio does not present the App Tracking Transparency prompt.

7. In-App Purchases and Subscriptions

Doppio is free to download and use. Some features require Doppio Pro, offered as an auto-renewable yearly subscription or a one-time lifetime purchase. A free introductory trial may be offered on the yearly subscription; any such trial is configured in the App Store, and its terms are shown to you before you confirm.

All purchases are processed by Apple through the App Store. Doppio uses Apple’s StoreKit directly and no third-party purchase or subscription service. The developer does not process or store your payment details.

To determine whether you have Doppio Pro, the app reads Apple’s on-device record of your completed transactions (Transaction.currentEntitlements). This is a local check on your device; it is not a network request to the developer, and it does not create any account or user identifier.

You can manage or cancel a subscription in your Apple Account subscription settings. Apple processes purchase and subscription transactions according to Apple’s own privacy terms.

8. Widgets and App Extensions

Doppio’s Home Screen widget, Control Center controls, and brew timer Live Activity may display information from your caffeine log, saved brew recipes, or brew timer state.

This data is shared between the main app and its extensions using Apple’s App Groups mechanism, which is private on-device storage. No caffeine logs, coffee data, symptoms, notes, or HealthKit data leave your device through widgets or Live Activities.

9. Notifications

If you enable notifications, Doppio may schedule local notifications such as daily limit alerts, a daily reminder, an evening check-in, detox reminders and targets, a sleep-based morning suggestion, a coffee-freshness alert, and brew timer completion.

Notifications are scheduled on your device using Apple’s UserNotifications framework. Notification content is not sent to the developer or to Firebase.

10. On-Device Intelligence

To phrase the bedtime caffeine advice in natural language, Doppio may use Apple’s on-device foundation model (Apple Intelligence), where the device supports it. This runs entirely on your device. Only a short summary of the already-computed advice is given to the model, and nothing is sent to Apple or any other server. If the on-device model is unavailable, Doppio shows a fixed, pre-written version of the same advice.

11. Support Communications

If you email support or use “Send Diagnostics Report” in the app, the message you send may include your app version, iOS version, device model, and a summary of your Doppio Pro entitlement state (such as App Store product identifiers and whether Pro is active). These reports are generated only when you choose to send them, and they are sent by your own mail app to the address shown. They do not include your caffeine logs, Health data, or notes.

12. Data Retention and Deletion

Local App Data

You can delete Doppio’s on-device data by uninstalling the app. This removes local SwiftData records, local preferences, and App Group data on that device.

iCloud Data

Deleting a caffeine entry, coffee product, or saved brew recipe in the app removes it from your private iCloud database, and that change propagates to your other devices. Uninstalling the app on one device does not by itself delete the data already synced to iCloud or present on your other devices; sign out of iCloud or manage Doppio’s data in iOS Settings → [your name] → iCloud → Manage Account Storage to remove it.

HealthKit Data Written by Doppio

Open the Apple Health app, find the relevant category (Caffeine or Headache), and delete entries there. You can also revoke Doppio’s Health permissions in iOS Settings.

Analytics

Turn off analytics in Doppio → Settings → Privacy → Analytics. Disabling it stops all future Firebase Analytics collection from Doppio. Because analytics events contain no personally identifying information, they are anonymized and aggregated and cannot be tied back to an individual for deletion.

13. Children’s Privacy

Doppio is not directed to children under 13. Doppio does not knowingly collect personal information from children. If you believe a child has provided personal information through the app or a support request, please contact us and we will address it.

14. International Processing

Firebase Analytics (Google LLC) may process data in countries outside your country of residence, according to Google’s own privacy and data-processing terms.

iCloud data is handled by Apple in your private iCloud account and is governed by Apple’s privacy terms.

Your on-device data — caffeine logs, coffee data, brewing data, symptoms, notes, and preferences — remains on your device and in your private iCloud unless you choose to share it through Apple Health, widgets, device backup, screenshots, support messages, or other actions outside Doppio.

15. Changes to This Policy

This Privacy Policy may be updated from time to time. If the policy changes materially, the updated version will be published at this URL with a revised “Last updated” date. Continued use of Doppio after an updated policy is published means you accept the updated policy.

16. Contact

If you have questions about this Privacy Policy or your data, please contact:

📧 dev@codingfactory.xyz

Doppio is developed by Mobile Coding Factory. It is an independent app and is not affiliated with Apple Inc., Google LLC, or Firebase.