Legal
Cookies
In force from 4 October 2026 · Pro Cykling ApS
In short.
- Velograph uses only what it needs to work, unless you say yes to more.
- The one thing you can say yes to is product statistics: counting which pages and features are used. Never your rides, your numbers, names or anything you write.
- No advertising, no tracking across websites, and no other company's cookies.
- Saying no is as easy as saying yes, and you can change your answer at any time: here, in your profile, or under "Cookie settings" at the foot of every public page.
Your answer
You haven't answered yet, so only what is necessary is used.
This is the answer for this browser. Signed in, your answer follows your account.
1. What Velograph uses
Necessary: always on
What Velograph cannot work without, or what you asked for yourself. The law allows these without asking. Each is set by Velograph, for Velograph, and read by nobody else.
| Name | What it does | How long |
|---|---|---|
velograph.authCookie · Velograph |
Keeps you signed in. | 60 days, renewed while you use Velograph |
velograph.2faCookie · Velograph |
Remembers who is signing in between the password and the code from the authenticator app. | 5 minutes |
.AspNetCore.Identity.TwoFactorRememberMeCookie · Velograph |
Skips the authenticator code on this device, only when you tick "Don't ask again on this device". | 14 days |
.AspNetCore.Antiforgery.*Cookie · Velograph |
Protects forms against being sent from other websites. | Until the browser closes |
velograph.garminCookie · Velograph |
Holds a one-time code while you connect Garmin Connect. | 15 minutes |
velograph.zwiftCookie · Velograph |
Holds a one-time code while you connect Zwift. | 15 minutes |
velograph.cloudCookie · Velograph |
Holds a one-time code while you connect a device maker such as Hammerhead, Wahoo, Polar or Suunto. | 15 minutes |
velograph.staffCookie · Velograph |
Keeps the visits of Velograph's own staff out of the visitor counts, also after they sign out. Only browsers where a member of staff has signed in get it. | 400 days, renewed each month while staff use Velograph |
velograph.consentCookie · Velograph |
Remembers your answer to the cookie question. | 12 months |
vg-themeBrowser storage · Velograph |
Remembers light or dark mode, when you pick one. | Until you change it |
vg-plan-clipboardBrowser storage · Velograph |
Remembers which training sessions you copied on the calendar, so you can paste them in another tab or after reloading the page. It holds which sessions they are, not what is in them. | Until you copy others or clear it |
vg-tz-keep:*Browser storage · Velograph |
Remembers that you chose to keep your time zone when this device is in another one. | 14 days |
sw.jsService worker · Velograph |
Shows browser notifications, only after you turn them on. | Until you turn notifications off |
Statistics: only with your yes
No cookie is set for statistics. With your yes, the page you are on tells Velograph's server which page you opened and which buttons you used, and the server counts it.
| Name | What it does | How long |
|---|---|---|
Product statisticsNo cookie · Velograph's servers |
Which pages are opened and which features are used, and the size of the screen, under a code that cannot be traced back to you without a key kept apart from the data. No cookie is set. | Counts kept 400 days |
2. Product statistics
- What is counted: which pages are opened, as patterns such as "a ride" or "the calendar"; which buttons and switches are used; errors you meet; whether you use a phone, a tablet or a computer; your role and the kind and plan of the workspace.
- What is never counted: rides and their numbers, health data, names, email addresses, photos, places, and anything you write or ask. No recordings of the screen, no heatmaps, no fingerprinting of your device.
- Who you are in them: a code made from your account with a key kept apart from the data, so the statistics cannot be traced back to you without it. Visitors who are not signed in are not counted in them. Velograph's server only counts how many of them open its public pages and where they came from, without any cookie or anything on their device (see section 2 of the privacy policy).
- Why: to see what works, what nobody uses and where people get stuck, and to make Velograph better.
- On what basis: your consent. Nothing is counted before your yes, and you can withdraw it at any time; what was counted before stays lawfully counted, but a no deletes what was counted under your code straight away.
- Who sees them: Velograph's own team, only as totals, never per person. Counted on Velograph's own servers in the EU. Never shared or sold, and no other company is involved.
- How long: 400 days, so one season can be compared with the last, then deleted.
- Under 18: never counted, and never asked.
3. How your answer is kept
- In this browser, in the
velograph.consentcookie, for 12 months. Then you are asked again. - With your account, when you are signed in: your answer then applies wherever you sign in, and a record of it, with the words you were shown, is kept as proof for as long as the account exists. An answer given in this browser just before you sign in or create an account is kept with the account, so you are not asked twice.
- When something changes in what Velograph asks for, everyone is asked again. Nothing new starts before you say yes.
4. Signals from your browser
If your browser sends Global Privacy Control, Velograph takes it as a no to statistics and does not ask. You can still say yes here or in your profile, and that answer counts.
5. Other companies
- No other company sets cookies on Velograph's pages. Fonts and the map library are served by Velograph itself.
- Map images come from OpenStreetMap when a page shows a map. Your browser asks OpenStreetMap's servers for them, which tells them your IP address; they set no cookies. Their privacy policy is at osmfoundation.org.
- When you leave Velograph to pay at Stripe, or to connect Garmin, intervals.icu, Strava, Google or Microsoft, their own pages and their own cookie rules apply.
6. Wherever you are
Velograph applies the same rules to everyone: those of the EU's GDPR and ePrivacy rules, which ask for a yes before anything that is not necessary. That also meets the rules in the UK, Switzerland, Brazil, Canada and elsewhere. For people in California and other US states: Velograph does not sell or share personal information, or use it for targeted advertising, as those laws define the terms.
7. Questions
Write to hello@velograph.ai. How Velograph handles personal data in general is in the privacy policy.