AERO

Privacy in this preview

Technical preview notice · 14 October 2026

This is a technical description of the preview, not a final public-launch privacy policy. Before public launch, the operator must identify the responsible organisation/person, publish a suitable contact, confirm lawful bases, retention and international-transfer arrangements, and complete the younger-user risk review.

Local racing workspace

Your demo nickname, tutorial progress, sessions, telemetry, track packs, notes, preferences and optional onboard video files are stored in this browser. A nickname is enough; do not enter unnecessary personal details. Demo profiles do not authenticate you or isolate different people's data. Anyone using this browser profile may see the same workspace.

Requests outside this device

Cloudflare serves AERO and processes network/request information, including IP addresses. AERO's Worker observability is disabled in the supplied configuration; Cloudflare may still process infrastructure/security logs under the deployed service configuration and terms. Do not put secrets or personal details in URLs.

When you choose a timing URL import, that URL is sent to AERO's relay and the timing provider is contacted by the server. Paste results text instead if you do not want a URL relayed. Import only data you are entitled to use and avoid sharing other drivers' personal details unnecessarily.

Abuse prevention

AERO uses request counters to limit password guessing and excessive API use. These counters are keyed by a secret-derived hash of your IP address, not the plaintext address, and record action categories and expiry times, not request contents. This identifier is pseudonymous, not anonymous. Security-counter cleanup is scheduled after 24 hours without accepted requests for that identifier; provider outages may delay cleanup. Separate daily AI counters enforce the shared usage allowance. Cloudflare processes this security state as our hosting provider.

Weather is optional

Open-Meteo requests are off by default. You can enable them in Privacy Centre. When enabled, imports, weather tools and diagnostics may contact Open-Meteo. It receives your IP address, circuit coordinates and requested dates; AERO does not request device geolocation. Turning weather off prevents future requests but does not erase prior provider records or saved session weather. See Open-Meteo's terms and privacy information.

Accounts and privileged tools

New cloud-account registration is disabled. Existing legacy cloud accounts, if this deployment has a D1 database, contain email, display name, password verifier, account status/plan and timestamps. Login sessions store token hashes and expiry times. Existing users can sign in, export account details or delete their account and login sessions. Local racing files are separate.

The developer and Track Studio tools use secure HttpOnly session cookies. KV stores tester configuration, designer access grants, published tracks, redemption metadata and audit events. Designer names can be aliases. Published track metadata, including authorship/provenance, can be retrieved by other users: do not publish private contact details. Reference images are not uploaded by the studio.

What is not included

No advertising SDK, session replay, marketing analytics pixel, externally hosted font, public driver profile, embedded YouTube player, newsletter signup or payment checkout was found in this build. External links open third-party services only when followed. Features added later need their own review.

Retention and controls

Local data stays until removed, reset or cleared by the browser. Workspace exports exclude video files and some interface preferences. Delete local workspace removes AERO local/session storage, its video database and named legacy caches; it does not delete downloaded backups, server records or privileged login cookies. Sign out of privileged tools separately. Close other AERO tabs before reset.

Legacy account sessions expire after 30 days; expiry does not automatically delete every old database row. Account deletion removes the account and all its session rows. Designer cookies last up to one hour; grants expire after their chosen duration plus 90 days, and studio publish audit entries after 90 days. Rate-limit counters have short expiries. Other KV records, older audit entries, provider logs and backups require the operator's documented retention/deletion process. No universal server deletion promise is made.

Questions, rights and younger drivers

Use AERO's support community for general questions; never post passwords, account exports or private documents there. A direct private privacy-contact route must be confirmed before public launch. The final notice must explain applicable access, correction, deletion, objection, restriction, portability and complaint rights and how to exercise them. Higher-privacy defaults apply to everyone; see Children & privacy. They do not replace an age-appropriate risk assessment or any required parental arrangements.

AERO Intelligence (optional)

Only after you agree and send a question, AERO sends your question and a nameless timing summary (up to 30 laps, lap classifications and calculated session statistics) to Cloudflare Workers AI. Raw telemetry, video, driver names and timing-page links are not attached. Personal information you type in a question is sent too. Cloudflare processes these requests under its service terms and data policies. AERO does not save chat messages on its server; the displayed conversation lasts only in the current page. Clear & withdraw consent removes this conversation and prevents further requests until you agree again; it cannot recall a request already sent. Daily rotating IP hashes and counters are used for abuse prevention, and are cleared after inactivity or replaced on the next day. Your ordinary session analysis remains on your device. AI explanations may be incorrect: check them against the recorded evidence.