Privacy Policy

Last updated: October 24, 2026

About this policy

DeCaf is operated by Tom McLaughlin, operating DeCaf as a sole proprietor. This policy describes information handled by DeCaf for iOS, Android and related services. For privacy questions or deletion requests, contact support@decaff.app.

Information handled by DeCaf

  • Your entries: drink names, caffeine amounts and times; bedtime settings; daily goals and taper plans; and optional sleep check-ins, including the date, a rating from 1 to 5 or a skipped entry. Manual sleep ratings are entered by you and remain separate from optional imported sleep records described below.
  • Preferences: reminders, notification history and saved drink favorites. The app also keeps data on your device.
  • Your account: email address, account identifiers and authentication information. The server stores a password hash rather than your plain-text password.
  • Optional account activity in the forthcoming iOS update: after you confirm the setup choice or enable Share app activity in Settings → Data & privacy, DeCaf sends app opens and broad feature actions to its own server, linked to your signed-in account. This is available to free and Pro users independently of Cloud Sync. Events include a random event identifier for duplicate prevention, event time, a session identifier, platform and app version/build. They exclude dose amounts, health and sleep values, journal entries, messages and location. No optional account activity is collected before confirmation. Your choice applies to this account on this device; prior opt-outs stay off. Turning it off stops new optional account activity collection and clears unsent activity; a request already received by the server may remain. Previously sent events remain until account deletion, which removes this new activity stream. No advertising or third-party analytics SDK is used.
  • Expanded focus and widget activity in a forthcoming update: a separate, fresh confirmation for your signed-in account on this device will be required before collecting these additional interactions. An earlier broad app-activity choice does not enable them, and earlier opt-outs remain off. If you agree, DeCaf records whether you save, edit or undo a drink, check-in or sleep-timing entry; whether an action starts in the app, a widget or a notification and where it completes; which focus you view or select (sleep, energy, anxiety, workouts, reduction or just tracking); and interactions with findings, evidence views, suggestions and related notifications. Activity includes random event and interaction identifiers, times, app version and a session or execution-context identifier. Widget and background actions are distinguished from app sessions. It does not include Health values, drink amounts, ratings, sleep times, journal contents, messages or notification text. Creating a notification does not establish that it was delivered or read; a later recorded action does not prove that a suggestion caused it. Unsent activity is limited to 500 events and seven days, and is cleared when you turn sharing off, sign out or change accounts. Only events matching the current account and consent choice may be sent. Turning sharing off stops new collection; activity already received follows the account-activity deletion rules above.
  • Earlier anonymous product counts: earlier iOS builds offer Help improve DeCaf, off by default, to send generic feature counts without account, session or device identifiers. These are combined by UTC day and build and cannot be individually removed. The forthcoming account-activity update stops sending this earlier stream. Existing historical analytics and invitation totals remain separate.
  • Invitation measurements: the service counts links created, valid invitation-page opens and new accounts successfully created through an invitation. An invitation token is sent in the request body to validate the measurement, then discarded from the measurement; counters store only day, metric, platform, build and count. Counts are not unique people or guaranteed complete attribution. Ordinary account/authentication and security handling remains separate.
  • Support: your email address and information you choose to include in a support message.
  • Purchase information, where applicable: product, provider, transaction identifiers, dates and entitlement status. Restoring or verifying an existing store purchase can send a signed transaction to DeCaf to verify account access, even while new purchases are unavailable. Payment providers handle payment card details; DeCaf does not receive your payment card number.

Optional Cloud Sync and server reports

When you enable Cloud Sync for an eligible account, DeCaf stores supported entries under your account: drink names, caffeine amounts and times; bedtime settings; goals and taper plans; manual sleep ratings or skipped check-ins; notification history; and supported favorites and reminder preferences. Cloud Sync does not upload your device-only imported Health records, private drink photos or private café visits.

