Privacy Policy

Last updated September 30, 2026 · applies to the AsyncRacing iOS app (beta) and asyncracing.com

AsyncRacing is a drag-racing game built on real acceleration telemetry: your phone measures your car, the run is corrected to one standard day, and the corrected number races other people's numbers. This policy says exactly what we collect, why, where it goes, and what you can do about it. The short version: no ads, no cross-app tracking, no data sale, and a public-road run is never scored, ranked or shown to anyone.

What we collect, and why

Account identity. Sign in with Apple gives us the anonymous identifier Apple provides plus the handle you choose. We do not request your name or email from Apple. If you play without signing in, we create an anonymous account identifier so your progress can attach to a real account later.

Waitlist email (website). If you join the list on asyncracing.com, we store the email you enter, for one purpose: telling you when the gates open. It is not used for marketing beyond that, not shared, and you can ask us to remove it at any time.

Location, during a recording. Recording a run reads your precise location (GPS), because GPS speed is the measurement — it is how the app times your pass and keeps the clock honest. Location is also used to: suggest a name for the venue you're at, fetch the local weather (see below), and tag where a run happened. Location is read only while you have the capture screen armed or are using "USE GPS" to name a spot — never in the background, and we do not build a location history.

Motion telemetry, during a recording. The accelerometer/IMU is read at high rate while a capture is armed, fused with GPS into the speed curve that becomes your run. Recording happens only when you arm it and stops when the pass ends.

Where your run goes depends on where you ran it. This is the part most apps bury, so here it is plainly:

• Public road — the run stays on your phone: it is never scored, never ranked and never shown to anyone. The only way it leaves your phone is Share my runs (below): with that turned on, its sensor recording is sent without its place and without your name, to help make the timing more accurate.
• Drag strip or attested private/closed course — if you save the run, these are sent to our server: the run's samples (time / distance / speed), the capture diagnostics (GPS rate and accuracy, sensor rate, peak g, the road grade and how it was measured, how much of the run the motion sensors felt, the launch speed), where the run started (one point, rounded to about 10 metres — never the trace), when it started and which way it was heading, your car's declared basics (name, engine type), your device model and the app build. The server looks up the weather, the slope correction and a road check from that start point itself, re-derives every number, and decides whether the run is admitted, quarantined, or rejected — and says exactly why a run can't rank. The start point is kept with the run, shown to nobody, and deleted with your account.

Sharing your runs to improve the timing (optional, off until you say yes). After a saved run, the app asks once whether you'd like to send that run's sensor recording — the raw GPS and motion readings its times were worked out from — so we can study and improve the timing on real phones in real cars. If you say yes, each run's recording is sent without its place: before it leaves your phone, every GPS position is moved to a fixed point far from anywhere (keeping only the shape of the run), altitude is counted from the start, and the place's name is removed. It is stored with a random ID for your install, the app version and the phone model — not your account, handle or Apple ID, and the server refuses any recording that still has a real position in it. Simulated runs are never sent. Public-road runs are sent too while sharing is on — the same way, without their place — and are still never scored, ranked or shown. Turn it off any time under You → Settings → Share my runs. Because shared recordings aren't tied to your account, deleting your account doesn't reach them: send us the share ID shown under that switch and we'll delete them.

Weather conditions. To correct your run to standard air, our server requests the observation nearest your run's start point and time (station pressure, temperature, dewpoint, wind) from public aviation weather (METAR) sources. The app may request the same to print your card. Those requests share an approximate location with the weather service; they carry no account identity.

Device verification (App Attest). When available, we use Apple's App Attest so your device can cryptographically vouch that a submission comes from an unmodified app on real hardware, and signs the exact run it sends. We store the attestation key identifier, the environment it attested in, and each run's verification result. This is anti-cheat, not tracking; a phone that can't attest still plays, its runs just don't rank.

