AudioRun Privacy Policy

Effective date: 2026-08-07 (beta)

AudioRun is a running tracker with voice announcements and optional AI coaching, developed by an independent developer. Contact: mail@mjones-foui.no

This policy describes what data the app handles, where it goes, and what stays on your device. AudioRun has no user accounts, no ads, and no analytics or crash-reporting SDKs.

Data stored on your device

All of the following is stored locally on your phone and is never sent anywhere by default:

• GPS routes — precise location recorded while you track a run (the app does not access location in the background; tracking runs as a visible foreground service you start and stop).
• Heart rate — readings from a Bluetooth or ANT+ sensor you choose to connect.
• Run statistics — distance, pace, duration, elevation, splits, personal records.
• Runner profile — age, gender, fitness level, and maximum heart rate, if you choose to enter them.
• Settings — including your Strava connection tokens, which are stored encrypted and are excluded from device backups.
• An installation identifier — a random number the app generates for itself the first time it needs one. It is not your device's ID, is not linked to you or to any account, and is used only to count coaching requests per installation (see below). Reinstalling the app produces a new one.

Your run database and settings (but not Strava tokens or API credentials) are included in Android's standard app backup (Google Auto Backup), which is encrypted and managed by Google — the developer has no access to it.

AI coaching (optional, off until you consent)

If you enable AI coaching and accept the in-app privacy notice, the app sends the following to OpenRouter (openrouter.ai), the AI provider that generates coaching messages:

• current run statistics (distance, pace, duration, heart rate and heart-rate zone, elevation gain),
• your runner profile (age, gender, fitness level, max heart rate),
• short summaries of your recent runs (distances, paces, average heart rates, personal bests),
• your training goal for the run, if set.

Raw GPS coordinates are never sent to the AI provider — only derived statistics. Requests are processed to generate a response and are subject to OpenRouter's privacy policy. Coaching is entirely optional; declining consent keeps the app fully functional with runs stored on-device only.

How the request travels. Coaching requests do not go to OpenRouter directly. They pass through a relay server operated by the developer, which adds the developer's OpenRouter credentials and forwards the request unchanged. This exists so that the credentials are not shipped inside the app, and it has a privacy side-effect in your favour: OpenRouter sees the relay's network address, not yours.

The relay is a pass-through, not a store:

• The contents of coaching requests and responses are never written to disk or logged. They exist only in memory for the seconds the request takes.
• What is kept is a count — how many requests an installation identifier has made recently, and the total monthly cost — so that a fault or misuse cannot run up an unbounded bill. Counters for an installation are deleted after two days of inactivity.
• As with any web request, the server's standard access log records the connecting IP address and the time. Nothing about the run, the profile, or the coaching text appears in it.
• The installation identifier stops at the relay; it is never passed on to OpenRouter.

Weather (optional, off without consent)

If weather is enabled (on by default once you accept the in-app privacy notice), the app sends your approximate location — rounded to about 1 km — to OpenWeather (openweathermap.org) once at the start of each outdoor run, to record the conditions (temperature, humidity, wind, sky) for that run. Your precise GPS position is never sent; indoor runs send nothing. The returned conditions are stored only on your device as part of the run. Requests are subject to OpenWeather's privacy policy. You can turn weather off anytime in Settings.

Strava (optional, user-initiated)

If you connect a Strava account (via Strava's own login page — AudioRun never sees your Strava password) and press upload on a run, the app sends that run to Strava (strava.com): the full GPS route, timestamps, heart-rate data, and the run name/description you chose. Uploaded activities are governed by Strava's privacy controls and privacy policy; their visibility follows your Strava account's default activity-privacy setting. You can disconnect Strava at any time in Settings, which revokes the app's access.

Map tiles

The in-app map loads tiles from OpenFreeMap (tiles.openfreemap.org). Like any web request, this exposes your IP address and the map area being viewed to the tile server. No account or identifier is attached.

What the app does NOT do

• No advertising, no ad SDKs.
• No analytics, tracking, or crash-reporting services.
• No sale of data, and no sharing with anyone beyond the four services named above (OpenRouter, OpenWeather, Strava, OpenFreeMap). The coaching relay is the developer's own server, not a further recipient of your data.
• No background location access — location is only used while a run is actively being tracked with a visible notification.

Data retention and deletion

Everything lives on your device: deleting a run in the app deletes it permanently (including its route, heart-rate data, and coaching log), and uninstalling the app deletes all locally stored data. Data you uploaded to Strava is managed through your Strava account.

The developer runs one server — the coaching relay described above — and it holds no copy of your runs, profile, or coaching messages: only request counts, which expire after two days of inactivity, and a monthly cost total. There is nothing there to delete on request, and no account to delete it from. Because uninstalling the app discards the installation identifier, even those counters lose any connection to you.

Permissions

• Location (precise) — required, to record your run route while tracking.
• Nearby devices / Bluetooth — optional, to connect a heart-rate sensor (declared as never used for location).
• Notifications — optional, to show the run-in-progress notification and its pause/stop controls.

Children

AudioRun is not directed at children under 13 and does not knowingly collect data from them.

Website beta signups

While AudioRun was in closed beta, this website accepted beta invite requests. Email addresses submitted there were stored on the site's web server and used only to send a Google Play testing invite. Nothing else was recorded with them, they were never shared, and they can still be deleted at any time by writing to the contact address above. The site no longer accepts signups; testing is now open, so you can join directly on Google Play.

Changes

Material changes to this policy will be published at this address and noted in the app's release notes.