The admin dashboard uses retained server records for account support and operational reports, including recorded caffeine amounts and times, bedtime distributions, configured goals and taper plans, and purchase-access counts. These reports use account-linked records; an aggregate display does not make the underlying records anonymous. They are separate from the optional app-activity stream. Turning off Share app activity does not erase synced records or stop these existing reports. Turning off Cloud Sync stops future synchronization; it does not itself delete records already stored on the server.

Bean Brigade and deliberate sharing

If you use Bean Brigade, DeCaf stores your chosen display name, connections and group membership to provide the feature. This is an in-app social graph, not access to your phone address book. Posts, captions, private messages and comments, shared photos, reactions and read states are stored with the relevant account and audience. A structured progress panel can include caffeine amounts and manual sleep ratings when you explicitly choose to share them. A photo selected for a Brigade post is uploaded while preparing it, before publication; keeping a photo only in your private drink log does not upload it.

A shared café visit can include the selected place name, address or catalog map point and the visit date or time you choose to share. This is a place you deliberately identify, not continuous location tracking. If you request optional location verification where available, the server checks a one-time location sample and retains the account, venue and expiring evidence that the sample qualified within five miles. It discards the submitted phone coordinates, accuracy and sample timestamp rather than storing raw GPS history. The selected venue and coarse proximity evidence can remain with your shared visit.

Review the audience before publishing. Private Brigade posts are available to the permitted recipients or groups. Creating a hosted share stores the selected content and makes it accessible through its share link until access expires or is revoked. Recipients can retain copies; deleting a post or revoking a link cannot recall copies already saved or exported. Local private photos, private visits and imported Health records are not automatically added to a shared post.

Optional buddy push notifications

If you enable buddy push notifications on a supported iPhone, DeCaf associates an Apple push token and notification preferences with your account to deliver updates. The server retains a token hash and encrypted delivery target. This device identifier is used for notification delivery, not advertising. Disabling the feature retires its registration; Apple also controls notification permission on your device.

Optional health import

iOS build 56 lets you explicitly request read access to supported Apple Health types: sleep, heart rate, resting heart rate, water, steps and workouts. Apple provides the fine-grained permission choices. Imported records remain local to this device and app account and are excluded from cloud sync and product counters. You may deliberately export a frozen panel image only after choosing the panel, giving consent and selecting an OS sharing destination. Exported images may be saved by the recipient and cannot be recalled. DeCaf does not write records to Apple Health.

This section describes optional Health Connect sleep import in the upcoming Android closed-test build 0.2.26 (38). Availability to eligible testers is pending; this feature is not available in the current Android 37 release. The historical Android release description below does not describe the later iOS Apple Health feature. Public store downloads are not available yet.

If you connect Health Connect, DeCaf requests read-only access to sleep records. This includes record identifiers, sleep and wake times, time-zone offsets, source app identifiers and names, and sleep stages where your source provides them. DeCaf uses these records to show sleep timing, duration and available stages alongside your caffeine entries. You can use DeCaf without connecting a health source. Your manual 1–5 sleep ratings remain separate.

Imported sleep is stored on this device for the current DeCaf account. It is excluded from app backups and is not sent to DeCaf cloud sync or analytics. DeCaf does not write sleep or caffeine records to Health Connect. These statements concern DeCaf’s imported copy; your source app and Health Connect manage their own records.

In the app’s Sleep data screen, choose Disconnect and remove imported sleep to stop importing and remove the saved imported sleep for the current account on this device. If removal fails, the app asks you to retry. This does not delete records from Health Connect or your source app, and does not itself revoke the system permission. Use Manage Health Connect access to change that permission. When DeCaf detects that sleep permission has been revoked, it hides imported records and attempts to clear the saved copy. A storage failure can leave that copy on disk. Detection requires the app to check access; revocation alone does not guarantee immediate erasure. Successful local removal is required to clear the saved copy.

Account-deletion requests

