Privacy policy

1. Who we are

PaceGuide ("PaceGuide", "we", "us") is a running-training service that builds and adapts training plans using data from your intervals.icu account. PaceGuide is operated by RunFlex, based in Australia, who is responsible for the personal information described in this policy.

We handle personal information in line with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. If you are in the United Kingdom or European Union, we also follow the UK GDPR and GDPR for you, as noted below.

Contact: run@busbridge.net

This policy applies to the PaceGuide web app and its API. intervals.icu is an independent service operated by its own provider; its handling of your data is covered by the intervals.icu privacy policy.

2. Summary

• You sign in through intervals.icu. We never ask for or store a password or an email address.
• We read training summaries and wellness data from intervals.icu to build your plan, and write planned workouts back to your intervals.icu calendar. For completed sessions and other activities you open, we also fetch the pace (or speed) and heart-rate streams on demand to show them as a graph and compare them with the plan; these are cached for up to 7 days in Cloudflare's cache in encrypted form and not stored in our database. To draw the small route outline beside an outdoor activity, we also read its GPS positions on demand and reduce them, on our server, to a shape with no coordinates in it: no location, distance or place reaches your browser or is kept. Only that shape is cached (encrypted, up to 7 days); the positions themselves are never stored. If you ask PaceGuide to update your thresholds (after a threshold test, or from the Progress tab), it writes only those settings (your Run threshold pace and threshold heart rate) to your intervals.icu sport settings. If you rate how sore you are or your mood in the morning check-in and your connection allows it, PaceGuide also saves those two ratings to your intervals.icu wellness record for that day, and changes nothing else on it. Beyond those, it never changes anything else there.
• Some of this is health information. We only process it with your explicit consent, which you can withdraw at any time by deleting your account.
• We don't sell your data, show adverts, or use third-party tracking or analytics.
• You can export or delete everything we hold from the Settings page at any time.

3. Information we collect

From intervals.icu (with your permission)

• Account identifiers: your intervals.icu athlete id, display name and time zone. If intervals.icu has no time zone for you, we use your device's time zone instead, so days and times show in your local time.
• Athlete settings: running threshold pace, threshold and maximum heart rate, resting heart rate and body weight, where you have set them in intervals.icu.
• Activity summaries for up to the last 12 months and ongoing: date, sport, name, duration, distance, training load, average heart rate, average pace, intensity, aerobic decoupling and whether it was a commute. We do not store GPS routes, maps, photos, or second-by-second data streams (see above for what is read on demand to draw graphs and route outlines).
• Wellness data: daily fitness/fatigue values, heart-rate variability (HRV), resting heart rate and sleep duration, where available.
• Calendar events that PaceGuide itself created, so we can keep them up to date.

From you

