Privacy

Last updated: 30 October 2026. Paceran (“PaceRunner”, “we”) runs PaceRunner. Questions or requests: contact@paceran.com.

The person in charge of protecting your personal information is Privacy Officer, reachable at contact@paceran.com.

What we collect, and why

• Your account: your email address, to send sign-in links and identify you; for each signed-in session, the IP address and browser it came from, to keep sessions secure.
• Your profile: a race time and the paces you set, your maximum heart rate, units, time zone and watch model, to turn words like “tempo” into your paces and heart-rate ranges, and to schedule on the right day; and each change to your paces, with its reason, so you can undo it. Heart rate can be health information; we use it only for these targets.
• Your workouts: the text you type, the workouts you edit and save, what you send to Garmin and when, Garmin's copy of each workout we read back to check it, and your answers to “did it run as previewed?”.
• Your Garmin Connect™ link: the Garmin user id, the permissions you granted, and access tokens, which we store encrypted. We never see your Garmin password.
• Your runs: if you share activities with PaceRunner in Garmin Connect, each run your watch records: its type, name, start time, length, distance and laps, and second by second its time, distance, pace and heart rate. We use them to show how each run went against the session it was for, to read a time trial's result, and, when your hard sessions keep missing their paces for a couple of weeks, to ask whether you want new ones. Heart rate can be health information; we use it only for this. Garmin also sends where you ran, and your other activities, such as rides; we don't keep those.
• Usage counts: how many workouts you parse and send, to apply limits.
• Your subscription: your plan, whether it's in its free week, active or cancelled, and when it renews or ends, as Stripe reports them. We never see or store your card details.
• Product analytics, only if you say yes: after your first workout is built, PaceRunner asks whether you'll share how you use it. If you say yes: events such as “workout parsed” or “workout sent” (including your sends from the week before you said yes), which features you use and which pages you open, and recordings of how you use the editor with everything you type hidden. All of it is tied to your account id, not your email. Until you answer, and after a no, none of this is collected. We keep your answer, the wording you saw and when.
• Errors: when a workout can't be read or sent, the error and your account id, to fix it. This is part of running the service and doesn't depend on your analytics answer.
• The home and sign-in pages, before you sign in: that the home page was visited and which “Start” button was clicked, and whether visitors click a “coming soon” button on the sign-in page, counted without cookies or any stored identifier.
• Waitlists: if you ask to hear about a feature, your email, which list, the wording you agreed to and when.

Who else handles it

We share it only with services that run PaceRunner for us, and only what each needs:

• Google (Gemini): the workout text you type, to turn it into steps. Your paces are applied on our side and not sent, and nothing from Garmin is. On the Gemini service we use today, Google may use that text to improve its products, including its AI models, so don't put personal details in it.
• Garmin: the workouts you choose to send, and the date; Garmin sends us the runs you share. Garmin's own privacy policy covers what happens in Garmin Connect.
• PostHog: error reports, and product analytics and editor recordings if you said yes.
• Stripe: your email address and your payment details, to take payment and manage your subscription. Stripe's own privacy policy covers your card details.
• Resend: your email address, to deliver sign-in links.
• Cloudflare: runs PaceRunner, so every request passes through it.
• Neon: stores everything above in a database on Amazon Web Services in Ohio, United States.

Our database is in the United States. Google, PostHog, Stripe and Resend process information in the United States; Garmin in the United States and the other countries it operates in; Cloudflare in its data centres worldwide, usually the one nearest you. So your information leaves Canada (and the EU or UK, if you're there) and may be accessed under the laws of those countries. Where the GDPR or UK GDPR applies, these transfers rely on each provider's data processing terms, including the European Commission's standard contractual clauses and the UK addendum to them. We don't sell personal information.

Legal bases (GDPR and UK GDPR)

Providing the service you signed up for (account, profile, workouts, Garmin link, runs, subscription); your consent (product analytics, editor recordings, waitlists); and our legitimate interest in keeping the service secure and working (usage counts, error reports, the anonymous visit and click counts before sign-in).

How long we keep it

Until you delete your account, except: waitlist sign-ups until you unsubscribe; product analytics for up to 12 months and editor recordings for up to 30 days; and our database's backups, which are overwritten within 30 days, so a deleted account is gone from them by then. Stripe keeps payment records for as long as tax and financial laws require.

Your choices and rights

• Correct your profile any time on Your paces.
• Disconnect Garmin Connect from the home page; we tell Garmin to remove PaceRunner.
• Delete your account on Your paces. This also removes PaceRunner from Garmin Connect. Workouts already on your Garmin calendar stay there.
• Ask for a copy of your information, in a portable format, or ask us to stop a use of it, by writing to contact@paceran.com. We answer within 30 days.
• Change your analytics answer any time on Your paces. Turning it off stops collection and deletes what PostHog already has about you; deleting your account does the same.
• Unsubscribe from a waitlist with the link in any email.
• Complain to the Office of the Privacy Commissioner of Canada, Quebec's Commission d'accès à l'information, the UK ICO or your EU data protection authority.

Cookies and similar storage

A session cookie keeps you signed in, and a short-lived cookie protects the Garmin connection step; both are needed for the service. Only if you say yes to analytics does PostHog store an identifier in your browser; it's removed when you turn analytics off or sign out. Your answer itself is kept with your account, not in your browser.

Changes

If we change this policy in a way that matters, we'll tell you in the app or by email before it applies.