The support form stores your email address, request wording/version and request time on our DigitalOcean-hosted service so the operator can review it. It does not look up whether an account exists, send an email or delete an account. Request records remain stored until removed; they are separate from app-account records. Access to request details is restricted to an authenticated operator. Ownership must be verified before any account deletion.

Optional website analytics

When enabled on this website and you choose Allow analytics, Google Analytics measures visits to our landing page, blog, comparison, privacy, support, terms and Muse pages, referring websites, campaign and ad labels, engagement, scrolling and link clicks. Invitation, welcome and account pages are excluded. Campaign reports associate successful submissions with the session’s source and campaign labels. A successful waitlist submission is counted without sending your email or form contents to Google. Google receives browser/device information and network information needed to deliver its service. Analytics cookies distinguish visits; we configure them to expire after 180 days without extending their expiry on each visit. Advertising personalization and Google signals are disabled.

Before you accept, this integration does not load Google Analytics. Use Analytics preferences at the bottom of the page to decline or change your choice. Declining stops new collection and clears this site's Google Analytics cookies; it does not erase data already received by Google. Your choice is saved in this browser. Website analytics is separate from app activity and Cloud Sync. See Google's privacy policy.

Launch-notification waitlist

If you join the waitlist, we store your email address, optional platform choice, and the wording, version and time of your consent on our DigitalOcean-hosted service. The unchecked consent box asks only for a DeCaf availability notification, not general marketing. Joining does not create an app account or grant testing access. No email is sent when this form is submitted.

We store a keyed digest of the submitting network address to limit repeated waitlist and deletion requests; these website forms do not retain the raw address. Rate-limit counters older than 48 hours are removed when later requests are processed. Your email and consent record remain on the list until removed. To request removal or ask about a saved request, contact support@decaff.app. Requests are not automatically processed by this page.

How information is used

We use this information to provide tracking and account features, process optional cloud synchronization, respond to support requests, verify access to paid features where enabled, and understand and improve product use. Cloud synchronization, where available, depends on your settings and entitlement; it is not a guarantee that every local entry has been backed up. Product interaction analytics are separate from your tracking-data sync setting.

Storage and service providers

DeCaf stores app data locally and operates a self-hosted service on DigitalOcean. Connections to the production service use HTTPS. Account access is authenticated. These protections do not amount to a claim of end-to-end encryption.

Service providers process information needed to operate the service: DigitalOcean provides hosting, and Resend handles transactional account email when enabled. Apple and Google handle their respective app distribution and store services. Stripe handles web payments where those features are enabled. Apple and Google purchases are currently disabled in the beta. Your email provider also handles messages you send to support.

We do not sell your personal information or use it for advertising. Sharing needed to operate these services is different from selling data. Store and payment providers handle their own records under their privacy policies.

Your choices and deletion

You can review and edit your tracking entries in the app. Cloud sync settings, where available, let you control that feature. To request a copy of your data or ask about a stored record, email support@decaff.app; this does not imply an in-app export tool.

On iPhone, you can request account deletion in Settings → Delete Account. The upcoming Android closed-test build 0.2.26 (38) includes Settings → Delete Account; availability to eligible testers is pending. The current Android 37 release does not complete in-app account deletion. For help, use the account-deletion request form. A saved request does not confirm that an account exists or delete it. Ownership must be verified before any account deletion. Successful account deletion removes the account and its server-side tracking and sync records. Some analytics, audit and transaction records can remain after their direct database account association is removed. Retained event properties and audit details may still contain identifiers; removing the account link does not necessarily anonymize those records. Deleting an account does not itself cancel a store subscription or erase records held by a store, payment provider or an email recipient.

For questions about retained records, backups or a specific deletion request, contact support. We do not promise that all copies in every system disappear immediately.

Children’s privacy

DeCaf is not intended for users under the age of 13. We do not knowingly collect personal information from children.

Policy updates

Updates will be posted here with a revised date.