Skip to content
SplitOne

Home / Legal / Privacy

Privacy policy

Version 3.2 · effective 12 October 2026

This policy explains how SplitOne handles personal data in the SplitOne mobile app (the “app”) and on the website at split1app.com (the “website”). It is written to meet the UK General Data Protection Regulation (“UK GDPR”), the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations 2003. You must be 13 or over to create an account.

If you are not a SplitOne user but your name appears on a karting result sheet, the section “Imported results: if you are not a SplitOne user” is written for you.

In short

  • We collect what the app needs to record and compare your lap times, and nothing for advertising.
  • No advertising, no advertising identifiers, no cross-app or cross-site tracking, no sale of data.
  • Your evidence photos are private. A result-reading service (OpenAI) reads them for you; nobody else sees them.
  • Other drivers printed on your result sheet are recorded as imported results and shown to signed-in users.
  • You can export your data and delete your account from inside the app. Deletion completes after a 30-day grace period.
  • You can complain to the Information Commissioner’s Office (ICO) at any time.

Who is responsible for your data

SplitOne is the controller of the personal data described in this policy. SplitOne is operated from the United Kingdom, and this policy is written under UK law. You can reach us at splitone@split1app.com. A person reads every message. We have not appointed a data protection officer because the law does not require one for processing of this kind and scale.

What we collect in the app

Your account

Your email address, your password (stored only as a salted hash using Argon2id; we cannot read it), your username, your display name, your experience level, your home track if you choose one, and a profile photo if you add one. We also record when you accepted the app terms and which version you accepted.

Signing in with Apple or Google

If you sign up or sign in with Apple or Google, your device sends us an identity token from that provider. We verify it and keep the provider’s unique identifier for you and the email address the provider gives us. Apple may give us a private relay address instead of your real one; that is fine, and we send account email to it. We do not receive or keep your name from Apple or Google. Apple and Google see that you signed in to SplitOne under their own privacy policies.

Your date of birth

You declare your date of birth when you create your account, and we record when you declared it. We use it for two things only: to check that you are 13 or over, and, if you are under 18, to apply the protections described in “Children”. When you turn 18 those protections stop applying automatically, but your settings stay as you left them. Your date of birth is never shown to other drivers, never used to target you, and our staff can see only whether you are under or over 18, not the date itself. If you are under 13 we refuse the sign-up and keep nothing.

Your karting data

The sessions you record: the track, layout and kart class, the date, an optional label and notes, your lap times, your kart number if you enter it, and how each time was added (typed in, read from a photo, imported from an email, or claimed from an imported result). Your original lap time is never overwritten. If you correct a time, we keep the previous value, the new value, your reason and the date as a revision history. You can delete any of your own times and sessions; a deleted time disappears from every screen and is kept only in our database, marked as removed by you.

Evidence photos and forwarded result emails

When you photograph a printed result sheet, the photo is uploaded from your device straight to our media provider (Cloudinary) into a private area for your account. Our server then gives OpenAI, the service that reads the sheet, a short-lived signed link to that photo. OpenAI returns the rows it can read; nothing it returns counts until you confirm your row. The photo is never shown to other users, and our staff have no screen that displays it.

You can also forward a result email from a track to a personal forwarding address we give you (a random address that contains no information about you). We keep the subject, date and cleaned-up text of the email and the candidate rows read from it, and the text is sent to OpenAI to read in the same way. Some tracks send their result emails to us directly; those emails are handled as imported results (below), not as your data.

Other drivers on your result sheet

A result sheet usually lists more than one driver. When you confirm your row, the other rows (nickname as printed, lap time, kart number and any category marker) are saved as imported results for that track and date, so that the leaderboard reflects everyone who drove. These rows are labelled as imported, are not accounts, and are described in the section “Imported results: if you are not a SplitOne user”.

Claiming an imported result

You can claim an imported result as yours. The lap time is copied to your account, the nickname on that row becomes linked to you at that track, so that future sheets with the same nickname at the same track land in your history automatically, and other drivers who might plausibly own that row are notified and can contest the claim. We keep a record of claims, releases and contests. A claim tells us whose time it is; it does not verify the time.

Videos

