Simple Fasting Get the app

Effective July 23, 2026 · Version 1.0

Privacy Policy

Simple Fasting is built so fasting information can remain on your device. This policy describes the current app and website, what information may be handled, and the choices available to you.

1. Scope and provider

This policy applies to the Simple Fasting mobile app, simplefasting.app, and messages sent to Simple Fasting support. “Simple Fasting,” “we,” and “us” mean the developer or legal provider identified in the applicable app-store listing.

The current app is local-first, requires no account, and has no Simple Fasting cloud backend. This policy does not apply to app stores, operating systems, email providers, hosting providers, export destinations, or third-party websites, which operate under their own policies.

2. Information stored in the app

The app stores the information needed to provide its features locally on your device:

  • Active and completed fasting sessions, including dates, start and end times, and durations.
  • Fasting goals and optional notes you enter.
  • Reminder, appearance, accent, widget, and Live Activity preferences.
  • Statistics and streaks derived locally from fasting history.
  • Local storage metadata needed to validate and maintain app data.
  • A limited local diagnostic log when storage initialization, reminder restoration, or app rendering fails.

This information is used on your device to operate the timer, history, statistics, local notifications, supported widgets, optional iOS Live Activities, settings, and exports. We do not intentionally receive this local app information.

Depending on your operating-system and device-backup settings, Apple, Google, or your device provider may include app data in a device backup. We do not control those backups.

3. Analytics and native crash reporting

The current app does not provide free or paid accounts and does not use an analytics SDK. We do not collect product events, create an installation identifier, build an analytics profile, use advertising identifiers, perform cross-app tracking, or transmit local fasting history to an analytics backend.

Crash and performance information may be collected by Apple App Store Connect and Google Play Console as part of their native platform services when you install the app through those stores and your device or store settings allow this reporting. Those platform reports can include technical information such as app version, operating-system version, device model, crash type, stack trace, crash-free sessions, crash-free users, ANRs on Android, and related diagnostic metadata controlled by Apple or Google.

Simple Fasting does not add PostHog, Sentry, or another third-party analytics or crash-reporting SDK in the current app. Platform-native reports are provided by Apple or Google under their own privacy controls and policies. We use available store crash information only to improve reliability and do not use it for advertising, cross-app tracking, behavioral profiling, or health-data analysis.

We do not intentionally send fasting dates, times, durations, history, goals, notes, reminder schedules, export contents, email addresses, names, phone numbers, contacts, GPS location, addresses, advertising identifiers, or health data through analytics or crash reporting.

We do not sell personal information. We do not share personal information for cross-context behavioral advertising or targeted advertising. We do not use local fasting information to advertise to you, determine insurance or employment eligibility, or build a profile about you.

Because the app does not send local fasting information to us, we cannot view, recover, remotely delete, or respond to access requests for data that remains only on your device.

4. Website and technical delivery data

The website is deployed as a static Cloudflare Pages site. Simple Fasting does not directly collect visitor information through its website code and does not intentionally use analytics cookies, advertising pixels, fingerprinting, or account cookies.

Cloudflare and other network providers necessarily process ordinary request data to deliver and protect the website. This can include IP address, user agent, requested URL, referring URL, timestamps, approximate region derived from an IP address, and security or error logs. Cloudflare may make limited customer logs available to us and may retain information under its own terms and privacy policy.

If technical delivery logs are available to us, we use them only as needed to deliver, secure, troubleshoot, and maintain the website, comply with law, and prevent abuse. We do not use them to track activity across unrelated websites or apps.

5. Emails and support

If you email support or report a bug, we and the relevant email providers process your email address, message, attachments, and other information you choose to send. We use it to respond, investigate issues, provide support, protect the service, and keep records when reasonably necessary.

Email is not a secure channel for sensitive health information. Do not send fasting history, medical records, passwords, government identifiers, payment information, or other information that is not needed to resolve your request.

Support messages are kept only as long as reasonably needed for the request, security, legal obligations, and legitimate recordkeeping, then deleted or de-identified where practicable. You may ask us to delete a support conversation, subject to legal and security retention requirements.

6. Permissions, notifications, widgets, Live Activities, exports, and diagnostics

