Last updated: 2026-06-08
Privacy and Data Policy
Faraway is designed to run locally on macOS and keep usage flow transparent. This page explains what the product currently states and how this is supported.
Short answer: Faraway does not collect app usage telemetry from users, and local reminder settings and logs remain on-device.
What data is handled by Faraway
- Reminder intervals, app-monitoring preferences, and local execution settings are stored on-device.
- Faraway app telemetry is not collected from users; only anonymous website page traffic analytics are in use.
- No user profile content or reminder text is described as being uploaded in product documentation.
Data boundary statement
The local-first model means the app does not send reminder history, timer state, app list, or screen usage logs to a backend service during normal use. The only automatic collection outside the app is anonymous page analytics for marketing-site traffic visibility.
If you file a bug report, only the information you choose to include is sent through the issue tracker (for example, macOS version, Faraway version, and reproducible steps).
How releases and fixes are published
Release binaries and notes are published in the source repository and issue tracker. Use these URLs for verifiable references:
Privacy FAQ
What data does Faraway keep on-device?
Reminder schedules, interval settings, and local execution state stay on-device. The app does not send usage telemetry in normal reminders.
What data leaves Faraway during issue reporting?
Only user-chosen bug details (for example, macOS version, app version, reproducible steps) are shared through the repository issue tracker.
Contact
If you identify a bug, attach logs if available and report in the repository issue tracker.