PRIVACY / PLAIN LANGUAGE
Your run is
your data.
Effective 19 July 2026 · Policy version 1.0
RunFasta is local-first. It has no advertising SDK and no RunFasta account is required. Network features are optional, and automatic backup starts only after you choose a destination.
Who is responsible
RunFasta is published by Paema Ideas. For privacy questions or requests, email privacy@runfasta.app. Publisher identity and jurisdiction details will be finalized on this page before the first public Play test.
What the app processes
| Data | Purpose | Default location |
|---|---|---|
| Precise route, time, pace, altitude, cadence, and workout details | Record a workout; calculate live pacing and training history | On your device |
| Heart rate and optional Bluetooth sensor/trainer data | Live effort feedback and post-workout analysis | On your device |
| Health Connect sleep, resting heart rate, steps, and weight | Optional recovery and fitness context | On your device |
| Goals, plans, check-ins, reflections, and profile settings | Personalize planning and show progress over time | On your device |
| Technical diagnostic logs | Troubleshoot failures when you choose to share a log | On your device |
Permissions
Location
Precise location is requested when you record a route. During a workout, a visible Android foreground-service notification keeps tracking active while the screen is off or another app is open. RunFasta does not track location when no workout is active.
Health Connect
With your permission, RunFasta reads sleep sessions, resting heart rate, steps, and weight. It does not write Health Connect records. You can disable sync in RunFasta and revoke individual access in Health Connect. Denial does not prevent ordinary workout recording.
Nearby devices and notifications
Bluetooth permissions support optional heart-rate sensors and compatible bike trainers. Notification permission supports workout controls and optional reminders.
Network requests and third parties
The core recorder and coach rules work without a RunFasta server. When you use the relevant feature, your device may contact:
- OpenFreeMap / MapLibre tiles to display maps. The tile service receives the requested tile area, IP address, and ordinary web-request metadata.
- Open-Meteo for weather or elevation context. Requests include coordinates needed for the lookup and ordinary web-request metadata.
- Your Android document provider, such as Google Drive, only after you select a backup folder.
- User-configured integrations, such as a fitness server or Strava, only in distributions where securely configured and after you initiate or enable them.
Those providers process requests under their own privacy terms. RunFasta does not sell personal or health data and does not use it for advertising.
Exports, backups, and sharing
Manual FIT, GPX, TCX, JSON, and diagnostic exports go to the destination you choose. Files can contain sensitive health information and, where stated in the app, precise routes.
Automatic run backups remove the configured distance from both route endpoints in FIT, GPX, telemetry JSON, and athlete snapshots. The full route remains in the local database. Very short routes are blocked instead of silently uploading untrimmed coordinates. Indoor cycling files have no GPS route.
Retention, security, and deletion
Local data remains until you delete an athlete profile, use the in-app permanent-deletion control, clear app storage, or uninstall RunFasta. Android system cloud backup is disabled. App-private files are protected by Android's application sandbox; no system is immune from compromise, so protect your device and exported files.
Deleting local data cannot delete copies you exported to another app, document provider, or configured integration. Delete those copies at their destination. See Support and data deletion for exact steps.
Children, medical use, and changes
RunFasta is not directed to children. It is a fitness planning tool, not a medical device, and does not diagnose, prevent, or treat disease. Stop exercise and seek qualified care for alarming symptoms.
Material policy changes will update the effective date and, where appropriate, be highlighted in the app before affected network processing occurs.