Notification permission is requested only when you choose **Allow Notifications** in onboarding or enable reminders from Settings. If you allow it, the fast-end reminder is enabled by default while the optional daily reminder remains off until you enable it. If you choose **Not Now** or deny permission, reminder controls remain unavailable unless you later allow notifications in system settings. Notifications are scheduled locally through the operating system. Supported widgets and optional iOS Live Activities receive the limited local fasting state needed to display them on your device, including on the Lock Screen or Dynamic Island where available.

The app stores whether onboarding was completed and whether the notification prompt was shown, but it does not store a separate “notifications enabled” value. Notification availability is read from the operating system because you can change it in device settings. Denying optional permissions may disable the related feature but does not prevent basic local fasting tracking.

Exports are created only when you request them. An export leaves the app when you choose a destination through the operating-system share sheet. You are responsible for the destination, recipients, security, and later deletion of exported files.

When certain app errors occur, Simple Fasting may keep up to 50 recent diagnostic events in local app storage. A diagnostic event can include its time and category, a sanitized error name and message, limited component context, app version, build version, and platform. The diagnostic report is designed not to include fasting history, goals, notes, settings, account identifiers, advertising identifiers, or device identifiers. Potential email addresses, web addresses, and local file paths in error text are redacted where recognized, but you should still review a report before sharing it.

The local diagnostic log is separate from Apple and Google platform crash reporting. It remains on the device until removed by the rolling limit, app-data clearing, or uninstall behavior. Its optional JSON report leaves the app only when you choose a diagnostic action inside Report bug, such as emailing it through a native mail composer or selecting a destination in the operating-system share sheet. If you attach it to an email, the email practices in Section 5 apply.

8. Retention, deletion, and your controls

You control information stored by the app and can:

  • Edit or delete completed fasting sessions.
  • Export app data in JSON or CSV format.
  • Clear local app data from Settings.
  • Remove app data by uninstalling the app, subject to operating-system backups and retention behavior.
  • Disable notifications or Live Activities, or remove widgets through app or device settings.
  • Review and explicitly share a local diagnostic report; clearing app data also clears local diagnostics.

Clearing or uninstalling may be irreversible. Create and safely store an export first if you need a copy. We cannot restore information that was never transmitted to us.

9. Privacy rights

Depending on where you live, you may have rights concerning personal information we actually hold, such as access, correction, deletion, restriction, objection, portability, withdrawal of consent, or appeal. You may also have the right to complain to a local privacy or data-protection authority.

Send a request to [email protected]. We may need to verify the request and may retain limited information where permitted or required by law. These rights do not let us access or delete local app data that we do not possess.

Residents of U.S. states with applicable privacy laws may also request information about collection, use, disclosure, sale, or sharing. For the current service, we do not sell personal information or share it for cross-context behavioral advertising, and we do not offer a financial incentive for personal information.

10. Security and incidents

We use a local-first design and reasonable safeguards appropriate to the information we handle. No device, email system, network, or storage method is completely secure. Protect your device with system access controls, keep it updated, review notification and widget visibility, and store exports securely.

If an incident involving information held by us requires notification under applicable law, we will provide the required notices. A compromise of your device, personal backup, email account, or chosen export destination is generally outside our control.

12. International processing

Apple, Google, Cloudflare, other network providers, and email providers may process technical or support information in countries other than your own. Those countries may have different privacy laws. Where required, providers and we must use recognized safeguards for international transfers.

Fasting history, goals, notes, settings, and other local app content remain subject to your device, platform, backup, and export choices and are not intentionally transferred to us through analytics or crash reporting.

13. Product boundaries

Simple Fasting does not include or plan accounts, synchronization, paid features, health integrations, analytics SDKs, or a Simple Fasting backend.

Before any new feature begins collecting or transmitting information in a materially different way, we will update this policy, describe the relevant data and purposes, and request permission or consent where required.

We will not silently turn existing local-only fasting information into remotely collected information.

14. Changes and contact

We may update this policy to reflect product, legal, security, or operational changes. We will publish a new version and effective date. If a change is material, we will provide additional notice in the app, on the website, or through another appropriate channel before or when the change takes effect where reasonably possible or legally required.

Continued use after an effective date is subject to the updated policy, but consent will be requested separately when law requires it. Earlier app releases retain the policy copy bundled with that release unless updated.

Privacy, support, and rights requests can be sent to [email protected]. Bug reports can be sent to [email protected].