Frequently asked questions

Racelogic VBOX (.vbo), AiM (.xrk and .xrz), MoTeC (.ld, plus the optional .ldx beacon file) and iRacing (.ibt). You upload the file the logger itself produces — nothing has to be exported or converted first. Another logger? Send us one file and we will tell you whether it can be read.

Two ways today. On the web: Sessions → upload, pick the car, the track and the session type, choose the file. On a laptop: the desktop sync agent watches a folder you choose and uploads every new logger file by itself — no dragging files at the circuit. The macOS agent is a signed download from the home page, www.driverpeak.com; the phone app shows your laps but does not upload.

Not published yet. A Windows test build is being tried on real machines in September; whether Windows ships for the beta is decided at the end of that month. Write to support@driverpeak.com to be told when it is ready. The macOS agent is available now — download it from the home page, www.driverpeak.com.

From GPS: the point the car passes most often becomes the start/finish, and every pass starts a new lap. iRacing files use the sim's own lap counter instead. The first and last passes are labelled out lap and in lap; a single pass with no repeat is an unconfirmed segment. A lap shorter than half the session's typical length, or slower than one and a half times its typical time, is kept but marked invalid with the reason shown next to it. Each session also carries a confidence: High with three or more valid laps whose lengths agree within 10 %, Medium with two or more within 25 %, Low otherwise, and No GPS when the file has no usable position data.

For iRacing sessions, the sectors are the sim's own splits. For everything else they are equal thirds of the detected lap, measured from the detected start rather than from a painted line, so they are consistent within a session and not comparable to an official timing sheet. Sector times are shown per lap, and the ideal lap is the best of each sector across your valid laps.

Team staff — engineers, coaches and admins — see every session of the team. Drivers see their own sessions. Other drivers on the team see yours only if an admin switches on “Drivers can see each other's sessions”; it is off by default. Membership is by invitation: an admin sends an invite to a named email address — single-use, valid for 72 hours, with the role chosen by the admin — and it can only be accepted from that address. (An admin can also mint an unaddressed link that any signed-in person can use once.)

It is stored on servers in the United States: the application on Railway (US West), the database on Tiger Cloud (Oregon), the original files on Cloudflare R2. It is used to detect laps, compute sectors and show them to you and to your team under the rules above — nothing else. No advertising, no selling, no third-party analytics on your laps. Crash reports (Sentry, EU) never contain telemetry files or positions; email goes through Resend (EU). The privacy policy is published as a draft while it is under legal review.

Coming. Self-service export (a zip with your account, sessions, laps, sectors, one CSV of telemetry per session and the original files) and account deletion with a seven-day grace period are the next thing being built. Until they ship, email support@driverpeak.com and we do it by hand — the data is yours.

Nothing during the beta. Pricing will be announced before anything changes, and you will be told before you are charged.

iPhone, through TestFlight during the beta. The phone app is for viewing: logbook, session, lap comparison and the track map. Uploads and team creation happen on the web. There is no iPad layout and no Android app yet.

Signed in on the web, use “Report a problem” in the menu or in the footer of any page; on the phone it is on the Team screen. Or email support@driverpeak.com. A person reads every report and replies within two business days during the beta.

status.driverpeak.com shows live checks of the API, the web app and this website, and any incident we know about.