Privacy Policy
This policy covers the Racemator iOS app and the racemator.com website. Racemator is operated from Australia by N. TURCAROLA PTY. LTD. (ABN 74 005 900 041) (“we”, “us”) — the entity responsible for the personal information described in this policy.
The short version
- There are no user accounts — we never ask for your name, email address, or a password.
- Subscriptions are billed by Apple; we never see your payment details. We keep your plan/product purchase history and Apple transaction identifiers to run your subscription.
- Your telemetry stays on your device unless you choose to share it or run an AI analysis. AI sends session data to our servers and the processor selected for your plan, after asking your permission. To show weather and satellite photos, the app asks Apple about the track’s area — never about your laps.
- The app reads your phone’s location only to find the track you’re at. Your position is used on your phone and is never stored or sent.
- An analysis finishes on our servers even if your phone loses signal or you close the app, and we hold the result so your app can collect it next time it connects.
- We keep limited AI-request and result data for a period to deliver and cache your analyses, improve the service, investigate problems, and detect, moderate and prevent abuse — details and retention periods below. A session you never run an AI feature on is never sent to us and never stored by us.
- If you subscribe, the app can send us usage analytics — which screens and features you use and for how long, never your telemetry or anything you type. You can turn it off in Settings, and it is never collected without a paid subscription.
- No ads, no third-party analytics services, no cross-app tracking, and nothing sold or shared for advertising. Data goes to service providers only as described below. Our own website statistics are self-hosted and set no cookies.
No accounts
Racemator has no sign-up. An active App Store subscription is the only credential. Internally we generate a random subscriber identifier and associate it with your subscription — that identifier is not your name, email, phone number, or Apple ID, and we cannot use it to identify you outside the service.
Subscriptions and Apple
Purchases are processed by Apple through the App Store. To verify that a subscription is active, we receive cryptographically signed subscription information from Apple: transaction identifiers, the product purchased, and its status and expiry. We keep this purchase history — which plan/product each anonymous subscriber bought, with Apple transaction identifiers — to verify and run the subscription, and, counted by plan, for our own product analytics (how many drivers are on each plan, and which plan's limits they reach). We never receive your payment method, billing address, or Apple ID email. Apple’s handling of your purchase is covered by Apple’s privacy policy.
Your telemetry data
Sessions you download from your kart’s data logger — including channel data and the GPS positions the logger recorded on track — are stored on your device. Nothing is uploaded automatically, synced, or backed up by us. Deleting a session in the app, or deleting the app, removes that data from your device.
The only time session data is sent to us is when you run an AI feature on it — see AI analysis. To show the weather and satellite photos for a track, the app asks Apple about the track’s area — see Apple weather and maps.
Apple weather and maps
Two features ask Apple about the place a session was driven. Neither sends anything to us, and neither sends your telemetry.
- Weather. To show the weather at the track while a session ran, and to give an AI analysis an estimate of it, the app sends Apple Weather the track’s approximate location (to about 1 km) and a time window around the session’s date. The weather that comes back is kept in the app’s memory only, never stored. Weather data comes from Apple Weather and its data sources.
- Satellite photos. To draw a track over a satellite photo, the app asks Apple Maps for a photo of the area around the track.
Apple’s handling of these requests is covered by Apple’s privacy policy.
Your phone’s location
The app reads where your phone is only to find the track you’re at, for a race day’s venue: when you tap Use my location (iOS asks your permission the first time). Your position is used on your phone there and then, and is never stored, logged or sent to us or anyone else. The app keeps only the track it found, on your phone. You can turn location off for Racemator in the iOS Settings app at any time.
AI analysis
When you run an AI debrief, comparison, focused analysis, question or queued batch, the app sends session-derived telemetry (lap times, channel data, track information, any kart-setup notes you entered, and the app’s weather estimate for the session when it has one) plus your questions to our servers. Before sending session data for AI analysis the first time, the app explains this sharing and asks your permission. You can withdraw it in Settings → Privacy and analytics → AI analysis to stop future AI sharing; this does not undo requests already sent or change the retention periods below.
We choose the AI processor for each plan and may change it. Requests may go to:
- Anthropic (Claude models; United States), the current default for paid plans with AI;
- ByteDance, through its BytePlus cloud (GLM
models), using
ark.ap-southeast.bytepluses.com, BytePlus’s Asia-Pacific (Southeast) regional endpoint; the endpoint name alone does not guarantee a particular processing country; - OpenRouter, a United States model gateway which forwards requests to the model’s maker, for example Mistral AI in the European Union;
- Mistral AI directly (European Union); or
- models we host ourselves on our own infrastructure, in which case the AI content does not leave our infrastructure.
Third-party providers act as processors to produce the response, under their data-processing terms and our instructions. We do not use your content to train AI models, and we do not permit providers to use it for training where the provider offers that control.
The analysis is provided for information only. It explains what your telemetry shows and may suggest things to try, but it is not coaching: it is not a driver coach and is no substitute for professional coaching, engineering or safety advice.
The data sent for that request, and the answer that comes back, are kept on our servers for up to 90 days. We keep them to deliver the answer (an analysis can finish after you close the app), to investigate faults, and to detect and prevent abuse of the service. Sessions you do not run an AI feature on are not sent to us, and so are not stored by us at all.
Each request is metered (token counts, timestamps, model used, and the feature run) against your anonymous subscriber identifier to enforce fair-use limits and plan features.
An analysis runs to completion on our servers once you start it, whether or not your device stays connected — so a dropped signal at a track, backgrounding the app, or closing it does not lose the analysis you have already paid for. We therefore hold the completed result on our servers so your app can collect it when it next connects, and so it can pick up a stream that was interrupted. You can cancel a running analysis at any time from the app; the partial result is kept the same way.
Several analyses at once. On Race Team you can queue a batch of analyses. The app prepares each one’s session data on your device and sends it to us, where it waits its turn and is analysed one after another, whether or not your device stays connected. Each one’s data leaves the queue once it has been analysed (from then on it is kept like any other analysis) or when you cancel it; anything still waiting after 30 days is cancelled and deleted.
Notifications. If you allow notifications, the app sends this device’s push token with each AI request — a debrief, a comparison, a question or a batch — so we can tell you when it is ready, when an answer needs the app open to finish, or that it did not finish, even if the app is closed. The notification goes through Apple’s push service with a generic message (“Your answer is ready to view”) and the analysis’s or batch’s internal reference, never your session’s name or data. We hold the token only in memory until that request finishes (up to 30 seconds longer for an answer waiting on the app; for a batch, until the whole batch has finished, which can take longer while it waits for an allowance to reset), and use it only for that request’s or batch’s notifications; we never store it, and never share it with anyone else.
Service delivery, improvement, moderation and abuse prevention
We may retain, cache, process and review AI-analysis request and result content, together with technical metadata (timestamps, token counts, app version, subscription tier, model and endpoint used, and error details). We use this to:
- deliver, cache and re-deliver your analyses — including holding a completed or partial result until your app collects it, and resuming an interrupted one;
- operate, secure, maintain and improve the service, including the quality and accuracy of debriefs and comparisons;
- investigate and fix problems, including issues you report to us;
- detect, investigate, moderate and prevent spam, fraud, abuse, and use of the service outside its intended purpose (for example rate-limit evasion, prompt manipulation, or content that breaches our terms or a model provider’s policies), and to enforce our terms;
- comply with legal obligations and respond to lawful requests; and
- plan capacity and measure aggregate feature usage.
Review is mostly automated; a person may inspect specific requests or results when investigating a fault, a report, or suspected abuse. This data is never sold, never shared for advertising, and access is restricted to the operator and to service providers acting on our instructions.
Diagnostics and logs
The app keeps a diagnostic log on your device. It is shared with us only when you choose to send it (for example via “Report a problem” in Settings). Our servers also keep standard access logs — IP address, request path, status, and user agent — used for security and operations.
Device integrity (App Attest)
We use Apple’s App Attest to verify that requests come from a genuine, unmodified copy of Racemator on real Apple hardware. This is Apple-provided attestation of the app installation — it is not device fingerprinting and does not identify you.
Usage analytics (app)
To work out which parts of Racemator are worth improving, the app can send us a small record of how it is used. This applies only while you have an active paid subscription: with no subscription, or once one lapses, the app sends nothing and our servers refuse to accept anything.
What it contains:
- Which screen you were on and how long you spent there.
- Which features you used — for example opening or downloading a session, how many laps you overlaid, how many sessions you compared, creating a championship, or reaching a screen that asks you to upgrade.
- Your app version, device model, operating-system version, and your subscription tier.
- A marker that groups one run of the app together. It is generated fresh each time the app starts and never reused for a later run; it is saved on your device only with events still waiting to be sent, until they are sent or discarded.
It is tied to the same anonymous subscriber identifier described under No accounts — not to your name or email, because we never have them. It never includes your telemetry or lap data, the contents of anything you type, your location, or any advertising identifier.
It is ours alone: it goes to our own servers, is used only to understand and improve the app, is not used for advertising, and is never sold or shared. Retention is in the table below.
Turning it on or off. Settings → Privacy and analytics → “Share usage analytics”. For subscribers it starts on — except in the EEA, the UK, Switzerland, South Korea, Türkiye and India, where it starts off and collects nothing unless you switch it on. When you turn it off, the app records that you did so (that one event tells us people are opting out) and then stops — anything still waiting to be sent is discarded. Turning it off stops future collection; information already sent is deleted on the schedule in the retention table, or sooner if you ask us (Your rights). Using “Reset all app data” in Settings returns the app to its defaults, which returns this setting to whichever way it starts where you are.
Analytics, advertising and tracking
The app contains no advertising and no third-party analytics or tracking SDKs, and we do not track you across other companies’ apps or websites. Nothing we collect is sold or shared for advertising, and we run no advertising of any kind. Sharing with service providers is limited to the purposes described in this policy.
The racemator.com website keeps basic page-view statistics (which pages are visited, and roughly where visits come from) using self-hosted software running on our own infrastructure — not a third-party analytics service. It sets no cookies and stores nothing in your browser. To count visits without them, our server derives a visit identifier from a one-way hash of your IP address and browser details with a secret that changes every month, so your visits within a month can be grouped together but not linked across months; your IP address itself is not kept. The data never leaves our systems. App usage analytics are separate and are described under Usage analytics.
How long we keep data
| Data | Kept for |
|---|---|
| AI request and result content (including a completed or partial analysis held for your app to collect) | Up to 90 days, then deleted. A result held purely for delivery is normally removed sooner, once it has been collected or has aged out. Content may be kept longer while it is needed for a fault we are investigating, or for an active abuse, moderation, security or legal matter. |
| Session data waiting in a batch (Race Team) | Until it has been analysed or its batch is cancelled, and at most 30 days; once analysed, as AI request content above. |
| Push token (when you allow notifications) | Only in memory, until the request or batch it came with finishes (up to 30 seconds longer for an answer waiting on the app); never stored. |
| Server access logs | Up to 30 days. |
| Usage metering (token counts per day) | Up to 24 months. |
| Usage analytics (which screens and features were used, and for how long — subscribers only, and only while the setting is on) | Up to 24 months, then deleted. |
| Subscription records and purchase history (plan/product bought, Apple transaction identifiers, status, linked to your anonymous subscriber identifier) | While your subscription is active and for up to 24 months after it lapses. |
| Aggregated, de-identified statistics (which cannot be linked back to a subscriber) | May be kept indefinitely. |
Where data is processed
Our servers, including any models we host ourselves, are operated in Australia. Third-party AI requests may be processed by Anthropic in the United States, ByteDance through BytePlus’s Asia-Pacific (Southeast) regional endpoint, OpenRouter in the United States and the model maker it forwards to (for example Mistral AI in the European Union), or Mistral AI directly in the European Union. We select the processor per plan and may change it, as described under AI analysis; self-hosted AI content stays on our infrastructure. The BytePlus endpoint does not by itself establish a particular processing country. Requests to third-party providers may therefore be processed outside Australia and, for EEA/UK users, outside the EEA/UK. The disclosures in this policy still apply, and we rely on the contractual protections in our processors’ data-processing terms.
Your rights
We handle personal information in accordance with the Australian Privacy Act 1988 (the Australian Privacy Principles). If you are in the EU/EEA or UK, you also have rights under the GDPR — including access, correction, and erasure. Our lawful bases are performance of a contract (providing the service you subscribed to) and legitimate interests (service improvement, security, and abuse prevention). Where usage analytics requires consent — the EEA, the UK, Switzerland, South Korea, Türkiye and India — the basis is your consent, given by switching the setting on, and you can withdraw it at any time by switching it off.
Because there are no accounts, we may need help locating data that relates to you: include your App Store subscription information (for example the original transaction identifier shown in your Apple purchase history) when you contact us, and we will locate, export, or delete the associated records where the law requires.
Children
Racemator does not ask for personal information from anyone, including children. Subscriptions can only be purchased through an Apple Account, subject to Apple’s age and family-sharing rules. The app is not directed at children under 13 (or the age of digital consent where you live, if that is higher), and we do not knowingly collect their personal information. If you believe a child has provided us with personal information, contact us and we will delete it.
Changes to this policy
We may update this policy at any time. The version posted here, with its date, is the one that applies from that date onwards. Material changes will also be noted in the app’s release notes.
A new version does not change how we handled data before it was posted, and where we rely on your consent — AI sharing, and the usage-analytics switch in the regions listed under Usage analytics (app) — a material change to what we collect or share means asking again, not simply posting a new date.
Contact
Privacy questions, access requests, or complaints: contact@racemator.com. If you are not satisfied with our response, you may complain to the Office of the Australian Information Commissioner (OAIC).