Run videos and reports. The top spots on each ranked board are shown only once the owner attaches a link to a run video (or an external GPS meter's run). We store the link or note you send and the reviewer's decision; nobody else sees the link, and we never fetch or host the video. You can also report a ranked car (a borrowed car, not their run, a public road, other) with a short note; reports are private to the reviewer, never shown to the reported racer, and closed reports are deleted after 90 days.

Push notifications. If you turn them on, we store your device push token to deliver race results and overnight callouts. Decline or revoke anytime; the game works without them.

Beta diagnostics. During the TestFlight beta, Apple provides us crash logs and the feedback you choose to send through TestFlight, under Apple's own terms. We use them to fix bugs, nothing else.

Bluetooth is used only if you connect an optional external GPS performance meter, and only while recording. Never in the background, never for anything else.

What's public when you rank

Leaderboards are the game. If your run is admitted and ranked, other players can see: your handle, your car's name and short tag, its class and performance index, corrected times (quarter-mile, 60–130, and related marks), trap speed, venue class (strip / private — never a precise location), and race results against other players. Aggregated, weather-normalized statistics (for example, where your car sits in the fleet distribution) are computed from admitted runs. Your precise location and your raw GPS coordinates are not shown to anyone.

Public run pages

A run you share gets a public page. Sharing a run from the app creates a link (asyncracing.com/r/…) that anyone who has it can open, and every racer has a racer page (asyncracing.com/racer/handle) listing the cars other players can already see in the app. A run page shows your handle and typical reaction time, the car's name, short tag, class and performance index, its ranking, the run's times and trap speeds, its speed trace (time, distance and speed — no positions), the corrected numbers and the air they were corrected for, the date, and a venue label only when the run was at a listed drag strip — anywhere else reads "a closed course" or "private land". It never shows your location, your GPS coordinates, your device, or your account details. The racer page shows your handle, win–loss record and red lights, best streak, best and typical reaction time, the date you joined, and those cars. Both ask search engines not to index them, and each carries a "report this page" link. To take a page down, delete the car in the app (its page stops working right away; previews already posted in a chat may keep their picture) or delete your account.

What we do not do

• No advertising identifier (IDFA), no ads, and no tracking across other apps or websites.
• No sale or rental of your data. No data brokers.
• No background collection — location and motion are read only while you have a capture armed.
• No invasive analytics: asyncracing.com uses Vercel Web Analytics — cookieless, first-party visit counting (pages, referrers, country, device type). It sets no cookies, stores no personal profile, and cannot follow you anywhere else. Beyond that, the site stores the email you type into the waitlist and, for shared run links, a count of how many times each was opened — no IP address, no cookie, nothing about who opened it.
• No scoring, ranking or showing of public-road runs — the only way one leaves your phone is a Share my runs recording, without its place or your name.

Your choices and rights

Play without an account. The full local game works signed-out. Ranking on public leaderboards requires Sign in with Apple.

Delete your account and data. Settings → Delete Account permanently deletes your account and all associated server data — runs (start points included), cars, race history, leaderboard standings, attestation records, evidence links and notes, reports you filed, and push tokens — plus everything on the device. Immediate and irreversible.

Access, correction, export, waitlist removal. Email us (below) to get a copy of your data, correct something, or remove your waitlist email. We answer regardless of where you live; if your jurisdiction gives you specific rights (GDPR, CCPA/CPRA, and the like), we honor them. California residents: we do not sell or share personal information as those terms are defined in the CCPA/CPRA, so there is nothing to opt out of.

Permissions. Revoke location, motion, Bluetooth, or notifications anytime in iOS Settings. The app keeps working; it just can't record new runs without the sensors a recording needs.

Data storage & retention

Server data lives with our backend provider, Supabase (Postgres, hosted in the United States), protected by row-level security so clients can only touch what's theirs. Local data lives on your device. We keep server data until you delete your account or ask us to remove it. Runs the server rejects keep only a minimal rejection record (reason, sample count, when) for anti-abuse; the rejected telemetry itself is not retained. During the beta, server data may occasionally be reset — another reason road runs and practice passes stay yours, on-device.

Children

AsyncRacing involves real cars and real speed. It is not directed at children under 13, and we do not knowingly collect their data — if we learn we have, we delete it. Recording requires a legally operated vehicle; see the Terms.

Changes

If this policy changes in a way that matters, we'll say so in the app or on this page before it takes effect, with the date above updated.

Contact

Questions, data requests, complaints: titef.beckham@gmail.com