Privacy notice

Your account

Data

Your email address, your password (stored only as a salted hash), a display name if you set one, an internal user name that nobody sees, your language and app settings, whether your email address is confirmed, and a profile picture if you add one on the web. The apps send their version, your Android or iOS version and your phone model with each request; we keep the latest with your account, visible only to our administrators, so we can help when you contact us.

Why

To create and run your account, sign you in and keep it secure, and to send you the emails an account needs: confirming your address, resetting your password, confirming a change of address and, while new accounts wait for approval, telling you when yours is ready. We don't send newsletters or marketing.

Legal basis

Performing our contract with you (GDPR Article 6(1)(b)). For the app and phone details: our legitimate interest in helping you when something goes wrong (Article 6(1)(f)).

Kept

Until you delete your account. A sign-up that is never confirmed is deleted 7 days after its last confirmation email.

Your rides

Data

The recordings you start: precise location (GPS), time, speed, and motion-sensor and air-pressure readings from your phone and, if you connect one, a RaceBox; the phone model and app version that made the recording; the name you give a ride; photos you attach on the web; and what we compute from all this: corners, lean angles, coaching notes, ride statistics, the weather at the time and place, and place names along the way.

Why

To show you your ride, read every corner back to you and track your progress. A ride is recorded only after you press Start, and your phone shows that it is recording for as long as it records.

Legal basis

Performing our contract with you (Article 6(1)(b)).

Kept

Until you delete the ride or your account.

Where you are while the map is open

Data

While the map is open or you navigate, the app asks our server what is around you, so it sends your current position (or, when you look around, the area on screen): speed limits, speed cameras and other hazards, road closures, fuel stations and other places, twisty roads, protected areas, and the name of a spot you tap. What you type into the search goes to our server too.

Why

To show these on the map and, while you ride, to warn you in time.

Legal basis

Performing our contract with you (Article 6(1)(b)).

Kept

Not stored with your account or in our database. Our server answers from its own data or cache, or asks the services in section 5 about the area without saying who you are. Like every request, these appear in our server logs (below) for up to 30 days.

Routes, places and your garage

Data

The stops and routes you plan and save, the GPX files you import, the places you save (such as Home) and the motorcycles you add to your garage: make, model, tyre sizes and fuel range. Your recent searches stay on your phone.

Why

To plan routes, guide you along them and estimate where to stop for fuel.

Legal basis

Performing our contract with you (Article 6(1)(b)).

Kept

Until you delete them or your account.

Hairpin Pro

Data

Your plan (Free or Pro) and where Pro comes from (Google Play, the App Store, or given by us), the product (monthly or yearly), its status, start and end dates, whether it renews, whether it was a test purchase, the store's reference for the purchase (Google's purchase token or Apple's original transaction ID) with a fingerprint (hash) of it, and a log of its status changes. To tie a purchase to your account, the app gives the store a code derived from your account's internal ID, which contains neither your name nor your email address. We never receive your card or other payment details: they stay with Google or Apple.

Why

To unlock Pro, keep it in step with the store (renewals, cancellations, refunds, payment problems), stop one purchase from unlocking several accounts, and help you if Pro does not show.

Legal basis

Performing our contract with you (Article 6(1)(b)).

Kept

Until your account is deleted. Deleting your account does not cancel a store subscription: you cancel that in the store.

You buy Pro through Google Play or the App Store: they take the payment, issue the receipt and handle refunds, under their own terms and privacy policies, as separate controllers. Our server asks them to confirm a purchase, and they tell our server when its status changes.

AI analysis, part of Pro

Data

When you open the AI analysis of a ride, ask a question about it, or ask the season coach on the Stats page, we send our AI provider, Anthropic, a compact summary: corner statistics, the coaching verdicts and place names along the route (for the season coach, figures from your rides), together with your question as you typed it. For a Pro rider, when a new ride has no name of its own, our server asks the AI for one automatically, from the names of the places where it started and where it turned, and a few of its figures. We never attach your GPS track, your photos, your email address or your name; but what you write into a question is sent as you wrote it, so leave out what you do not want sent, and anyone else's personal data. For each call we also record its kind, size and cost against your account, to keep within the limits.

Why

To write the ride summary, answer your questions and name your rides. The answers are advice about your riding; nothing is decided about you automatically. AI use is capped per ride, per day and per month for each rider.

Legal basis

Performing our contract with you (Article 6(1)(b)). Asking for an analysis or a question is your choice; naming new rides is part of Pro.

Kept

