Your data

• Everything that's yours: recording, every read of your own runs, the runs themselves, getting them out (files, export), your place on an event's board, a season of backup, and YAW Sim on your PC.
• If YAW ever charges, it's for things that cost money to run or someone's time — an organiser's event screen, an AI coach, a person reviewing your runs, a box for the car — and the price is shown before you pay.
• Never: selling your runs or where you drove, ads, charging you to get your own data out, or making stopping harder than starting.
• Founding drivers. Turn on backup before anything costs money and your account is marked a founding driver: whatever YAW adds later stays free for you.

• Runs, courses, settings and run videos live in this browser's storage on this device. Other websites can't read them, and deleting the app (or its data) deletes them.
• Motion and GPS are read while a session is open, and written into the run.
• The microphone, if you turn it on, works out engine speed from the note. The sound isn't kept — except in run videos, below.
• Camera slip reads frames from the rear camera and keeps none of them.
• Record video of runs saves video — with the engine note, if the mic is on too. It stays on this phone: never backed up, never in a link.
• Photos of your car (Your car in 3D) are kept on this phone, shrunk to 2560 px and stripped of the location the camera writes into a photo, to draw your car in the 3D replay. Never uploaded, never backed up, never in a link.
• A short error log — the last 30 things that went wrong in the app, with the page and the build — is kept on this phone for the self-test. It's never sent anywhere; you can copy it into a message yourself, or clear it.

• Each run you record — its telemetry, GPS track included — and each course you mark is copied to YAW's own server on Cloudflare, with the name and car you typed. Videos and car photos aren't.
• The account is six words. No email, no password, no phone number. The server keeps a one-way hash of a key made from them, never the words — so nobody can reset them for you, and nothing stored says who you are.
• To get rid of it: Backup → Erase everything in the cloud. Every run, course and link goes, and the account with them — straight away, for good, with nobody to ask. The runs on this phone stay.
• Pairing YAW Sim on a PC. The PC shows six digits; typing them here lends that PC this account, as the six words would. The server holds the key in between for ten minutes at most, then only the PC has it. To take it back, tap Disconnect in YAW Sim's settings on that PC. Erase everything in the cloud ends the account on every PC at once.

• Share a link lets anyone holding the link open that one run. A link posted publicly is public.
• It carries the run (GPS track included), your name and car, and a short code that's the same on every link you share. Nothing else — not your other runs, not your account.
• Turn a link off from the run's page, or from Backup → links you've shared, which also shows how often each was opened.
• Deleting a run from this phone doesn't delete its backed-up copy, so its link keeps working until you turn it off.