Onboard videos you upload go from your device straight to Cloudinary, which also converts them for playback. We store the video, a thumbnail, its duration and resolution, the title, description, track, date, conditions and camera position you enter, and the camera brand and model if you enter them. Videos are private by default and become visible to others only if you publish them; you can withdraw a published video at any time. Uploads that never finish are removed after six hours. Video comparison projects store only your analysis settings, never an edited copy of the video.

Content you share

Community posts and the photos attached to them, comments, mentions, helpful votes, saved posts, tips, published videos and your public profile. Who can see this content is described under “What other people can see”.

Interactions

Who you follow and who follows you, follow requests, tracks you follow, who you block, and reports you submit about content or other drivers. Block lists and report records are kept server-side so that they keep working reliably.

Location

The app asks for location access (“while using the app” only) when you tap to find tracks near you, never at sign-up. When you do, your device’s current position is sent to our server with that one request so we can sort tracks by distance, and is not stored. You can decline and search tracks by name instead. We do not build or keep a history of your movements.

Notifications

If you enable push notifications, a push subscription identifier and your platform (iOS or Android) are registered with our notification provider (OneSignal) so it can deliver them. The app only asks after you have saved your first session, never on first launch, and you can decline. You can switch each category of notification off in Settings; only “scan needs confirming” stays on, because it protects the accuracy of your results. Push notifications are not sent between 22:00 and 08:00 UK time; the in-app notification still appears. We keep an in-app record of each notification (its type and what it links to) until you dismiss it.

Sign-in records

Each time you sign in or the app refreshes its session, we record the IP address and the app or browser identifier string of the device, with timestamps, as a security record for that session. Sessions expire after 60 days without use, and signing out or changing your password ends them. These records are deleted when your account is deleted.

Diagnostics (crash reports)

If the app crashes or hits an error, a crash report is sent to our error-monitoring provider (Sentry). Before it leaves your device we strip email addresses, authentication headers and request bodies, and we never attach your account identifier. The report contains the error details and basic device information such as device model, operating system version and app version.

App analytics

The app sends our own server a small number of product events (for example, that the app was opened, that sign-up completed, or that a result card was shared), with your platform and app version. When you are signed in, the event is tagged with your account identifier; otherwise it is tagged with a random identifier created on your device and kept in secure storage. Our server forwards these events to our analytics provider (PostHog). There is no analytics or advertising software from any other company in the app, we never use your device’s advertising ID, and we do not track you across apps or websites.

Photo and video metadata

Your camera can embed metadata in photos and videos, such as the time and, if your camera setting is on, the place they were taken. Since the October 2026 update, the app removes that metadata on your phone before any photo or video is uploaded, so the location never reaches us. Older versions of the app uploaded files as they were, so please keep the app up to date.

Coach interest

If you tell us you are a coach, we keep only the email address you enter and send one acknowledgement email. Registering interest is not a marketing subscription and does not create an account.

What we do not do in the app

  • No advertising, and no advertising SDKs.
  • No cross-app or cross-site tracking, and no use of your device advertising ID.
  • We do not sell personal data, or share it for advertising purposes.
  • We do not read your contacts, calendar, microphone, motion sensors or health data.
  • We do not send marketing email. Every email we send is needed to run your account.

Imported results: if you are not a SplitOne user

SplitOne records historical karting results from tracks’ result sheets, emails, photos and PDFs, so that new tracks are not empty on day one and so that a driver can compare their time with everyone who drove that day. If your nickname was on such a sheet, we may hold an imported result about you even though you have never used SplitOne.

  • What we hold: the nickname exactly as printed, the lap time, the kart number and any category marker, the track, layout and date, and which document it came from. We do not hold your real name, contact details or anything else.
  • Who sees it: signed-in SplitOne users, on that track’s leaderboard, labelled as an imported result. Imported results are never shown on the public website and are never presented as verified.
  • Markers for minors: a row whose own details carry a junior or under-16 marker is kept in our database but is never displayed anywhere, and cannot be claimed.
  • Legal basis: our legitimate interest in providing accurate, complete leaderboards, balanced against the limited nature of the data (a nickname and a lap time that the track already printed or published). Because we cannot contact the people on a sheet individually, this policy and the removal page below are our notice to you.
  • Your rights: you can ask us to remove or correct your row, or to claim it, at split1app.com/help/remove-a-result, without an account. A person checks the request against the source; a matching nickname on its own is not treated as proof. If we remove a row we hide it and keep a suppressed copy so that a later import of the same sheet cannot bring it back. You also have the rights listed under “Your rights”.

