RaceCortex Privacy Policy
Last updated: 17 June 2026
RaceCortex ("RaceCortex," "we," "us") is software operated by RaceCortex LLC (a single-member LLC in Arkansas, USA). This policy explains what information the RaceCortex desktop app, the AI race engineer ("Clive"), and our website (racecortex.com) collect, why, and who processes it. RaceCortex is currently in closed beta; data practices may change as the product develops, and we'll update this policy and the "last updated" date when they do.
By creating an account or using RaceCortex during the beta, you agree to this policy.
The short version
- We collect what we need to run the service: your account email, your gameplay/telemetry data (so Clive can engineer for you), your push-to-talk voice (transcribed to text), basic usage metrics (to keep the service running and prevent runaway costs), and diagnostics (to fix crashes and bugs).
- A lot of data never leaves your PC — your iRacing telemetry, local session history, and preferences are processed locally.
- We do not sell your data and don't show ads.
- Automatic crash reporting can be turned off in Settings.
1. Information we collect
Account information. When you redeem a beta invite and sign in, we store your email address and a securely hashed password (handled by our auth provider, Supabase — we never store your password in plain text). We also record your beta invite code and beta-access status.
Gameplay & telemetry data (sent to the AI to generate engineer responses). While you drive, RaceCortex reads live data from iRacing and sends the relevant context to our AI proxy for processing. This includes things like your car and track, lap and sector times, position and gaps, fuel, tyre/temperature readings, incidents, and session type, plus your iRacing display name, iRating, and license (so Clive can address you and tailor advice). This is used to produce real-time engineer callouts and answers; it is processed in real time and is not used to build an advertising profile.
Voice (push-to-talk). When you hold your push-to-talk key and speak, the captured audio is sent to our speech-to-text provider (Groq) for transcription. We use the resulting text to understand your request. We do not retain your voice recordings.
Usage & cost metrics. To operate the service and enforce per-user spending limits (so one runaway client can't exhaust our API budget), we record per-account, per-day counts and estimated costs of API calls and token usage by AI model. This is operational/aggregate data tied to your account, not the content of your conversations.
Diagnostics & crash reports. To find and fix problems, the app sends crash and error reports to our diagnostics provider (Sentry). These include technical details such as error/stack traces, the app version, your operating system, and hardware (e.g., GPU/CPU) information, associated with your account email. If you use the "Report a problem" button, we also receive your typed message, your optional contact email, and your recent app log files (we automatically redact obvious secrets such as tokens before sending; logs may still contain gameplay details like car/track names). Automatic crash reporting is on by default and can be turned off in Settings → it does not disable the manual "Report a problem" button, which only sends when you click it.
Website & technical data. When you download the app or check for updates, our hosting/CDN providers (Vercel, Cloudflare) process standard request information such as IP address and request metadata in server logs. Our website also uses Vercel Analytics — a privacy-friendly, cookieless analytics tool — to measure aggregate site traffic (such as page views and referrers); it does not use cookies or build a personal profile of you.
2. What stays on your device
Much of what RaceCortex handles is processed locally and not collected by us, including: your raw iRacing telemetry stream, locally cached session history and analysis, your saved preferences and overlay layout, and your application logs (these stay on your PC unless you choose to send them via "Report a problem"). Your sign-in token is stored securely in the Windows Credential Manager on your machine.
3. How we use information
- Provide the service — generate Clive's engineer responses, coaching, and strategy.
- Operate and protect it — authenticate you, enforce spending limits, prevent abuse, and keep costs sustainable.
- Improve it — diagnose crashes/bugs and understand aggregate usage during the beta.
- Communicate — send you beta onboarding, important service notices, and respond to your reports.
We do not sell personal information, and we do not use your gameplay or voice data to serve advertising.
4. Who processes your data (sub-processors)
We rely on these third-party services to run RaceCortex. Each processes only what's needed for its function, under its own terms and security:
| Provider | Purpose | Data involved |
|---|---|---|
| Supabase | Accounts/auth + operational database | Email, hashed password, beta status, usage metrics |
| Vercel (incl. AI Gateway) | Hosts our API proxy; routes AI requests | Request metadata; relays gameplay context to Anthropic |
| Anthropic (Claude) | Generates Clive's responses/coaching | Gameplay/telemetry context + your transcribed requests |
| Groq | Speech-to-text for push-to-talk | Your push-to-talk audio (transcribed, not retained by us) |
| Inworld | Text-to-speech (Clive's voice) | The text of Clive's spoken responses (may include your name and race context) |
| Sentry | Crash/error diagnostics | Error traces, app/OS/hardware info, account email, and—if you submit a report—your message + redacted logs |
| Cloudflare | DNS + installer/update distribution | IP/request metadata for downloads and update checks |
| Vercel Analytics | Privacy-friendly website analytics | Cookieless, aggregate page views & referrers (no personal profile) |
| Resend | Transactional/onboarding email | Your email address |
We are not affiliated with iRacing; RaceCortex reads iRacing's local telemetry on your machine but does not access your iRacing account.
5. Data retention
During the beta we keep account and usage data for as long as your account is active, and diagnostic data per our providers' defaults (for example, Sentry currently retains events about 30 days). When the beta ends or you ask us to delete your account, we'll delete or anonymize your personal data within a reasonable period, except where we must keep it for legal/security reasons.
6. Security
Data in transit is encrypted (HTTPS/TLS). Passwords are stored hashed by Supabase; your session token is stored in the Windows Credential Manager. No system is perfectly secure, but we take reasonable measures appropriate to a beta of this size.
7. Your choices and rights
- Crash reporting: turn it off anytime in Settings → "Send crash reports."
- Access / correction / deletion: email us at privacy@racecortex.com and we'll help you access or delete your account data.
- Region-specific rights: depending on where you live (e.g., the EU/UK under GDPR, or California under CCPA), you may have additional rights such as access, deletion, portability, or objection. We'll honor applicable requests; contact us at the address above. (Full automated rights tooling is planned for public launch.)
8. Children
RaceCortex is not directed to children. You must be at least 18 to create an account.
9. International users
RaceCortex is operated by RaceCortex LLC, based in Arkansas, USA. By using the Service, you understand that your data may be transferred to and processed in the United States.
10. Changes to this policy
We'll post changes here and update the "last updated" date; significant changes will be communicated to beta users by email.
11. Contact
Questions or requests: privacy@racecortex.com, RaceCortex LLC, Arkansas, USA.