Back to RunHunch

Privacy

Last updated 17 November 2026

RunHunch uses your information to show your training, build running plans and help you learn from your activities. This page explains what is processed and how to request access or deletion.

Who is responsible?

The data controller for RunHunch is Potone Invest AS, organisasjonsnummer 936116183.

Contact: privacy@runhunch.com.

What information is processed?
  • Account and profile: email, your name if provided, sign-in information, language, time zone, maximum heart rate and heart rate zones.
  • Goals and plans: race goals, dates, target finish time, training volume, available training days, planned workouts and your changes.
  • Activities: time, duration, distance, pace, heart rate, intervals, elevation, power and running dynamics, where available in the file you import.
  • Original files: The FIT file is kept so activities can be analysed again. The file may also contain GPS positions, routes, device information and other watch data, even if these are not displayed in the app.
  • Your entries: expected and experienced effort, bodily sensations and your own descriptions, sleep, food/drink and other details you choose to record before or after an activity.
  • Connections: the service’s user ID, access token and sync status when you connect an available integration.
  • Technical information: operational and error logs held by hosting providers, including requests, times, IP addresses and browser information.

Information comes from you, the files you upload and services you choose to connect. Connections are optional. Without activity data, RunHunch cannot display analysis or history for those activities.

How is your information used?

Account information is used for sign-in and access to your own data. Goals, training settings and activity data are used to build running plans, analyse completed activities and show volume, intensity and progress. Before and after entries compare expectations with experience.

Access tokens are used only for the connection you chose. Technical logs support operation, troubleshooting and protection of the service. RunHunch has no public activity feed and does not sell training data to advertisers.

Plans and analysis are calculated automatically from training, settings and your entries. These are suggestions you can follow or change. They are not used for decisions about insurance, employment or other rights.

When you contact us

We use your email address and the information you choose to share to reply and follow up your request. We do not use these details for marketing.

Customer support relies on the contract when your request concerns the service you use, and otherwise on our legitimate interest in answering questions and improving the service (Article 6(1)(b) or (f)). Rights requests are handled to meet our data-protection obligations (Article 6(1)(c)).

Do not send training files, health details, passwords or access tokens by email. If we need more information, we will agree a safe way to share it.

Email is handled by Webhuset. Ordinary correspondence is deleted within six months of closing the request. A minimal rights-request register is kept for twelve months after closure to document handling. If a specific legal duty or claim requires longer retention, we document the purpose and deadline for that request.

If the contact form is available, it sends messages via Google Cloud to Webhuset without storing a copy in the app. Spam protection uses counters with a one-hour window. Counters contain neither the message nor raw email/IP addresses and are marked for expiry after two hours. Provider log and backup deletion is a separate process.

Legal basis and your choices

Behandlingsgrunnlaget for konto og tjenestene du bestiller er avtale etter personvernforordningen artikkel 6 nr. 1 bokstav b. For frivillig import og bruk av trenings- og opplevelsesdata er grunnlaget samtykke etter artikkel 6 nr. 1 bokstav a. Opplysninger som sier noe om fysisk helse krever i tillegg uttrykkelig samtykke etter artikkel 9 nr. 2 bokstav a.

You are asked for explicit consent before using the training features. Your choice and the consent version are recorded. Creating an account or reading this notice is not consent in itself. You can withdraw consent under Data. This stops further imports and removes your training data, without changing the lawfulness of earlier processing.

Necessary security and troubleshooting are based on a legitimate interest in protecting accounts and maintaining service availability, under GDPR Article 6(1)(f). You may request the interest assessment and object to this processing.

Training services and automatic sync

Connections appear when available. The Polar connection uses Polar AccessLink. The Intervals.icu connection imports running activities and original FIT files from available connected services, such as Garmin, COROS, Suunto, Polar and Wahoo, once access is approved and activated.

During authorisation you choose which permissions to grant. RunHunch receives an access token, not your watch service password. Sync tokens are encrypted on the server. Disconnect an available integration under Data and manage RunHunch access with the provider.

Disconnecting stops future imports. Previously imported activities remain in RunHunch until you request deletion. Deleting data in RunHunch does not delete the original at your watch provider or Intervals.icu. Strava activities cannot be forwarded through the Intervals.icu API.

Providers and sharing
  • Google Cloud: app hosting, database and storage of training data and original files in Belgium (europe-west1).
  • Google Firebase: sign-in and website delivery. Firebase Authentication processes authentication data in the United States; Firebase Hosting uses global infrastructure. European training storage does not mean all information is processed only in the EU/EEA.
  • Webhuset: email for account messages, support and privacy requests, under Webhuset’s data processing agreement. The app does not automatically attach training data or original files to email. Messages use encrypted connections.
  • Polar / Intervals.icu: activity transfer when you authorize a connection. These services and watch providers have their own account terms.

Training plans and ordinary activity analysis use no paid AI calls. AI course lookup and weather lookup are disabled. Fonts are served by RunHunch without Google Fonts.

The earlier Lovable Cloud/Replit setup is no longer used for new production writes. A frozen rollback copy is temporarily retained; its deadline and those of other recovery copies must be settled before this notice is finalized.

Agreements, subprocessors and transfer safeguards outside the EU/EEA are being reviewed before admitting new users. This notice remains a draft until the open items are confirmed.

Storage and deletion

Account, plans, activities, original files and your entries are retained while you use your account, so history and new analyses remain available. Under Data you can download your information with original files, withdraw consent and delete your account. Withdrawal stops sync and deletes training data, plans and your entries; the account remains. Account deletion also removes the sign-in account. Export before deleting if you want a copy.

Disconnecting removes connection tokens from the active service but keeps imported activities. Daily database backups are configured for 14 days of retention. Deleted file objects are configured with a 7-day recovery window. This does not promise immediate removal from every copy. Recovery must respect earlier deletions and withdrawn consent.

Other deletion periods

Google states that other authentication information is removed from live and backup systems within 180 days after account deletion is initiated. Authentication IPs are retained for a few weeks, and website-delivery IP data for a few months. These are provider periods, separate from active training history.

Google's ordinary operational logs are retained for 30 days and required audit logs for 400 days. Both log categories have a global storage location. These periods are separate from training history and backups.

Separate recovery archives and the frozen migration copy currently have no automatic deletion deadline. Deletion requires checking that a usable recovery copy remains and earlier deletions are respected. Webhuset’s own logs and backups follow its provider procedures; we do not have a confirmed maximum period for those copies.

Google information about retention and deletion

Browser storage and cookies

The browser stores your sign-in session to keep you signed in. Fonts are served by RunHunch. Local storage also saves your language choice and prevents repeated reminders. Changing language under Data also saves your choice to your profile. Connecting a training service uses a short-lived secure cookie to verify that authorization belongs to the correct browser.

RunHunch does not use advertising cookies or fetch fonts from Google. You can clear browser storage or sign out. Clearing browser storage does not delete data stored in your account.

Access, correction and other rights

You can download your information and delete your account under Data. For a large history or if you need help, contact us for access, a copy, correction or deletion. You can also request restriction of processing and, where applicable, a machine-readable copy of data you provided. You can withdraw consent and object to processing based on legitimate interest.

To request access, correction or deletion, email privacy@runhunch.com. We verify identity only when needed and do not ask for ID documents in the initial message. We respond without undue delay and within one month. Complex requests may need up to two additional months; if so, we explain why within the first month.

You can complain to the Norwegian Data Protection Authority. Significant changes in how information is used will be notified before taking effect. The date above shows the latest update.