• Joining an event sends your position, speed and angle to the event while your session is open, with the name, car and Instagram handle (if you gave one) you typed and a random id this phone made. Anyone with the event's code (anyone at all, for an event listed at its track) can watch every car live, not only the big screen. The id is the same at every event and shows on each event's board. It stops when you leave the event or close the session. Your handle shows on the big screen, the results, and on videos fans film of you with YAW Cam.
• The event keeps a results board: your name, car, handle and each run's headline numbers (angle, speed, how long you held it, how many fans hyped it) under that random id. Anyone with the event code can read it, and it stays after the day ends. Your laps aren't on it: they're kept apart, as the next line says.
• Your laps at an event are kept with it. While you drive (above walking pace), the event keeps your position, speed, angle and the way the car's body points at most every 0.4 s, under the same random id, name and car, so the course the whole field drives can be found from everyone's laps. Only the event's organizer (the device that made it) and YAW's owner can read them; anyone else with the code can't. They're kept until the organizer or YAW's owner deletes them (the organizer can, from the event's screen), and each car's stop being kept after about eight hours of driving. To have yours deleted, say so in Send feedback (below).
• The field's course. The organizer's screen finds the course from those laps. Any other event screen can find it from the positions, speeds and angles it's already showing, kept in its browser only while it's open (on the organizer's device, for up to three days, so a reload doesn't lose practice). When the organizer puts the course on the event, what goes to every phone there is the zones (points on the track) and, from two drivers or more, the field's line through them (the middle of everyone's laps), not anyone's positions. Comparing your run with that line, after the run or with Line calls on in the car, happens on your phone and sends nothing.
• Qualifying, called by the organizer. When the event's organizer turns qualifying on, your phone hears it and tags the next run it saves as your qualifying run, on the phone (you can move the tag on the run's page). Nothing new is sent: with sharing on, the tag goes with the run the way it always has.
• Judging. When an event has judges, each run you finish there gets a place for their scores. The points they give it are kept with the event under your name and car, and anyone with the event code can read them: they're the results. Your phone hears the scores for your own runs and puts them on the run; with sharing on, they go with it to YAW, as a qualifying run's always have. Which judge gave which score stays with YAW's server. A judge's link holds their key, kept on their tablet.
• The bracket. When the organizer makes one, your name, car and where you qualified are on it, and anyone with the event code can see it, like the results. Your phone hears the battles you're in and tags your runs in them (lead or chase, and the result) on the phone; with sharing on, the tag goes with the run.
• Battle replays. The organizer's device can play a battle back, or any two cars that ran together, from the laps the event keeps: both cars in 3D, and how close the chase stayed. It reads them the way it reads them for the course, with its organizer key, and works it out in its browser; nothing new is sent or kept, and nobody else can open them.
• YAW's owner keeps a private record of each event's course found from those laps, and how each run there scored on it, with the name you typed. It's for building YAW, and isn't shared.
• Watching an event with YAW Cam. Your phone joins the event as a fan, under a random id it makes and keeps — not the one a car joins with, so watching and driving can't be tied together. Your taps of hype go to the event and count toward the run on screen. So do counts of what you did with the camera — opened it, recorded, clipped, shared or saved a video, turned Tripod on — as numbers for the event's organizer, with nothing about you. The event keeps your random id only to count you once. Your videos never leave your phone unless you share them, and Tripod uses where you're standing on the phone only.
• The day's reel. A take also keeps, on the phone with it, the angle and speed its overlay showed every quarter second, so YAW can find the best few seconds in it. Make the day's reel (in YAW Cam, from your takes; on Today, from the clips of you a coach sent from the stands, lined up with your own runs) cuts them into one video on your phone. Nothing is sent to make it, and it goes nowhere until you share or save it.
• Checking the angle against a video. The video you check a run against (a clip from the stands, or a file you choose) is played and tapped on your device and isn't sent anywhere; your taps are kept in this browser so a reload doesn't lose them. The map you tap landmarks on loads satellite pictures of the track, as the other maps do. The result — how far YAW's angle was from the video's, over how many moments — is kept with the run, and with sharing on it goes to YAW with the run, where YAW's owner adds it up with every other check to say how accurate YAW's angle is.
• The App Store app is this same YAW inside an iPhone app: it sends exactly what the website does, to the same places, and keeps its runs on the phone the same way (separately from the website's — move them with a backup). Links it makes for others point at this website. Apple may send the developer crash reports and usage numbers only if you've allowed it in your iPhone's settings (Privacy → Analytics → Share with App Developers).
• One number about you. Joining also sends how many other events this phone has joined — the count, never which ones. The list stays on the phone.
• Finding an event at the track. YAW fetches the short list of events listed right now — the same list for every phone — and works out on the phone which of them is near you. Where you are is never sent. It only looks when location is already allowed for YAW (or when you tap to look), and it only ever offers: joining is always your tap.
• Listing an event (off unless its organizer turns it on) publishes its name, the place it's at (to about 10 m) and its start and end times to anyone using YAW, until it ends. The relay counts how many new listings each internet address puts up in an hour, to stop one script flooding the list; that count is held in memory and never written down.
• An event's key. The device that starts an event keeps a random key for it, which is how the relay knows who may change the event's course and listing. The relay keeps only a one-way hash of it. The organizer link passes the key to the organizer's own phone after the # in the address — the part a browser never sends to a server — and YAW clears it from the address bar once it's read.
• Notes and clips from your coach. The event's organizer (or whoever runs YAW) can send your phone a short note, or a video they filmed of your run. The event remembers the name you joined with, so a note sent while your phone has no signal or YAW isn't open waits for it on the relay for up to half an hour, then goes. Clips stay with the event (its newest 60) for your phone to fetch; anyone with the event's code can fetch them too.
• Going live streams the same numbers and your position to a room code, for anyone with that code to watch. Nothing from it is kept.
• The public leaderboards. Your best at YAW events goes on the month's public leaderboard (/season) — your name, car, handle, best angle, how long you held it, your runs, how many events and your biggest crowd — and, if you gave an Instagram handle, on a page of your own at /d/your handle, with each event you drove and your best there. Switch On YAW's public leaderboards off in Settings and you're left off both from your next session. The random id your phone joins events with is never shown there.
• YAW's own view of its events. Whoever runs YAW sees what happens at every event in one place: that an event started or was listed, who joined and left (the name, car and handle you typed), each run's headline numbers, and how big the crowd got — what an event's board and big screen already show, across all of them. Each driver's best of the month is kept for a month's leaderboard, under the same random id. Your position isn't kept there either.

• Off unless you switch it on (Settings → Share my runs with YAW). On, every run on this phone — the whole run: angle, speed, the phone's motion sensors and GPS positions, with the name, car and handle you typed — goes to YAW's server, one at a time, never while you're recording. The people building YAW use them to make the angle reading better on real cars, and put everyone's runs at a track together to map its course: the line drivers take there, and where they get sideways. They're copied into the private records the people building YAW keep (a private GitHub repository), and nobody else can read them. The one exception is Ian, the driver YAW is built with: his runs from 2026-10-16 are on YAW's unlisted lab and pitch pages, and the Spotter demo (/pitch/spotter) carries his qualifying run whole (angle, speed, the motion sensors and positions) beside the series' broadcast of it.
• Each track's course, learned. From the runs drivers share and the laps events keep, YAW finds each known track's zones every night and puts them on its server for every phone. What goes there is the zones (points on the track), the field's line through them (the middle of everyone's laps) and how many passes, drivers and days they came from: never anyone's run, lap, name or position. A track's course goes up only once two drivers or more have laps there.
• Your phone makes a random key that names where its runs are kept; nothing else identifies it. Your runs stay on your phone as well.
• A run you tag as your qualifying run keeps YAW's grade and the judges' points you type in on it; a battle run keeps its round, lead or chase, the name you typed for who it was against, and how it went. With sharing on, the run goes again with those on it, so the people building YAW can check its judging against real judges' and keep your season's record. With sharing off, they stay on your phone.
• Delete what I shared (same card) removes every run this phone sent, straight away, and switches sharing off.