The analysis and the conversation about a ride stay with the ride until you delete it; the season coach's conversation stays with your account until you delete the account. The usage records stay with your account; once it is deleted they remain only as figures with no link to you. Anthropic works for us as a processor: under its commercial terms it may not use this data to train its models, and it deletes it within 30 days, unless it must keep a request longer because it was flagged for breaking Anthropic's usage policy, or because the law requires it.

Crash reports

Data

Technical details when the app crashes or hangs: the error, memory figures, the recorder's state, the app and system version, and the phone's maker and model. On the iPhone also what the system's own diagnostics (Apple's MetricKit) report about a crash or a hang. A short memory log of each ride (one line of memory figures a minute while you record) is sent too, on both phones. No location.

Why

To find and fix bugs.

Legal basis

Your consent, which you give by switching on Send crash reports under Settings → Privacy & data, or, on Android, by pressing Upload on the crash report screen (Article 6(1)(a)). The switch is off until you turn it on, on the iPhone, in the app from Google Play and in the test version that we publish ourselves alike. While it is off, the iPhone app writes down and sends nothing. Switch it off at any time.

Kept

Until the problem is fixed, and in any case no longer than 12 months after the report reaches us: older ones are deleted automatically.

Security and abuse prevention

Data

Your IP address, browser or app details and the result of Cloudflare's bot check (Turnstile) when you sign in, sign up or reset your password, and a count of recent attempts and requests from each IP address or account, also for public pages such as a Follow my ride link.

Why

To keep bots, password guessing and floods of requests away from the service and from accounts.

Legal basis

Our legitimate interest in keeping the service and your account safe (Article 6(1)(f)).

Kept

Attempt counts are held in memory for up to an hour. We don't store IP addresses with your account.

Server logs

Data

For each request to app.hairpinride.com: the time, the address asked for (a position in it rounded to about 1 km, and without the text of a search; the codes in sign-in, share and follow links are masked), the result, your IP address as passed on by Cloudflare, and your app or browser details.

Why

To keep the service running, trace faults and defend it against attacks.

Legal basis

Our legitimate interest in a working, secure service (Article 6(1)(f)).

Kept

30 days at most: older lines are deleted automatically. We don't link the logs to your account, don't use them to follow anyone, and read them only to find a fault or an attack.

Early access, only if you ask for it

Data

Your email address and a normalised form of it (so one inbox is counted once), your phone type and where you mostly ride, if you pick them (both are optional), the language of the page, and when you asked, when you confirmed your address and, later, when we invited you. Your IP address is held only in memory, for up to an hour, to limit repeated requests, and is not stored with your request (the server logs above still hold it, for 30 days at most).

Why

To confirm your address and send you an invite when Hairpin is ready for you: one email to confirm your address and one when your invite is ready. Nothing else unless you ask.

Legal basis

Your consent, which you give by sending the form and confirming your address (Article 6(1)(a)). You can withdraw it at any time by writing to privacyhairpinride.com.

Kept

A request you don't confirm is deleted after 30 days. A confirmed one is kept until your invite is sent and for 12 months after, or until you ask us to delete it at privacyhairpinride.com. The emails go out through the same provider as our account emails (section 5).

This website and the web app

Data

hairpinride.com uses no tracking cookies, no analytics and no ads. Its one cookie, hp_lang, is set only when you pick English or Hungarian with the language switch, and remembers that choice for a year. The web app at app.hairpinride.com keeps your sign-in and your planner settings in your browser's storage, only so that it works. Cloudflare, which carries both, processes connection data such as your IP address to deliver the pages and protect them from attacks.

Legal basis

Our legitimate interest in running a secure website (Article 6(1)(f)). The language cookie and the web app's storage only do what you asked for, so they need no consent.

Friends

Data

Your friends, the requests you send and receive, the riders you block, and your invite link, which you can renew or stop. To add someone by email you type their exact address: we use it only to find the account, and we never let anyone search or list accounts. We send no email about friend requests.

Who sees what

A friend sees your display name and your profile picture, and nothing else until you share something with them or invite them to a group ride.

Kept

Until you remove the friend or one of you deletes their account.

Share links for rides and routes

Data

For each link: which ride or route it opens, when it was made, when it expires (never, or after 7 or 30 days), whether you stopped it, the title you typed for it, your choice to hide the start and end, and how many times it was opened (not who opened it).

Who sees what

