Privacy policy
How GoKart Crew handles your personal data, and what you can ask us to do with it.
Last updated: 3 November 2026
Who we are
GoKart Crew is operated by Roadtrip Technologies Limited, registered with the Companies Registration Office (Ireland), no. 616164, registered office 142 Charlotte, Honey Park, Dún Laoghaire, Co. Dublin, A96 HX8K, Ireland. We are the data controller for the personal data described here. For anything about your data, write to privacy@gokartcrew.com.
What we collect
| Data | What it is |
|---|---|
| Account | Email address, display name, handle, country, nationality if you gave it, avatar, and whether your profile is public. From Google sign-in we receive your name, email address and profile picture. |
| Phone number | Required before you join a race, so the race's organisers can reach you about it and add you to its WhatsApp group. Stored apart from your public profile and never shown to other members on the site. |
| You and your karting | Asked once, when you join, so we can plan races around who the crew is: the year you were born, the county you live in, whether you've been karting before and how often you go. Your gender (woman, man, non-binary or prefer not to say) is optional: you can leave it blank. Kept apart from your public profile, like your phone number: never shown on your profile or to other members. Your year of birth and gender are seen only by you and our admins; your county and your karting answers are also seen by the people who run a race you join. |
| Racing | Races you join, confirm or leave, results, finishing positions, lap times, points and podiums. |
| Results sheets | When an organiser enters a race's results from the circuit's timing sheet, a name on the sheet that doesn't match a member is kept with its position and lap time, so the result can be linked to the driver if they join. The race page shows them only as an unregistered driver: the name is seen only by the race's organisers and our admins. |
| Race photos and videos | Photos an organiser takes at a race and posts on the race's page, which anyone can see: you may be in them. Videos are the organiser's YouTube links, shown on the race page. If you would rather not be in one, tell the organiser or write to us, and we take it down. |
| Race reviews | After a race you raced, your review: your overall stars and, if you write one, your review, which are shown on the race page with your name if your profile is public (otherwise as a member of the crew), and to the people who run that race with your name. The rest of your answers (the other ratings, what stood out, whether you'd race again, and any private note) go to the race's organisers without your name. Our admins can read all your answers with your name, including reviews you gave earlier. |
| Calendar invitations | When you join a race, or organise one, we email a calendar invitation for it to the address on your account, then update it as the race goes on and cancel it if you leave or the race is called off. We keep which invitation we last sent you for each race, and when. |
| Karma and lifts | Lifts you offer or accept, the town you set off from, karma earned and spent, and the cosmetic items you unlock. |
| Membership | Invites you create or redeem, and applications for an invite, including any member you name and what you tell us about your karting. |
| How you found us | When you register or ask for an invite: the campaign that brought you (the utm tags on the link you followed), the website that linked to us (its address, without anything after the "?"), the first page you landed on, and, if you came from an ad on Facebook, Instagram or Google, the click id the ad network added to the link (fbclid or gclid), so a registration can be matched to the ad that brought it. Our admins use it to see which campaigns work. |
| Payments | When you pay by card, Stripe processes it: we store the Stripe customer and payment identifiers, the amount, currency and status, and never see or store your full card number. When you pay by Revolut transfer, we store the Revolut username you tell us you paid from, the payment reference, the amount, when you told us you had paid, and when and by whom it was checked and any refund sent back to you. |
| Rider waiver | The version of the rider waiver you accepted and when, as our record that you accepted it (see the Terms). Kept with your account, and visible only to you and our admins. |
| Revolut username | The Revolut username (@revtag) you last paid a seat from, kept on your private profile to fill in the payment form next time. Only you and our admins can see it; it is never shown to other members. You can change it the next time you pay, or ask us to delete it. |
| Safety reports | If another driver reports you for unsafe driving after a race you both raced: the race, the reason category, any note they wrote, who wrote it and when. If a report leads to a cooldown or removal we also store the decision, the dates and the reason categories behind it, and, when a removal is reviewed, which of our admins decided it, when, and their note. |
| Technical | Sign-in cookies, and the usual server logs (IP address, browser, pages requested) kept for security and troubleshooting. To rate-limit the public access-request form we store a salted hash of the IP address, never the address itself. |
| Page counts | How many times each public circuit and race page is viewed per day, a single number per page, shown to that circuit's team on its dashboard. And how many visits a day arrive through each campaign link (the utm tags on the link) and on which circuit or race page, a single number per set of tags, shown to our admins. Nothing about who viewed is kept: no cookie, no IP address, no account, so it doesn't need your consent. |
| Analytics (only if you agree) | If you accept analytics cookies: the pages you view, what you do on them (joining a race, sending an invite, paying for a seat), your device, browser and approximate location, and a random identifier kept in a cookie. Collected by Google Analytics; Google does not store your IP address. Never your name, email or phone number. |
| Advertising measurement (only if you agree) | If you accept advertising cookies: the pages you view, and when you ask for an invite, become a member or pay for a seat (with the amount), sent to Meta with Meta's own browser identifiers (the _fbp and _fbc cookies), your browser and IP address, and your email address and account id in hashed form (scrambled one way, so Meta can only match them to a Facebook or Instagram account it already knows). We keep your answer, those two identifiers and your browser's description with your account, so that a payment we check by hand can be reported too. Never your name or phone number. |
Cookies
We use Google Analytics cookies (_ga and _ga_…, kept for up to 13 months) only if you accept analytics cookies in the cookie banner, to understand which pages and races people use. We use the Meta Pixel's cookies (_fbp and _fbc, kept for up to 90 days) only if you accept advertising cookies, to see which of our Facebook and Instagram ads bring people to a race. The two are separate choices (“Choose which” in the banner), and until you say yes to one, its code isn't loaded at all. You can change your mind at any time with “Cookie settings” at the bottom of every page: saying no deletes those cookies, and we stop reporting anything about you to Meta.
Besides those, the only cookies we set keep you signed in, remember the invite you arrived with, remember for 30 days which campaign or website sent you here, and for 90 days the ad click id if an ad did (see “How you found us” above), and remember your cookie choice for six months. They are needed for the site to work, so they don't ask. The support chat (Customerly), on the invite pages and for signed-in members, keeps its own cookies so your conversation with us carries on from page to page.
Why we use it, and on what legal basis
- To run your membership and your races — creating your account, holding your place on a grid, taking your payment when you confirm (by card, or by a Revolut transfer we check by hand), refunding you when a race is called off, and showing results and leaderboards. Legal basis: performance of our contract with you.
- To plan races around who the crew is — your age, county, karting experience and how often you go, whether you can give lifts, your nationality if you gave it, and your gender if you gave it, looked at across the whole crew rather than one member at a time: where and when to run races, and how to set up the grids. Legal basis: our legitimate interest in running races that suit our members; for your gender, which is optional, your consent, which you can withdraw at any time by asking us to delete it.
- To show what our races are like — photos from a race on its page. Legal basis: our legitimate interest in sharing the crew's races; you can object to any photo you are in, and we take it down.
- To keep the community working — invites, vouching, karma, lifts, preventing abuse of the public forms, and keeping the platform secure. Legal basis: our legitimate interest in a community that stays civil and safe.
- To meet our legal duties — keeping records of payments for tax and accounting. Legal basis: legal obligation.
- To understand how the site is used — anonymous-style usage statistics from Google Analytics, only if you accept analytics cookies. Legal basis: consent, which you can withdraw at any time with “Cookie settings”.
- To measure our ads — telling Meta when someone who saw one of our Facebook or Instagram ads asks for an invite, joins or pays for a seat, only if you accept advertising cookies. Legal basis: consent, which you can withdraw at any time with “Cookie settings”.
- To send you anything optional, such as a newsletter, only if you ask for it. Legal basis: consent, which you can withdraw at any time.
What other members can see
Your handle, display name, avatar and racing record (races, positions, best laps, karma and unlocked items) are visible to other members, and are public on the web if you switch your profile to public in your account settings. Your email address and phone number are never shown on the site. Nor are your year of birth, county, gender and karting answers. Your year of birth and gender are seen only by our admins. Once you join a race, the people who run it (its lead organiser, any co-organisers, and the circuit's staff when the circuit hosts it) can see, on the race's organiser page, your email address and phone number, your county and karting answers, the lifts you offer, what you paid for that race and how (with your Revolut tag if you paid by Revolut), and your review of that race (your stars and written review, under your name), so they can run the race and reach you about it. Once you have paid for your seat, they also see your phone number through our organisers' Claude connector when they use it, and in the calendar invitation for the race that we email them, which lists every driver on the grid by name and gives the phone numbers of the drivers who have paid. If you join that group, WhatsApp and the people in it will see your number, under WhatsApp's own terms.
Safety reports: who can see them, and for how long
After a race, drivers who raced it can report someone on the same grid for unsafe driving. A report stores the race, the driver reported, the reporter, one reason category (contact, blocking, dangerous overtaking, ignoring flags or unsporting behaviour), an optional note and the time it was sent. Reports can only be made within 72 hours of the race — or of its results going up, if that is later — and once per reporter per driver per race.
- Only our admins can read a report. Not the driver it is about, not other members, not organisers, not the circuit. The reporter cannot read it back either; it is not shown anywhere on the site.
- There is no public counter. Nobody but our admins can see how many reports a driver has, and there is no badge, list or leaderboard of them anywhere.
- If you are sanctioned we email you the decision, the dates and the reason categories, and you can see the same in your account. A removal is decided by one of our admins, never automatically, and we tell you while it is being reviewed. We withhold the reporters' identities and their notes: that is third-party personal data, and it stays withheld if you make a subject-access request. You can still contest the decision and have a human look at it.
- How long: a report stops counting after 12 months, or sooner if a sanction it fed is lifted, and we delete reports older than 24 months. A cooldown or removal is kept as part of the membership record for as long as your account exists.
Legal basis: our legitimate interest in members being safe on track, and in being able to show that a sanction was applied fairly. You can object to it by writing to privacy@gokartcrew.com.
Who we share it with
| Service | What it does for us |
|---|---|
| Supabase | Database, accounts and sign-in emails. Hosted in Ireland. |
| Vercel | Website hosting. Our server code runs in Dublin. |
| Stripe | Card payments and refunds. Stripe is the controller of your card data. |
| Revolut | Receiving seat payments by Revolut transfer, and sending refunds back. Revolut is the controller of your Revolut account data; we see what anyone you pay sees: who the transfer came from, the amount and the note. |
| Resend | Sending our emails (invites, seat offers, confirmations, calendar invitations). |
| Customerly | Our support chat, on the invite pages and for signed-in members. When you're signed in, the chat knows who you are: your name, email, handle, phone number and your answers from the welcome flow, so whoever answers you doesn't have to ask. It keeps your conversations with us. |
| Only if you choose to sign in with Google. | |
| YouTube | Race videos. Nothing is loaded from YouTube's player, and no YouTube cookie is set, until you press play on a video; the player then comes from youtube-nocookie.com, under Google's terms. |
| OpenStreetMap | Circuit maps. Loading a map sends your IP address to OpenStreetMap. |
| Google Analytics | Measuring how the site is used, only if you accept analytics cookies. Run by Google Ireland Limited on our behalf; the data is kept for 14 months. |
| Meta | Measuring our Facebook and Instagram ads and showing them to people likely to race (the Meta Pixel and Conversions API), only if you accept advertising cookies. Meta Platforms Ireland Limited, joint controller with us for collecting and sending the data, under Meta's Business Tools terms; Meta decides for itself how it then uses it, under its own privacy policy. |
These providers act on our instructions (Google Analytics included, under Google's data processing terms), except Stripe, Revolut, Google sign-in, Meta, WhatsApp and OpenStreetMap, which decide for themselves how they use the data you give them. Some of them are outside the European Economic Area; where that happens, the transfer relies on the European Commission's standard contractual clauses or an adequacy decision. We never sell your personal data.
How long we keep it
Your account and racing history stay until you ask us to delete them. Payment and accounting records are kept for six years, as Irish tax law requires. Server logs are kept for a short period, and the hashed rate-limit records for one day. Results already published on a leaderboard may stay as part of the race record, with your handle removed if you delete your account.
Your rights
Under the GDPR you can ask us for a copy of your data, correct it, delete it, restrict or object to how we use it, or receive it in a portable format. Write to privacy@gokartcrew.com and we will answer within one month. If you are not happy with our answer, you can complain to the Irish Data Protection Commission at dataprotection.ie.
Children
GoKart Crew is for adults. You must be 18 or over to be a member, because joining a race means paying for it, which is why we ask the year you were born when you join. Circuits apply their own age, height and safety rules on the day.
Changes
If we change this policy we will update the date at the top of this page, and tell members by email when the change matters.