At a glance
Fastyra does not collect or transmit your fasting records to the developer. Plans, times, meals, sessions and preferences are processed locally to provide the features you choose.
Last updated: 25 August 2026.
Privacy policy
Fastyra is designed to work without an account, advertising profile, developer backend or tracking.
No registration, login or personal profile.
No ads, IDFA or third-party analytics SDKs.
Your full history remains on your iPhone.
Fastyra does not collect or transmit your fasting records to the developer. Plans, times, meals, sessions and preferences are processed locally to provide the features you choose.
Last updated: 25 August 2026.
This policy describes data processing performed by the Fastyra iPhone app, its widgets and its companion app for Apple Watch. It does not cover data processing performed independently by Apple or by a website you choose to open under its own terms.
Fastyra may store the following information locally because you create or configure it:
Fastyra does not ask for weight, age, sex, calories, location, contacts or Health data. It does not create a clinical or advertising profile.
Fastyra has no user account or developer backend. It contains no advertising, third-party analytics, tracking, IDFA integration or CloudKit synchronization. The app’s privacy manifests declare no tracking and no data collected by the developer.
The widget and Watch keep only the local snapshots, preferences and bounded command records needed for these features. None of this information is sent to a Fastyra server.
You can create a JSON backup or export fasting sessions as CSV. A file leaves Fastyra only when you choose a save location or share it through the system sheet. After that, the file is under your control and the privacy terms of any service you select; Fastyra cannot delete copies stored elsewhere.
The Learn section contains optional links to external educational sources. Opening one launches the destination through the system. That website may receive ordinary web-request information, such as your IP address, under its own policy. Fastyra does not add your fasting history or an advertising identifier to the link.
Local information remains until you edit or erase it. In Fastyra you can correct or delete individual history entries, export a backup, restore a supported backup, or choose Erase all data. Full erasure removes the plans, history, preferences, local companion state and notifications controlled by Fastyra, then returns the app to its welcome setup.
Because Fastyra has no account or backend, the developer cannot view, recover or synchronize records from your device. Keep your own JSON backup before deleting the app or changing devices if you want to retain the history.
The only permission expected in version 1.0 is notifications, and the app’s core timer and history continue to work if you decline it. Fastyra relies on Apple’s app containers and system frameworks to separate its local data from other apps. Protecting access to your unlocked device and to files you export remains your responsibility.
Apple may independently process App Store purchases, downloads, device diagnostics or system services under Apple’s privacy terms. That processing is not performed by Fastyra’s in-app data store and does not give Fastyra an account containing your fasting history.
If Fastyra’s data practices change, this page and its update date will be revised before a release that relies on the change. A future feature that collects or transmits data would require a new review and a clear disclosure.
See the Fastyra support page for practical instructions on exports, erasure, notifications, widgets and Apple Watch. Fastyra cannot inspect your local records remotely.
For a privacy question, open a request on GitHub. GitHub issues are public, so do not include fasting history, exported files, health information or other sensitive data.