• Send feedback (Home, Settings, and the session menu) sends what you write, the name you put with it, your car, the event you're on, the YAW build and the page you were on — to the people building YAW, and only when you tap Send.
• Ticking Attach this phone's details adds this phone's error log (the same one the self-test shows) and its browser's description (the phone model and browser version). Untick it and neither goes. The log never leaves the phone any other way.
• The relay counts how many messages each internet address sends in an hour, in memory only, to stop one script flooding it.
• Whoever runs YAW can have its alerts on their own phone — that a driver joined, a new best of the day, feedback arriving — with the same names and numbers the event's screen shows. For that the relay keeps their phone's push address; nobody else's.

• Once a day, YAW asks its own server for every track's learned course and keeps them on this phone. It asks for all of them at once, so the request says nothing about which track you're at, and it sends nothing else.
• Satellite and street tiles are fetched from Esri and OpenStreetMap whenever a map is on screen. As with any map on the web, they see the request: your IP address, and roughly where the map is looking.
• A run's map has a sketch mode that draws the line without loading any tiles.

Optional, and not switched on yet. If you ever attach one, it's used for two things only: getting back into your account if you lose the six words, and telling you about anything you've paid for. Never passed on.

Drivers at a track — not children. Drive it on a closed course, not a road, and don't read the phone while you're moving: that's what the spoken callouts are for.

This page is meant to describe exactly what the code does. If you find a difference, that's a bug worth reporting to whoever gave you the app — and the fix goes in the code, not this page.