• Goals (race distance, date, target time, and optionally the race's altitude), experience level, optional age, weekly availability, regular commitments (e.g. a bike commute), parkrun and club-run preferences.
• Plan edits, feedback ratings, benchmark results, and settings such as units and how the plan should adapt.
• Morning check-in you choose to make: a 1 to 5 rating of soreness (1 none, 5 very sore) and of mood (1 low, 5 great) for the day, stored encrypted and used with your other readiness signals.
• Pain or injury reports you choose to make (body location, a 1 to 10 severity), and whether you have told us you are managing an injury.
• The date and time you gave consent to health-data processing.

Created by PaceGuide

• Your training plans and planned workouts, daily training metrics we derive (such as readiness), feedback messages and suggested plan changes.

Technical information

• Your intervals.icu access token or API key, stored encrypted, which lets PaceGuide read your training and write workouts while you are not using the app.
• A session identifier (see section 9). To protect the service against abuse we briefly hold your IP address in short-lived rate-limit counters in server memory only (at most 10 minutes; they are never written to storage). To pace syncing with intervals.icu we also keep, with your account, when it last synced and how much syncing it has used that day; this is deleted with your account. Our hosting provider processes standard request logs as described in section 7.

4. Health information and your consent

Heart-rate data, HRV, resting heart rate, sleep, training load, and pain or injury reports can reveal information about your health. Under the Privacy Act this is sensitive information (health information), which we may only collect with your consent. Under the UK GDPR and GDPR it is special category data.

We collect and use it only with your explicit consent, which we ask for when you first sign in and before any data is synced. You can withdraw consent at any time by deleting your account in Settings, which stops all processing and erases the data. Withdrawing consent doesn't affect processing that happened before.

PaceGuide provides training guidance, not medical advice, diagnosis or treatment. Readiness indicators and injury-related messages are general signals; always consult a qualified professional about pain, injury or health conditions.

5. How we use information and why

We do not use your information for advertising, we do not sell or rent it, and we do not build profiles for anyone other than you.

If you are in the UK or EU, our legal bases under the GDPR are contract (Art. 6(1)(b)), your explicit consent for health information (Art. 9(2)(a)), legitimate interests (Art. 6(1)(f)) and legal obligation (Art. 6(1)(c)), matching the table above.

6. intervals.icu and your calendar

• We request only the access we need: read activities, read wellness, read settings, and write calendar events. We also request permission to write settings, which is used only when you tap to update your thresholds (after a threshold test, or on the Progress tab), and then changes only your Run threshold pace and threshold heart rate. If you use the morning check-in, the soreness and mood ratings are saved to your wellness record for that day, which needs permission to write wellness.
• Every workout PaceGuide creates carries an identifier beginning rf:. We only ever change or delete events with that identifier. Your own events are never modified.
• Workouts we write appear in intervals.icu and, through it, on devices and services you have connected there (for example Garmin, Coros, Wahoo, Suunto or Zwift), under those services' own terms.
• You can revoke PaceGuide's access at any time in your intervals.icu settings, or delete your PaceGuide account.

7. Who we share information with

We share personal information only with these service providers, who process it on our instructions:

• Cloudflare, Inc.: hosting, database (Cloudflare D1), key-value storage (sessions), edge cache, background job queue, and network security. Cloudflare processes request logs to operate and protect its network.
• intervals.icu: the service you connect, which we read from and write planned workouts to on your behalf.

We may disclose information if required by law, or to protect the rights and safety of users. If PaceGuide is transferred to another operator, this policy (or one at least as protective) would continue to apply and you would be told in the app first.

8. International transfers

Cloudflare operates a global network and may process or store data outside Australia, including in the United States and other countries. Before disclosing information overseas we take reasonable steps to make sure the provider handles it in line with the Australian Privacy Principles, including through Cloudflare's data processing terms. For people in the UK or EU, transfers are protected by safeguards such as the UK International Data Transfer Addendum and EU Standard Contractual Clauses.

9. Cookies and on-device storage

PaceGuide uses only strictly necessary cookies, so no cookie banner is needed:

• rf_session: keeps you signed in. HttpOnly, secure, first-party, expires after 30 days (renewed while you use the app). In the demo, the cookie lasts only until you close your browser, and the demo session ends after 2 hours.
• rf_oauth_state: protects the "Sign in with intervals.icu" step against forgery. Expires after 10 minutes.

The app can be installed on your device. To work offline it caches the app and your most recent screens in your browser's storage on your device. While you build or change a plan, your unsaved choices (such as your goal, training days and threshold pace) are also kept there so you do not lose them if you leave the page; they are deleted when you save or discard the plan or sign out, and a draft older than 14 days is deleted the next time you open the plan builder. Charts you save in the Progress chart builder are stored there too, as your choice of measures only and never any readings. Signing out or clearing site data in your browser removes all of it. If your sign-in expires, the saved screens are cleared the next time the app opens, and they are cleared when a different athlete signs in on the same device. We load no fonts, scripts or images from third parties.

10. How long we keep information

• Account, plan, training and wellness information: for as long as your account exists.
• When you delete your account, we delete your data and encrypted token from our live database immediately, and we remove your upcoming PaceGuide sessions from your intervals.icu calendar (sessions already in the past stay there). Copies in our hosting provider's point-in-time database backups expire within 30 days.
• Rate-limit counters (which may include an IP address): held in server memory for at most 10 minutes, never stored. Cached activity streams: up to 7 days. Sessions: up to 30 days after your last visit, or immediately when you log out, either on one device or on all of them from Settings.
• Demo accounts (made-up data, no real person or intervals.icu account): private to the browser that started them, and deleted when you exit the demo or after 3 hours without use. To keep the demo from being misused, each day's demo starts are counted per network using a one-way code made from your IP address and the date; the address itself is never stored, and the count only matters for that day.
• Background job logs (technical outcomes, no health data): up to 90 days, and deleted with your account.

11. Security

• All traffic is encrypted in transit (HTTPS).
• intervals.icu tokens and API keys are encrypted at rest with AES-256-GCM using keys held separately from the database.
• Your health and training information is also encrypted in the database with AES-256-GCM, using a key unique to your account that is derived from a master key stored apart from the database. This covers your profile, heart rate, HRV, sleep and fitness values, activity details, plans and workouts, goals, pain reports and feedback. A copy of the database or a backup on its own cannot be read. Because PaceGuide needs to read your data to sync and adapt your plan while you are away, our service can decrypt it when it runs; it is not encrypted so that only you can read it.
• Some labels stay readable so the service can find your records: dates, plan and workout status, sport type, your time zone, units and settings such as adaptation mode, and your intervals.icu athlete id.
• Every database query is scoped to your account, and this is covered by automated tests.
• We keep the minimum data needed: no GPS tracks, no raw data streams, no email addresses or passwords.
• Tokens and health data are never written to logs.

No system is perfectly secure. If a breach is likely to cause you serious harm, we will act quickly, tell you, and notify the Office of the Australian Information Commissioner (and any other authority where required), as the Notifiable Data Breaches scheme requires.

12. Your rights

Under the Privacy Act you can ask to access and correct your personal information. You also have these choices:

• Access your information and take it with you (portability): Settings → "Export my data" downloads everything we hold as JSON.
• Correct it: update your profile and settings in the app, or the source data in intervals.icu.
• Erase it: Settings → "Delete my account".
• Withdraw consent to health-data processing at any time (by deleting your account).
• If you are in the UK or EU you also have the GDPR rights to object to or restrict processing and to complain to your local authority.

You can also exercise these rights by emailing run@busbridge.net; please include your intervals.icu athlete id (shown in Settings). We respond within 30 days.

13. Automated decisions and algorithms

PaceGuide uses deterministic, rule-based algorithms (documented publicly in our methodology) to build plans and suggest changes. These suggestions don't produce legal or similarly significant effects. You stay in control: by default changes are proposed for you to accept or reject, and you can edit, lock or remove any session.

14. Children

PaceGuide is not intended for anyone under 16. We ask you to confirm you are 16 or older before any data is processed. If you believe a child has used PaceGuide, contact us and we will delete the account.

15. Changes to this policy

If we make material changes, we will update the version and effective date above before they take effect. Where changes affect how we use health information, we will ask for your consent again before using it in the new way.

16. Contact and complaints

Questions or requests: run@busbridge.net.

If you are unhappy with how we handle your information, please contact us first so we can help. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au). If you live elsewhere, you can complain to your local data-protection authority.