Privacy Policy

1. Quick summary

• We collect your account email, your iRacing telemetry while sessions are active, lap recordings you store, real-circuit sensor data when you use the mobile app, and any data you import from third-party tools.
• We send small slices of your telemetry to AI providers (Anthropic, Fish Audio, ElevenLabs, OpenAI) to generate live commentary, voice and coaching.
• If you choose to create a custom voice clone, we store the voice samples and the synthesised voice model against your account only — we do not use them to train models for other users.
• We never sell your data. We never use your private content for advertising.
• You can delete your account, your voice clones and your stored data at any time from the Account page.
• Imported reference laps for other drivers are kept private to you and never aggregated across users.

2. What we collect

Account information

• Email address, password (stored as a salted hash — never in plaintext)
• Display name (optional, used in commentary lines that address you)
• iRacing customer ID (auto-populated from your Connector once you claim a PC, used to look up your iRacing PB)
• Subscription status and Stripe customer ID
• Bound Connector client IDs (the PCs you've linked to your account)

Session telemetry

• Per-tick samples while iRacing is running and the Connector is active: position, speed, throttle, brake, gear, RPM, lap distance, basic G-forces, GPS lat/lon, steering, clutch, ABS state
• Driver list, gaps, sector times and incident events for the active session
• Track name, car name, session type, lap times

Imported data

• Lap exports you upload from third-party tools (e.g. Garage 61 CSV files), tagged with the source they came from

Voice / microphone

• While you hold the push-to-talk key, the Connector captures audio from your selected microphone, sends it to our STT provider for transcription, then discards the audio. We don't store the raw recording. (See section 6.)
• If you create a custom voice clone, the voice samples you upload are stored against your account and used to synthesise speech you request. See section 7.

Real-circuit sensor data (mobile app)

• GPS location during an active mobile session (lat/lon/altitude/speed/heading)
• Accelerometer and gyroscope readings during the session
• Telemetry frames from a paired BLE device (e.g. RaceBox, Garmin Catalyst) where one is connected
• The venue you selected for the session and any session metadata you entered (car, notes)

Operational data

• Login timestamps, IP address (for fraud / abuse detection), browser user-agent
• Session counts and feature-usage counters (used for free-tier limits and capacity planning)
• Email delivery status (bounces / complaints from our email provider)

3. How we use it

We use your data to:

• Generate live AI commentary, race-engineer calls, spotter calls and (on Works Driver / Constructor) coaching during your iRacing sessions
• Show you lap analyses, deltas vs reference laps, and post-lap coaching reports on the dashboard
• Operate, secure and improve the service
• Charge you for your subscription and process refunds where applicable
• Send transactional email (verification, billing receipts, trial reminders, password resets)
• Send occasional product email if you opted in (you can unsubscribe one-click from any such email)
• Comply with legal obligations

We do not use your private data for advertising. We do not sell your data to third parties.

4. Third-party processors

Delivering RealRacer.ai requires sending parts of your data to specialised providers. Each is bound by a data-processing agreement and processes your data only for the listed purpose.

The list above may change as we add or replace providers. We will update this Policy when it changes materially.

5. Imported lap data (Garage 61, etc.)

RealRacer.ai lets you upload lap exports from third-party tools you already use. When you do this:

• The uploaded file is parsed and stored against your account, tagged with its source (e.g. garage61_import).
• If the lap belongs to you (matched by your display name or email), it is stored as a your-lap — used for your personal benchmarks and may contribute to anonymised aggregate stats.
• If the lap belongs to another driver, it is stored as a reference-only lap. It is visible only to you, used only as a reference you can compare against, and is never aggregated, ranked, or shown to other users.
• You can remove individual imported laps, or bulk-remove all imports from a given source, from the dashboard. Removal is immediate; back-up copies are purged within 30 days.

By uploading third-party lap data, you confirm you obtained that data through that service's own export feature on your own account, and that you have the right to provide it to us.

6. Voice / microphone capture (push-to-talk)

The Connector records from your selected microphone only while you hold the push-to-talk key. It does not listen passively. When you release the key:

• The captured audio is sent over an encrypted connection to our speech-to-text provider (OpenAI Whisper) for transcription.
• The transcript is forwarded to the engineer voice agent for a reply.
• The raw audio is discarded after transcription. We do not store voice recordings.
• Transcripts may be retained briefly with your session log for debugging and abuse-detection, then purged within 30 days.

You can disable PTT entirely from your dashboard or by removing the PTT_KEY from your Connector configuration.

7. Custom voice clones

Where RealRacer.ai offers the option to create a custom voice clone (see Terms section 6), the following applies:

• What we collect: the audio samples you upload, the synthesised voice model produced from them, and metadata you provide (display name for the clone, role assignment within RealRacer.ai).
• How it’s used: the samples are passed to our text-to-speech provider to create a voice model bound to your account. Once the model exists, your samples are retained for the lifetime of the clone so we can rebuild or migrate the model when providers change. The synthesised voice is only invoked to produce speech you request inside RealRacer.ai.
• What we do NOT do: we do not use your voice samples or the clone’s output to train models that other users can access; we do not sell, license or share clone audio or models outside our processors; we do not use clones for marketing or any purpose unrelated to operating your account.
• Sensitive-data note: in some jurisdictions a voice sample may constitute biometric or sensitive personal data (e.g. EU/UK GDPR Art. 9, California CPRA §1798.140(ae)). By uploading a sample you give explicit consent for us to process it for the purposes described in this section.
• Deletion: you can delete any clone (samples + model) from the Account → Voices page at any time. Back-up copies are purged within 30 days. Deleting your account deletes all associated clones.
• Takedown: if you believe a clone in RealRacer.ai uses your voice without permission, email takedown@realracer.ai; we will usually disable the clone within 72 hours pending review.

8. Real-circuit capture (GPS, IMU, BLE)

When you use the RealRacer.ai mobile app for a real-circuit session:

• The app requests permission to use your device’s GPS, motion sensors and Bluetooth before any capture begins. You can deny or revoke each independently from the device’s settings or the in-app Sensors panel.
• Captured sensor data is associated only with the active session and your account. It is not used for advertising, location tracking outside the session, or any cross-user feature without your consent.
• Sessions are bounded by an explicit start and stop in the app; the app does not record sensor data outside an active session.
• GPS coordinates are stored at sample rate (typically 5–10 Hz) for the duration of the session and are used to identify the venue, compute lap times and deltas, and present per-corner coaching.
• You can delete a real-circuit session from the dashboard. Back-up copies are purged within 30 days.

The real-circuit mode is intended for use on closed circuits only (see Terms section 7.3). We do not encourage, facilitate or support its use on public roads.

9. Aggregation & cross-user data

RealRacer.ai computes population benchmarks (e.g. "global best at this track in this car") from telemetry across all users. These benchmarks are anonymised — we do not show your name, email or session details to anyone else, and we do not show other users' identities to you.

The following data is excluded from cross-user aggregation and stays private to you:

• Imported reference-only laps (laps from other drivers you uploaded)
• Laps from sessions where you opted out of aggregation
• Laps tagged as personal practice / scratch

You can opt out of cross-user aggregation entirely from the Account page. Doing so excludes your future telemetry from population benchmarks; we will also remove your historical contribution within 30 days of the request.

10. Email & communications

We send transactional email (verification, billing, trial reminders, password reset) to all account holders — these are operational and cannot be unsubscribed without closing the account.

Marketing email (product updates, new features) is opt-in and can be unsubscribed with one click from any such email, or from your Account page. We honour AWS SES bounce and complaint signals automatically: if our email to you bounces or you mark a message as spam, we suppress further sends to that address.

11. Retention

• Account record: kept while your account is active and for up to 12 months after deletion (for legal / financial record-keeping).
• Telemetry samples: kept hot for 30 days, then archived to cold storage and purged after 12 months unless you specifically star a lap.
• Imported laps: kept until you delete them or close your account; back-ups purged within 30 days of deletion.
• PTT audio: not stored.
• PTT transcripts: up to 30 days.
• Custom voice clones: samples and model retained for the lifetime of the clone; deleted within 30 days of removal from the Account page.
• Real-circuit sessions: sensor data retained against your account until you delete the session; back-ups purged within 30 days of deletion.
• Session logs: 12 months, for capacity planning.
• Stripe payment data: retained by Stripe per their policy; we keep the customer ID and last-4 metadata for as long as your account exists.

12. Your rights

You can:

• Access: see what we hold about you from the Account page (email, display name, subscription, lap counts) and request a full export.
• Correct: update your email and display name from the dashboard.
• Delete: close your account and delete all associated data. Done from the Account page.
• Export: request a copy of your telemetry and imported laps in machine-readable form.
• Opt out: exclude yourself from cross-user aggregation, marketing email, or product analytics, independently of each other.
• Complain: if you are in Australia, the EU, the UK, California or any other jurisdiction with a data-protection regulator, you can lodge a complaint with that regulator. Email us first — we'd rather fix the issue directly.

13. Security

We use industry-standard practices: HTTPS for all browser and Connector traffic, salted-hashed passwords, signed session tokens, a least-privileged AWS account structure, and encrypted at-rest storage for the database. No system is perfectly secure; if you suspect your account has been compromised, email security@realracer.ai immediately.

14. Children's privacy

RealRacer.ai is not directed at children under 16. We do not knowingly collect personal data from anyone under 16. If we become aware that we have, we will delete it.

15. International transfers

RealRacer.ai’s primary infrastructure runs in AWS regions in Australia and the United States. If you access RealRacer.ai from elsewhere, your data will be transferred to and processed in those countries. Our third-party processors may also process data in their own regions (Anthropic, ElevenLabs and OpenAI in the US, Fish Audio in Singapore, Stripe globally).

16. Changes to this Policy

We may update this Policy from time to time. Material changes will be notified by email and/or a banner in the dashboard at least 14 days before they take effect. The "Last updated" date at the top is the easiest way to spot changes.

17. Contact

The data controller for the purposes of EU/UK GDPR is RealRacer.ai (Victoria, Australia). For privacy questions, access requests, deletion requests, or to exercise any right described in section 12: privacy@realracer.ai.
Voice-clone takedowns: takedown@realracer.ai.
General support: support@realracer.ai.
Security incidents: security@realracer.ai.

See also our Terms of Service.