Privacy policy

Jordan Caruso (JRC Dynamics) is the data controller for this service. We handle personal information under the Australian Privacy Act 1988 (Australian Privacy Principles). If you are in the UK or EEA, we also process your data under the UK GDPR / EU GDPR — our lawful bases are performance of a contract (running the account you asked for) and legitimate interests (keeping the service secure and working).

Sign-in uses a code or link we email you, or optionally Apple or Google. We store your email address to identify the account, plus a display name and avatar if you set one. Session cookies keep you signed in on devices you use. We do not store passwords.

You get an account by choosing a plan or a free trial on our website, by signing up in the JRC Trackside app, or with an access code. The email address you enter when redeeming a code is stored so the sign-in can complete.

Content you create: runs and run notes, lap times, car and tyre records, setup sheets you upload (PDF) and the values extracted from them, race results, track and event records, videos you upload for analysis, and your app settings.

Collected automatically: approximate weather conditions for a run (fetched by track location and time), timestamps, and standard server logs used to operate and secure the service.

We count page views to see which pages people visit. This uses no cookies, stores no IP address, and is aggregate only — it cannot identify you or follow you to another site.

When you use the Engineer (chat, suggestions, quick fixes), automatic setup-sheet reading, lap times read from a screenshot, or setup changes you describe in words, the relevant parts of your data — run history, setup values, notes, lap times, the text you typed, and uploaded setup sheet images and screenshots — are sent to our AI provider, OpenAI, to generate the response. We do not send your email address or account identifiers. A teammate’s Engineer can send the runs you share with their team too, as the next section says.

Engineer output is generated guidance, not verified advice. See the Terms.

Your runs, notes, videos and setup sheets are private to your account and are never shown to other users unless you join a team.

Joining a team is always your choice: an invite has to be accepted by you before anything is shared, and nobody can add you to a team without that. Once you accept, other members of that team can see your runs, setups and lap data — including runs logged before you joined — and you can see theirs. Individual runs can be withheld with “Share this run with my teams”, and leaving a team ends the team’s access to your data.

Your day cards are shared with the team the same way: the notes, figures and summary for a day or a weekend, built only from the runs you share. Each card’s Team switch keeps that day to you. A day that holds a run you keep to yourself starts kept to you, and so do day notes and summaries written before day cards were shared, until you switch their day on.

Your teammates can also open the RaceBox files on the runs you share and compare their laps with yours in Data analysis. Their Engineer can read those runs (setups, laps, RaceBox files, handling marks and ratings, never your notes) and sends them to OpenAI to answer their questions, with your name but never your email. Both start once you’ve been told: the one-time note in the app, or the line shown when you join a team or start one.

Records you add to the shared catalog — tracks, tyres, additives and chassis types — are visible to other users by design, because every driver uses the same catalog. If you add a chassis by uploading its setup sheet, the blank sheet becomes that chassis’s sheet for every driver: we clear the values typed into its boxes first.

Public timing pages also show other drivers. Race results list everyone in a race, and practice lists show who was on track and when, by name or transponder number, with their lap times. The app shows you what those pages show, so you can compare your laps with theirs. We do this under our legitimate interest in letting drivers compare against published results.

If you set your practice laps to private in your MYLAPS account, MYLAPS refuses them to everyone except you, and that includes us.

We use these providers to run the service. We do not sell your data to anyone.

• Vercel — application hosting, file storage (uploads), and anonymous page counts.
• Neon — managed PostgreSQL database.
• Stripe — payments and subscriptions. Your card details go to Stripe, never to us. We keep only Stripe's fingerprint of the card a free trial starts with, so each card gets one trial.
• Meta (Facebook and Instagram) — if you tap one of our ads and then start a free trial on our website, the thank-you page tells Meta, so it can show our ads to similar racers. A cookie remembers the ad for up to 90 days, and the thank-you page uses Meta's cookies. Nothing from inside the app is sent, and we don't do this in the EU, UK or Switzerland.
• OpenAI — AI features, as described above.
• Our email provider — sending sign-in links and notifications.
• Sentry — reports of errors in the app (the page, browser and error), so we can fix them.
• Apple and Google — only if you choose to sign in with them.
• Apple, Google and browser push services — only if you enable notifications.
• Open-Meteo — weather lookup by track location and time.
• OpenStreetMap (Nominatim) — finding a track’s location from the town or address you type.

To find your sessions and lap times, the app reads public timing pages on LiveRC, Speedhive, Sensible Laps, RC-Results and MyRCM, using the link, driver name or transponder number you give it. Those sites are not sent your account data.

For MyRCM, the app keeps a list of European meetings and who is entered in each, with the names, nations, classes and transponder numbers MyRCM publishes on its entry lists, so it can find your races wherever a meeting is listed. It also remembers which meeting was held at a track on a day, not who told it. Each meeting is deleted 45 days after it ends.

Some of these providers process data outside Australia, including in the United States. We may also disclose data if required by law.

Your content is kept while your account exists. Server logs are kept for a short period for security and debugging. Chassis sheets you added to the shared catalog stay after your account is deleted, without your values.

You can access and edit your data in the app at any time. You can delete your account from Settings → Delete account, which permanently removes your account, your runs and records, and your uploaded files. This cannot be undone.

You may also ask us for a copy of your data, ask us to correct it, or object to how we use it. Email support@jrcdynamics.com and we will respond within 30 days. If you are unhappy with our response you can complain to the Office of the Australian Information Commissioner (oaic.gov.au), or to your local data protection authority.

Traffic is served over HTTPS, data is stored with managed providers, and access to your content requires being signed in to your account. No service can promise perfect security; please do not upload anything you would not want stored on a third-party cloud.

This service is not directed at children under 13, and we do not knowingly collect their data. If a child has created an account, contact us and we will delete it.

We may update this policy as the service changes. If a change affects how we use your data, we will email you at least 30 days before it applies. The date below shows the current version.