What other people can see

SplitOne is built around comparable lap times, so some of what you do is visible by design:

  • Driver profiles are public by default for adults and private by default for drivers aged 13 to 17. A public profile can appear in search and may be visible to people who are not signed in. A private profile shows others only your basic profile (username, display name and photo), with no results, statistics or follower lists, until you approve their follow request.
  • Your lap times appear on a track’s leaderboard when the session has a confirmed kart class and layout and you have “Appear on leaderboards” switched on. Leaderboards are visible to signed-in users only.
  • Posts you publish in the community, comments, and videos you choose to publish are visible to other users, and may be visible to people who are not signed in.
  • Your privacy settings control whether your profile is public, whether results appear on it, whether you appear on leaderboards, and whether we suggest imported results that might be yours. Evidence photos, forwarded emails and unpublished videos are always private.
  • If you share a result card, the image contains your lap time, the track and your position, but not your name or any other driver’s name. It goes only where you send it.
  • Our staff can see your account and content through an administration tool for support and moderation. Every administrative action is recorded in an audit trail.

What we collect on the website

Server access logs

Our hosting provider (Vercel) records a technical log entry each time a page is requested. That entry can include your IP address, the page requested, the date and time, the referring page, and your browser and operating system version. Our API host (Railway) keeps a similar log of requests to our server, including IP address.

Page-view and link analytics

When you visit a page, our own server records that a page of a given type was viewed (for example, a track page or a Tip), and when you click certain links, your browser tells our server which type of page and content the click was on. Neither event carries any identifier for you or your device: every visitor’s events look the same to us. They are forwarded from our server to PostHog; your browser never talks to PostHog. Nothing is stored on your device for this, which is why it does not need your consent.

Campaign attribution (only if you accept in the cookie notice)

If you arrive from a link that carries campaign parameters (utm_source, utm_medium, utm_campaign) and you choose Accept in the cookie notice, your browser sends our server those parameter values and the type of page you landed on, once, and stores a flag so it is not sent again. The event has no identifier for you. If you choose Reject, nothing is sent or stored. Details are in our cookie policy.

Tracked advert links

Some of our adverts and flyers use a short link on this site (an address beginning split1app.com/go/). When you open one, our server records that the link was opened, the time, whether the device was an iPhone, an Android phone or something else, the two-letter country code our hosting provider derives from your connection, and whether you were sent to the App Store, Google Play or our download page. It does not record your IP address, your browser details or any identifier for you or your device, and it stores nothing on your device, so it does not depend on the cookie notice. We use it only to count how many people each advert brought. The store page you are sent to may carry the advert’s campaign name in its address; what Apple or Google do with that is described in their own privacy notices.

Images from our media provider

Cover images on Tips are served from Cloudinary’s content delivery network, so your browser’s request for the image, including your IP address, reaches Cloudinary. Fonts and every other file come from our own domain.

Forms and email

The “remove a result” form opens a pre-filled message in your own email app; nothing is sent to our servers until you send that email. The password reset page sends your new password to our server over an encrypted connection; only its hash is stored. The email confirmation page passes a one-time code to the app and records nothing. If you email us, we hold your email address and whatever you choose to put in the message, so that we can reply.

Why we process it, and our legal basis

  • Providing the service: your account, karting data, evidence, videos, content, interactions, claims and service email exist to deliver what the app does. Legal basis: performance of our contract with you (UK GDPR article 6(1)(b)).
  • Age check and protections for drivers aged 13 to 17: our legal obligation to process children’s data fairly (article 6(1)(c)), and our legitimate interest in keeping the service appropriate for its youngest users (article 6(1)(f)).
  • Safety and moderation: reports, blocks, moderation records and the audit trail protect users from abuse and let us meet the app stores’ content rules. Legal basis: our legitimate interests in keeping the service safe (article 6(1)(f)), and legal obligation where it applies.
  • Security: sign-in records, password hashing and server logs detect and investigate misuse. Legal basis: our legitimate interests in securing the service.
  • Imported results about other drivers: our legitimate interest in complete, comparable leaderboards, as explained above.
  • Diagnostics and product analytics: crash reports and a small number of product events keep the app working and tell us which features matter. Legal basis: our legitimate interests in operating and improving the service, balanced against the minimal impact on you. You can object at any time (see “Your rights”).
  • Location, push notifications and campaign attribution: only with your consent, given through the device permission prompt or the cookie notice, and withdrawable at any time in your device settings, the app’s notification settings, or the cookie policy page.
  • Website logs and page-view analytics: to keep the website running, secure and useful. Legal basis: our legitimate interests.
  • Legal claims and compliance: where we must keep or disclose data to meet a legal obligation or to establish, exercise or defend legal claims.

