Privacy Policy — Fasting Well

Last updated: May 24, 2026

Fasting Well (“the app,” “we”) is built by Generalize LLC (“we,” “us”). This policy describes exactly what data the app collects, what it does with it, and what it does not.

It is written in plain English. If anything here is unclear, email us at hello@fastingwell.app and we’ll fix it.


The short version


What data the app stores on your device

All of this lives in your phone’s local AsyncStorage and never leaves the device unless you choose to share it:

You can wipe all of this in one tap via Settings → Data → Reset everything.


What we send off the device

Anonymous usage analytics (PostHog)

To know what to improve, the app sends a small set of anonymous events to PostHog (a privacy-respectful analytics service, GDPR-compliant). These events describe what action happened — never what value. Examples of what we send:

We never send: your weight value, your fast duration, your mood, your energy, your notes, your custom protocol details, your name, your email, your IP address (PostHog strips IPs by default in our configuration), or any identifier that could be tied back to you.

PostHog issues a random anonymous ID per install that we use to count unique users — but that ID is not linked to any personal information.

To opt out: Settings → Privacy → toggle off Share anonymous usage data. The opt-out takes effect immediately.

Crash and error reports (PostHog Error Tracking)

If the app crashes or throws an unhandled error, we send the error message and a stack trace to PostHog so we can fix it. These reports include code locations but not your fasting/weight/mood data.

This is part of the same analytics opt-out — if you turn off analytics, error reports stop too.

Apple Health / Health Connect (only if you opt in)

If you enable Settings → Health → Sync with Apple Health (or Health Connect on Android):

This data flows between your app and the system’s local health database. It does not pass through any server we operate. You can revoke this permission any time in your phone’s Settings → Privacy & Security → Apple Health (iOS) or Health Connect (Android).

Local notifications

Stage-transition, goal-reached, and eating-window reminders are scheduled with the operating system on your device. They do not round-trip through any server. We do not use push notifications.

Share-card image (only when you tap Share)

When you tap “Share image” on a completed fast, the image is composed entirely on your device. It is only sent anywhere if you explicitly pick an app from the system share sheet. Fasting Well never uploads the image automatically.

Article content (Learn tab)

The Learn articles ship inside the app bundle. Opening an article does not make a network request to us. (Anonymous “article opened” analytics events are sent only if analytics is enabled.)


What we don’t do


In-App Purchases (Pro tier — coming in a future version)

The current version of Fasting Well (v1.0) is free. A future version will add a Pro tier with custom protocols, unlimited history, weight tracking, share cards, and other features.

When Pro launches:

This policy will be updated when Pro ships to fully reflect what RevenueCat receives.


Children’s privacy

Fasting Well is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has used the app, contact us at hello@fastingwell.app and we’ll help.

For users under 18, please consult a doctor before practicing extended fasting.


Your rights (GDPR / CCPA / state privacy laws)

Because we do not have your personal data on any server, there is nothing for us to access, correct, port, or delete on your behalf. All of your data lives on your device under your control.

If you want to:

If you’ve already disabled analytics and want to ask PostHog to delete the anonymous event records that were sent before, email us at hello@fastingwell.app with the request and the approximate dates and we’ll initiate a PostHog deletion on your behalf.


Changes to this policy

If we change anything material in this policy, we will:

  1. Update the “Last updated” date at the top.
  2. Note the change in the app’s “What’s New” release notes for the next version.

If the change affects what data we collect, we will surface a one-time in-app notice before any change takes effect.


Contact