Privacy · Updated October 8, 2026

Your running history
stays with you.

RunFit analyzes and stores your runs on your device. Here’s what that means—and what connecting services involves.

Your runs and analysis.

Your imported runs, workout analysis, heart-rate settings and goals are stored in the browser on your device. RunFit does not keep a server-side database of your activity history.

File imports are processed locally and are not uploaded to RunFit. The app retains the local information needed to display and analyze your runs. An imported archive does not become a cloud backup.

RunFit does not sell your activity data or use it for advertising. The app does not use advertising cookies.

RunFit counts daily and weekly active devices and clicks on the Ko-fi support button using a randomly generated identifier. No runs, scores, athlete identifiers or analytics IP-address records are stored with these counts.

Your browser keeps a random analytics identifier and sends it with analytics events. The server stores temporary hashes of that identifier for deduplication within the current day or week, plus aggregate counts covering about one year. It does not store the original identifier in the analytics database. Expired hashes and counts are removed on the next analytics collection or reporting request. Clearing browser site data removes your local analytics identifier.

What connecting Strava involves.

Strava sends the activity data you authorize through RunFit’s connection service to your browser. That service handles authorization and requests needed to sync your runs.

RunFit stores encrypted Strava access credentials and connection information so the connection can continue. It also keeps account and browser identifiers, the time each browser last used the connection, and activity-change information needed for notifications and request limits. Pending notifications may include an activity identifier, title, activity type or privacy change. They are removed after the receiving browser acknowledges them. A connection cookie identifies your browser’s authorized session.

Strava sync covers the last 24 months.

RunFit does not request GPS streams from Strava. Activity summaries and details returned by Strava may nevertheless contain coordinates or map information; those responses pass through the connection service to your browser. RunFit does not store them in its server database. Files you choose to import may contain location information; their contents are processed locally. Strava and the hosting provider also handle the network requests needed to deliver the service.

If a browser has not used RunFit’s Strava connection for more than 400 days, RunFit normally removes its server-side connection data and pending notifications during monthly cleanup. When no browser connections remain for your Strava account, RunFit removes the stored Strava credentials and account connection data. Outdated activity-change information is also removed during monthly cleanup. Your running history stays on your devices.

When you contact support.

The email address, subject and message you submit are sent to RunFit support using Resend’s email service. Cloudflare Turnstile checks submissions for abuse. Your message is not public; it is used to respond to your request.

Support emails and correspondence are kept for as long as needed to handle support. You can contact support to request deletion of your correspondence or server connection information. Local running history is managed using the controls on your own device.

Please share only what is needed for help. Do not send credentials or a full activity archive.

You control your local copy.

On the Data page, you can export a RunFit backup, delete older history, or delete local app data. Browser cleanup or clearing site data can also remove local history. A backup you save is your responsibility to keep safe.

Disconnecting Strava gives you a choice: retain a local copy or remove Strava activities from RunFit on this device. RunFit immediately removes its server-side Strava credentials, account and browser connection records, pending notifications, and related request-limit identifiers. This ends the connection for your other RunFit browsers as well; their local copies remain on those devices. Neither choice deletes activities from Strava. RunFit also attempts to revoke the Strava grant; if that cannot be confirmed, check access in your Strava settings.

Deleting local data while offline cannot immediately contact the connection service. RunFit records a pending disconnection and retries it when you return online. The server’s inactivity cleanup also applies to unused browser connections.

Requesting persistent storage asks your browser to protect local data from automatic cleanup. It does not upload your data or guarantee that it cannot be deleted.

Services you may use.

Cloudflare hosts RunFit and handles ordinary connection information such as IP addresses and request metadata. Strava handles your Strava account and activity access. Support submissions use Cloudflare Turnstile and Resend. If you choose to support the project, Ko-fi handles that visit and any payment.