Automated decisions

We do not make decisions about you by automated means that have legal or similarly significant effects. OpenAI reads result sheets, but a time only counts once you confirm it. The app may suggest that an imported result matches your username; the suggestion becomes yours only if you claim it. Rows with junior markers are hidden by a pattern match on the printed marker, which affects only whether an imported row is displayed.

Who else processes it for us

We use a small number of service providers, each processing data on our instructions under a written contract, and not for their own purposes:

  • Railway (application server and database, Amsterdam, Netherlands): runs our API and hosts our database, so all account and karting data is processed there and this is where your personal data lives at rest.
  • Vercel (website hosting, London region; a US company): website access logs.
  • Cloudinary (media storage and video processing; an Israeli company with storage that may be outside the UK): your photos and videos, and Tip cover images on the website.
  • OpenAI (result-sheet reading, USA): a short-lived link to your evidence photo, or the text of a result email you forwarded, for the time it takes to read it. Under OpenAI’s API terms this content is not used to train its models.
  • Sentry (crash reports, EU data region): the scrubbed crash reports described above.
  • PostHog (analytics, EU cloud): the product events and website page-view events described above.
  • OneSignal (push notifications, USA): your push subscription identifier, platform, and the title and text of each notification, if you enable them.
  • Resend (email, USA): your email address and the content of the service emails we send you, and the result emails you forward to your personal forwarding address.
  • Mapbox (maps in the app, USA): map tile requests from your device, including its IP address, when you open the Tracks map. We have turned Mapbox’s own telemetry off, so it does not receive your location.
  • Apple and Google: deliver push notifications to your device through OneSignal, and handle sign-in if you use Sign in with Apple or Google.

We do not sell personal data to anyone. We disclose it outside this list only if the law requires it, to protect someone’s safety, or if SplitOne is sold or merged, in which case this policy continues to apply.

International transfers

Your data is stored in the European Economic Area (the Netherlands) and processed in the UK and the European Economic Area, which the UK recognises as providing adequate protection. Some providers listed above are established in the United States or may store data there. For those transfers we rely on the UK International Data Transfer Agreement or Addendum, or on the UK–US data bridge where the provider is certified under it. You can ask us for details of the safeguard used for any provider.

How long we keep it

  • Account, profile, karting data, evidence, videos and content: while your account exists, then deleted or anonymised as described under “Deleting your account”. You can delete your account at any time.
  • Sign-in records: sessions expire after 60 days without use; the records are deleted with your account.
  • Unfinished video uploads: removed after six hours.
  • Server access logs (Vercel and Railway): kept by the hosting provider for up to one day for the website and up to seven days for the app’s server, and then deleted automatically. We do not copy them anywhere that keeps them for longer.
  • Crash reports: up to 90 days (Sentry, European region), then deleted automatically. They are kept for that period even after account deletion; see below for what they contain.
  • Product analytics events: up to 12 months (PostHog, European region), then deleted automatically. They are kept for that period even after account deletion, and the account identifier they carry no longer connects to any account once deletion completes.
  • Imported results about non-users: kept as historical results for as long as the leaderboard for that track exists, unless removed on request.
  • Audit trail of administrative and account actions: kept indefinitely. It records who did what and when, by identifier only; it never contains names, email addresses, dates of birth or message contents.
  • Coach interest: until you ask us to remove it, or until the coaching feature launches or we decide not to build it, whichever comes first. It is one email address and nothing else, and it is deleted with your account if you have one.
  • Email correspondence: for as long as needed to deal with your request and any follow-up, then deleted.
  • Database backups: backups of our database are replaced on a rolling schedule; deleted data drops out of them within 90 days at most.