Anyone signed in to Hairpin who has the link. A shared ride shows its map with the start and the end hidden (at least the first and last 500 metres, cut where the track passes them again, and the distance and time counted without them), the moving time, the maximum lean, the number of corners, the date, and the title you typed or the name you gave the ride yourself. It never shows the corner coaching, charts, AI texts, photos or the time of day. You can switch off Hide start and end for a link: then it shows the whole track with its own name. A shared route shows its line, the stops and their names, the distance, time, climb, twistiness and elevation; the viewer can plan their own copy of it. A route you planned yourself is shared whole, so if it starts at your home, the link shows that; a route made from a recorded ride or a GPX file is cut like a ride.

Kept

The link opens until you stop it or it expires. Its record stays in your list of shared links until you delete the ride or route, or your account.

Group rides

Data

The group ride (its name, planned start, leader and sweep, who was invited and who accepted, declined or left, and the shared route with its latest versions) and, while it runs: your live position, sent every 5 seconds while you move and every 30 seconds while you stand, also in the background while you record a ride or follow a route; your quick messages; a safety alert; and the leader's regroup pin.

Who sees what

Only the members of that group ride: not your other friends, and not our administrators (Hairpin gives them no way to). They see your name, your position and how far ahead or behind you are, your quick messages for two minutes, and a safety alert while it stands. A safety alert is raised by your phone when you have stood still for 5 minutes away from the planned stops, or when your phone notices a hard impact followed by stillness (the crash detector on Android, the group alert on the iPhone); the detector reads the motion sensors on your phone during a group ride, and only the alert reaches the group. On the iPhone the alert is also spoken, if you have the voice switched on, and shows a notification on your phone with an I'm OK button; the iPhone asks to show notifications only when a group ride begins. The group ride calls or texts nobody (the text message the Android app we publish ourselves can send is in section 4). When the ride ends, every member sees the summary: each rider's distance, moving time, maximum lean and clean corners, taken from their own recording. Creating and leading a group ride is part of Pro.

Kept

Live positions, quick messages, alerts and the regroup pin are held only for a short time in our server's memory, and never written to our database or our logs: a position is dropped after 10 minutes (after two hours if it carries an alert), a message after two minutes, and everything when you leave or the ride ends. The group ride's record (its name, who took part, its route and its summary) is not live data: so that friends can look back at the ride, it is kept after it, until its leader deletes it or its last rider is gone. A group ride that was cancelled or never started is deleted a day after it ended (a ride nobody starts ends a day after its planned start). Your place in a group ride, and your row in its summary, go when you step out of it or delete your account. If the leader deletes their account, a finished group ride stays for the riders who remain, without a leader, with its name, route and summary; one that is still planned or running goes with its leader. The summary is built from the members' own rides, so a ride its owner deletes drops out of it.

Follow my ride

Data

The link you make while recording a ride (a code we store only as a fingerprint, with when it was made, ends and was stopped) and, while it is live: your position, direction, whether you are moving, the last ten minutes of your path and, while you navigate, your destination and your estimated arrival time.

Who sees what

Anyone who has the link, on a web page, without a Hairpin account: you decide who gets it. They see your display name (or “Hairpin rider”), your position with the last ten minutes of path, and, while you navigate, where you are going and when you should arrive. Never your email address or your rides. The link works until the ride ends, you stop it, or the time you chose runs out (12 hours at most); then the page says “ride ended” for an hour and stops working. Signing out of the app on the phone that made it stops it too. For people who open the page, we count requests per IP address in memory, to limit abuse, and their requests appear in our server logs like any other (section 2, 30 days at most); the page sets no cookies.

Kept

Your position, path and destination are held only in our server's memory, never written to our database or our logs, and are gone when the link ends. The link's record holds no place and is deleted 30 days after the link ended.

Places you propose for the map

Data

A name, a type, opening hours, a note and the spot, with when you proposed it, its status, and our decision (with a reason if it is refused).

Who sees what

An administrator reviews each proposal before other riders see it; while it waits, only you and our administrators see it. An approved place is shown to every rider on the map as a Hairpin community place, never with your name; only our administrators see who proposed it.

Legal basis

Performing our contract with you (Article 6(1)(b)); the review rests on our legitimate interest in a correct and lawful map (Article 6(1)(f)).

Kept

You can withdraw a proposal while it waits. An approved place stays on the map until we take it off; write to supporthairpinride.com if you want it removed. If your account is deleted, an approved place stays on the map with no link to you; a proposal still waiting or refused is deleted with the account.

Reports

If you report a place (a reason and an optional note), only our administrators see the report and that it came from you. We email you our decision. Your reports are deleted with your account.