PureFast Privacy Policy

Private by design. Local by default.

PureFast is built as a local-first intermittent fasting and progress tracking app. This policy explains what the app stores, which permissions it may request, when data leaves your device, and how you stay in control.

App PureFast
Package com.purefast.app
Effective Date May 7, 2026
Support Contact hello@akashsarker.com

Plain-language summary

No account required PureFast does not require sign-up, email registration, or a cloud profile to use core features.
No ads or third-party analytics PureFast does not include advertising SDKs, third-party analytics, or background marketing trackers.
Health data stays local by default Fasting logs, body measurements, hunger entries, notes, and most settings are stored on your device.
Permissions are feature-based Camera, notifications, biometrics, and location are only used for features you choose to enable.
Exports are user-controlled If you export JSON, CSV, images, or timelapses, those files may be saved or shared outside the app because you asked for it.
Google Play handles billing If you subscribe to PureFast Pro, payment processing is handled by Google Play under Google's policies.

1. What PureFast stores

PureFast stores data on your device so the app can track fasts, show progress, remember your settings, and support optional features like Ramadan timing and progress photos.

Profile and baseline data Age range, biological sex, height, starting weight, target weight, waist measurements, preferred units, and protocol preferences.
Fasting data Fast start and end times, fasting goals, completed duration, protocol mode, notes, edits, and whether a goal was achieved.
Daily check-ins Weight, waist, mood, energy, sleep quality, hunger level, notes, and optional linked progress photos.
Hunger coaching data Hunger wave events, cooldown completion, and related fasting context.
Settings and accessibility data Timer format, haptics, motion preferences, contrast preferences, fasting protocol settings, reminder settings, and biometric lock preference.
Ramadan timing settings Selected calculation method, tuning offsets, Ramadan day count, and locally stored coordinates when you enable Ramadan timing.
Progress photo files Photos captured or imported by you, stored in app-private storage for the Progress Photo feature.
Local backup and export files Encrypted local backup files and user-requested JSON or CSV exports.
PureFast is designed so that core health and fasting records remain on your device unless you explicitly export, share, or back them up outside the app.

2. Permissions and device access

PureFast requests only the permissions needed for features you actively use.

Camera

Used for the Progress Photo Studio so you can capture body progress photos with framing overlay, timer tools, and comparison features.

Notifications

Used to show the active fasting notification, live fasting status, milestone updates, and scheduled reminders such as circadian prompts.

Approximate or precise location

Used only when you enable Ramadan timing so PureFast can calculate local Fajr and Maghrib times for your area. The last known coordinates used for this feature are stored locally in app settings on your device.

Biometric authentication

Used only if you enable biometric protection for private photo access. Authentication is handled by your device's biometric system. PureFast does not receive, store, or process your raw fingerprint, face, or other biometric template data.

Boot completed

Used to restore fasting notifications and scheduled reminders after your phone restarts or after the app is updated.

3. When data leaves your device

PureFast is local-first. In normal use, the app's core fasting and health records stay on your device. Data leaves your device only in the situations below.

Manual export

If you export your data, PureFast creates a JSON or CSV file that may be written to your device's Downloads area. After export, that file is outside PureFast's private storage and may be accessible to other apps or services depending on your device and sharing choices.

Manual sharing

If you share a comparison card, timelapse, or exported file, the content is shared only because you chose to send it through Android's share sheet.

Imported files

If you import a CSV or a past photo, PureFast reads the file you selected. Imported photos are copied into app-private storage. Imported CSV content is used to create fasting records on your device.

Auto-backup

If you enable auto-backup, PureFast creates encrypted local backup files in app-private storage and retains a rolling set of recent backups.

Third-party services you choose

If you use Google Play subscriptions, Android share targets, or other device-level services, those services may process related data under their own privacy policies.

4. Subscriptions and billing

PureFast Pro subscriptions are offered through Google Play Billing. When you choose to subscribe, Google processes payment information, subscription renewals, trial eligibility, and purchase receipts under Google's own terms and privacy policies.

PureFast itself uses billing responses to unlock Pro entitlement status inside the app. PureFast does not process raw credit card data directly.

5. Security and storage protections

PureFast uses device-local storage and platform security features to protect your data.

  • Core records are stored in a local on-device database.
  • Progress photos are stored in app-private storage.
  • Photo path references used by the app are encrypted with Android Keystore-backed cryptography.
  • Local backup files created by the app are encrypted before storage.
  • Biometric lock can be enabled to gate access to private photo flows inside the app.

No security measure is perfect, but PureFast is designed to minimize unnecessary exposure by keeping core data local and avoiding third-party advertising or analytics SDKs.

6. Retention and deletion

Your data remains on your device until you delete it, clear the app's storage, uninstall the app, or overwrite it through your own edits.

  • Local encrypted backups are rotated, keeping only a limited recent set.
  • Manual exports remain wherever you saved them until you remove them yourself.
  • Shared files may remain with the receiving app, platform, or person you shared them with.

7. Your choices and controls

Because PureFast is local-first, many privacy controls are directly in your hands.

  • Edit or delete fasting and log entries inside the app.
  • Disable Ramadan location-based timing, reminders, notifications, or biometric lock at any time.
  • Delete exported files, comparison images, and timelapse files from your device or gallery.
  • Clear app data or uninstall the app to remove local app storage from your device.

8. Children

PureFast is a wellness and fasting tracking app intended for a general audience and is not designed specifically for children. Users should use fasting-related features responsibly and, where appropriate, with guidance from a qualified professional.

9. Future integrations

If a future version of PureFast adds optional integrations that access additional data sources, such as health platform data sharing, those features will require clear in-app permission prompts and this policy will be updated accordingly.

10. Changes to this policy

We may update this Privacy Policy when PureFast adds or changes features, permissions, or data handling behavior. The updated version will show a new effective date at the top of this page.

11. Contact

If you have questions about this Privacy Policy or about PureFast's privacy practices, contact:

PureFast Support
hello@akashsarker.com