Deleting your account

You can delete your account from inside the app (Profile → Settings → Privacy → My data → Delete account, confirmed with your password), or start a request without the app by following the steps at split1app.com/help/delete-account. Deletion is scheduled after a 30-day grace period, during which you can sign in and cancel it. Before you delete, you can export a copy of your data from the same screen.

When deletion completes:

  • your email address, date of birth, username, display name, home track, sign-in identities, sign-in records, push registration, personal forwarding address, notifications, follows, saves, votes, mentions, evidence photos, forwarded emails, videos, claims and the link between your account and your name as printed on a track’s result sheet are deleted;
  • your posts and comments are removed from view and replaced with a tombstone so that other people’s replies still make sense;
  • your sessions and lap times are kept in anonymised form, under a random token that cannot be linked back to you, because a lap time is part of the shared record of who drove that day; session notes and labels are deleted.

We keep a limited amount of data after deletion, only where we have a genuine need:

  • block records, so that a block placed against an account keeps protecting the person who placed it;
  • reports and moderation records, where needed to enforce our rules or the law;
  • the audit trail, which is append-only and contains identifiers rather than personal details;
  • crash reports and product analytics events, for the retention period above. They never contain your name, email address or anything you wrote; the account identifier they carry no longer connects to any account once deletion completes;
  • records we are legally required to retain.

Imported results that were on the same sheets as your times are not affected by your deletion, because they are not your data. You can also delete individual posts, comments, videos, times and sessions at any time without deleting your account.

Your rights

Under UK GDPR you have the right to:

  • ask what personal data we hold about you, and get a copy of it;
  • have inaccurate data corrected;
  • ask us to erase your data;
  • ask us to restrict how we use it;
  • object to processing we carry out on the basis of legitimate interests;
  • receive the data you gave us in a portable, machine-readable format;
  • withdraw consent at any time, where consent is our legal basis, without affecting what was done before.

The app already gives you most of this directly: the export under My data is your copy of your data in JSON, you can edit your profile and correct times, and you can delete content or your whole account. For anything else, email splitone@split1app.com from the address your account is registered with, or tell us how we can confirm it is you. We will respond within one month; if a request is complex we may take up to two further months, and we will tell you if so. Exercising your rights is free, and we will not treat you differently for doing so.

Complaints

If you think we have handled your data badly, please tell us first so we can put it right. You also have the right to complain to the Information Commissioner’s Office, the UK supervisory authority: Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, telephone 0303 123 1113, ico.org.uk/make-a-complaint.

Children

You must be 13 or over to create a SplitOne account. In the UK, 13 is the age from which you can agree to an online service using your personal data yourself, so we do not ask for a parent’s consent. We check the date of birth you declare against the UK date on the day you sign up; if you are under 13 we refuse the sign-up and store nothing, not even the date you entered. We do not verify age against documents, so if you are a parent and believe your child under 13 has an account, email us and we will close it and delete its data.

Accounts held by drivers aged 13 to 17 are protected in two ways, following the ICO’s Age Appropriate Design Code and the Online Safety Act 2023:

  • Higher-privacy defaults: a private profile, no leaderboard listing and no suggestions of imported results. The account holder can change each of these in Settings.
  • No Community: posts, questions, tips, comments and mentions are only available from age 18. Under-18 accounts cannot read or write there, cannot be mentioned by other drivers and do not see posts in search. This is enforced by our servers, not just hidden in the app.

The app shows no advertising and does no profiling of anyone. Private messaging does not exist. Imported results carrying a junior or under-16 marker are never displayed, whoever they belong to.

Security

All traffic between the app, the website and our servers is encrypted. Passwords are hashed with Argon2id. Uploads are signed by our server for a single file in your own folder, and evidence photos and videos are served only through signed, expiring links. Staff access to the administration tool is role-based and every action is audited. No system is perfectly secure; if we learn of a breach that puts you at risk we will tell you and the ICO as the law requires.

Changes to this policy

We will update this page when what we do changes. If a change materially affects how we handle your data, we will tell you in the app before it takes effect, and we will ask for your consent where the law requires it. The version and date at the top show the last change.