Manage your account in one place
Your driver profile, result emails and privacy choices are in the account menu.
Open your account menu
Select your avatar or initials. Profile, Settings, Help and Sign out are together here. Profile and Settings open as full pages; Help opens in a separate tab.
Profile: your name and home K1
Edit your driver name and choose your home venue, then save. Your username is permanent and displayed for reference. Your home K1 helps the app start in a useful place; it does not reassign old sessions or stop you browsing other venues.
Changing these choices does not replay completed setup.
Settings: connections and privacy
- Connections: set up result forwarding and review received emails.
- Privacy & account: review verified account details, required acknowledgements and optional sensor choices.
- Help & support: find this guide or contact support when the available recovery steps do not solve the issue.
No Community sharing is enabled by choosing a home venue or opening Settings. The adult Community pilot requires its own participation and statistics choices. Community data can be downloaded from its Privacy & sharing tab; whole-account export and deletion keep the support route below.
Understand the two sensor choices
Sensor Data consent and private native cloud delivery are separate. Neither is required for your K1 email results.
Consent recorded for native cloud delivery describes your saved choice. Uploads still require an eligible account and device. This label is not proof that a device is collecting or uploading data.
Withdrawal requires an explicit confirmation. A cleanup marked pending or failed is not finished deletion; use the offered retry or support route. Native cloud withdrawal and the broader Sensor Data withdrawal have different scopes, described before you confirm. Device copies, Sensor Logger recordings and account deletion are separate concerns.
Saved changes and account access
Your supported profile changes, notes, plans, goals and kart records save to your authenticated account. Browsing filters and temporary Coach conversation are not the same as saved driving evidence.
If a save fails, keep the draft and read the recovery message. Explicit reload can discard unsaved edits. If one part saved and another did not, the message identifies the partial result; do not assume the whole change succeeded.
Sign out does not delete your account or driving history. Deactivated access is also not deletion. Eligible privacy cleanup remains reachable even when access to driving history is blocked. Use the privacy and support contact for account-data or deletion requests.
Open Profile ↗ · Open Settings ↗ · Open Privacy & account ↗
Demo reset and conversion
The focused Demo saves supported annotations, kart assignments, plans, goals and simulated choices privately. A fixture update does not erase current testers' edits. Only the owner can reset Demo data, restart onboarding or review a conversion to Real.
Conversion requires explicit target confirmation and verified removal of the registered synthetic footprint. Unexpected real resources stop the operation. Your verified account, permanent username and required legal/audit records stay; fictional history, Demo goals, home-venue choices and simulated sharing do not carry into Real use. Sign in again and complete Real setup before operational result forwarding becomes available.
Feedback during early access
Feedback is available only when the owner enables it for your account. It is independent of Community, and works for enabled Demo and Real testers. Use Feedback in the header or Feedback about this inside an open dialog. Choose Bug, Question, Improvement / idea or General feedback, then describe what you noticed. Bugs can include what you expected.
The report remembers the page or section where you started. Choose a section identifies a chart or registered area without activating the controls underneath. Review the included page reference, app version, device capture time, browser family, viewport and Demo/Real origin before sending. Routes do not include personal record IDs or query strings. Notes, account credentials, result files, recordings and diagnostic dumps are not collected automatically.
Images are optional and off by default. Choose your own image, crop it and cover private areas, then review it. Only those reviewed pixels are sent; the original file, filename and metadata are excluded. You can remove the image and send text only.
Cancel keeps the draft in this tab. Navigation does not change its captured context. Closing the tab or signing out discards the draft. If confirmation is lost, Retry same report recovers the same submission. If access is switched off, submission stops and you can copy or discard the draft.
Submitted feedback is private to the owner and is retained separately from fictional driving data. Demo reset and conversion preserve it. Reports are kept for 365 days and images for 30 days, with expired content removed by the daily retention job. Account erasure removes associated feedback. Contact support for a data request.
Owners can enable Feedback when inviting someone, manage it in Owner → Accounts, and review reports in Owner → Feedback. Complete means Resolved; Decline means Not planned; Reopen returns a report to New. These actions retain the report. Opening a report does not mark it read automatically. Private owner notes and read state have explicit controls.
Export loaded reports previews Markdown or JSON for manual download and upload to Codex. It states how many matching reports are loaded; use Load more if needed. Images and private notes are excluded by default; saved owner notes require a separate choice. Downloads are outside Driver OS retention. Nothing is sent to Codex or an email provider automatically.
Owner invitation cards
When card invitations are enabled, eligible owners can open Owner → Accounts, review the exact batch count and confirm generation. New codes appear once. Print two-up cards opens the browser print dialog with two half-page cards on each Letter sheet; the last sheet can have one blank half. Keep printed copies private. Hiding codes, leaving Owner or reloading removes the printable codes. A lost generation response must be checked as the same request before creating another batch.
Card rows identify the claimed account and whether registration is complete. Registration delivery status distinguishes an email accepted by the provider from its confirmed delivery. Refreshing this status makes no invitation or email request.
Reviewed receipt recovery
Eligible owners can open Owner → Email review → Prepare receipt recovery for an explicitly enabled receipt. This workflow is unavailable to ordinary accounts and Demo. Recovery stays off until the operator enables the reviewed receipt.
Preparing a plan needs your consent and a click. Review its source verification, proposed race and raw-lap counts, expiry and exact action before deciding. Preparation does not save recovered results. Confirmation is a separate step: type the displayed plan ID and digest, give fresh consent and press Confirm reviewed recovery. Source placing, scores and raw laps are preserved; no kart or session stage is inferred.
An expired or superseded initial plan cannot start recovery. The app distinguishes saved canonical results from pending anonymous field completion and pending analysis. If it offers a recheck, approve only that same plan explicitly; opening the page or waiting never retries or replays recovery. An uncertain outcome needs review before preparing a replacement. Reloading or leaving the page discards the in-memory review, so do not assume an unresolved operation never started.
Reviewed historical matching
Owners can open Owner → Email review → Historical private matching to preview a reviewed source bundle. The preview reports private observation counts and sources without a recorded visit. It does not save matches. Download review results for the separate operator approval step; the download excludes original emails and opponent names.
Apply approved matching requires exact server approval for each source. Processing stops at the first conflict; earlier confirmed results remain saved. These tentative observations do not establish a person's identity, merge different visits, create Community connections or change sharing preferences. Canonical sessions, laps, exclusions and settings remain unchanged.
Private race-video metadata
Race-video review is an owner pilot inside Sessions. Video files, thumbnails, local filenames and device paths stay on the device. Explicit Save stores only the private review metadata described in Review a session. It is not shared with Community or sent to Coach. Reselect local footage when reopening. Deleting the owning account or race removes its review metadata.
Previous interface referencePreserved guidance · 2026-09-28
Your Driver OS account
The /driver experience uses your authenticated account's results. Driver name, home K1, confirmed notes, private plans and goals follow the account after saving. Temporary browsing and the floating Coach conversation remain separate. Changing your home venue never moves or relabels sessions.
Open the avatar menu for Profile, Settings, Help and Sign out. Profile is a full-width page for driver name and home K1. Your permanent username is shown as text. Completed setup is not repeated; an old setup link returns to Profile. Help opens in a new tab.
Settings → Privacy & account shows your verified sign-in details, age range and recorded notices inside Driver OS. Optional sensor collection and native source backup remain separate consent choices. A recorded cloud-storage choice is not proof that a device can upload; the backend checks current eligibility for each upload. Withdrawal opens a confirmation explaining its scope; cleanup may remain pending, and a retry is available when appropriate. Deactivated drivers can reach their own privacy and cleanup status from account recovery without loading racing history. Whole-account export or deletion remains a support request, not a self-service delete button.
Save failures and conflicts stay visible. Reload saved data (discard unsaved edits) replaces unsaved changes with the saved account state. Refresh uses a neutral loading shell while verifying the account. No private cached results appear before that check, and a denied access check clears the private view.
Community · Coming soon enables no live directory, friends, statistics sharing or messaging. The site owner's separate Owner workspace uses server authorization; a displayed name or email never grants access. Opening Owner does not modify race or kart history.
Other supported account experiences
The sections below document the earlier web interface and the native companion where those features remain available. Their layout, setup and browser-preference controls are not part of the new /driver Settings page; use the native Profile and Settings directions above for that experience.
Use a verified email to sign in. Your profile, imported results, manual journal context, saved plans and supported saved analyses follow the authenticated account.
The native app and browser keep separate sign-in sessions. Opening the browser from the native app does not copy the phone's refresh credential. Sign out retains its existing account-wide behavior: other sessions can require sign-in when they reconnect. Do not use sign-out to troubleshoot an offline recording; preserve its local evidence first.
Demo Tester accounts
The persistent Demo data indicator means driving records, vehicle examples, source summaries and saved coaching are fictional. Your sign-in, username and profile remain genuine. Demo Testers have no functioning inbound results address, raw telemetry upload, analytical sync or paid/live AI. Connections and Discover show simulated states, and synthetic sensor summaries never become accepted evidence.
The owner can reset the demo scenario while preserving sign-in, or reset onboarding and the scenario so you can repeat setup. An onboarding reset clears the driver name and home location; it preserves the verified email, username and legal acknowledgements. A reset also invalidates older tabs' saved work so they cannot restore the previous scenario. Reconnect and refresh if a reset occurred while you were away.
Deactivation preserves authentication but blocks access to the private demo. There is no casual Demo-to-Real switch. Conversion requires removing and verifying deletion of every synthetic record before real capabilities can be enabled.
Sensor storage boundaries
- Sensor Logger files are cached in the importing browser and retained in private account storage until that recording is deleted.
- Older native raw iPhone and Watch files stay in protected local application storage, are excluded from device backup, and survive sign-out until their exact cloud receipt is verified and receipt-first cleanup removes that device copy.
- The native cloud flags are false in the checked-in build. Only the explicitly signed Owner Internal archive may override private cloud delivery; analytical accepted-slice sync remains off.
- When private cloud delivery is enabled with separate consent, a private cloud copy can be retained for analysis and research even if its evidence is rejected or ambiguous. Delivery receipt, race relationship and quality remain separate facts.
Expanded internal recordings remain in private local storage. New eligible recordings can use expanded private cloud delivery when it is separately enabled for both your account and native build. Older full recordings need explicit authorization tied to the exact source and current consent; enabling future delivery does not authorize all retained history. Full iPhone copies remain retained after verified cloud recording; cloud deletion does not delete that local copy. Watch-to-phone transfer requires the same authorized account and a verified phone receipt. Review, export and exact local deletion are available in Advanced → Recording information. Signing out does not delete retained local recordings. These recordings are not accepted analytical data.
Deletion and consent are distinct
Deleting a local native file removes that device copy. Deleting an uploaded native record is a separate cloud action. While cloud deletion is pending, Driver OS hides that source from analysis but does not claim that retained database or storage objects are gone; use the available retry control or contact support if cleanup cannot finish.
Deleting one cloud recording targets that exact displayed source; a paired badge or race candidate never expands the deletion scope. Withdrawing private cloud delivery consent stops new source uploads and deletes or hides all uploaded complete native sources and their cloud metadata, while accepted slices remain unchanged. Withdrawing the underlying Sensor Data consent stops all native sensor processing and deletes or hides accepted artifacts, projections and complete native-source uploads. Neither withdrawal deletes Sensor Logger recordings, and whole-account deletion also requires separate storage cleanup.
Age boundaries
Self-service accounts are for people 13 or older. Teen Sensor Logger use is limited to motion-only files after the required attestation; a file classified as location or heart-rate is rejected as a whole. Native capture and sync are not offered as a teen workflow in the current internal build.
Saved page layouts
Home, Sessions, Progress and Coach layouts are saved separately to your authenticated account after you choose Save layout. They survive sign-out, browser restarts and signing in on another device. These preferences contain only approved section names, their order and visibility, plus update and revision metadata. They contain no race evidence, competitor names, AI output or behavioral click history. Signing out clears the layout from app memory; deleting the account also removes its saved page preferences. Reset each page with Reset to default, then Save layout.
Saved Race Day Review coaching
Where enabled for the owner, Race Day Review saves the validated analysis, its cited source relationships, model and version details, and saved time to that account. A prior answer remains marked outdated when evidence changes. Deleting a contributing source or the account removes its dependent saved analysis; operational usage metadata follows the separate private usage retention policy. Provider response storage is requested off, but provider security and abuse controls can still apply.
Account access
The owner can deactivate app access for Demo and Real accounts. Your sign-in, profile and retained records are preserved; access removal is not account deletion. New protected requests are denied after deactivation. Reconnect or refresh to see the current access status. Content already viewed, cached or downloaded cannot be recalled. Real access can be restored by the owner without changing the account type or granting new AI or native permissions.
Setup choices and recovery
Profile → Your driving choices reopens driving interests; Optional setup contains sensor and AI interests. Continue saves setup progress to your account. Unfinished choices also survive leaving and returning in this browser. When revisiting setup, Close setup returns to Profile and keeps those choices here without changing your saved profile. Your home city is used for suggestions without requesting a street address. Demo data-only resets preserve completed choices; onboarding resets repeat setup while keeping the existing username and legal requirements.
Local experience and review preferences
History filters, the simple-navigation preference, achievement acknowledgement and reviewed timing cues stay with this account in the current browser. They are presentation preferences, not changes to results, achievements, Event context or saved coaching actions. They do not sync to another device. Clearing browser storage can restore the reminders; a signed-in device starts its own seven-day achievement celebration when it first displays that achievement.
The separate Save layout controls remain account-synced. Home, Sessions and Progress expose them in Saved layout & optional widgets panels using your existing optional widgets and saved choices. The wide review’s required history, evidence and retained focus stay available. A local reminder acknowledgement does not save a page layout.
Home track and starting view
The optional home track and starting view are saved for this account in this browser. They are separate from your home city, temporary venue browsing and account-synced page layouts. Remove browser preference restores the existing opening behavior without changing your current view or driving history. Choose Home track or All venues for new tabs; existing defaults stay unchanged until you choose. Reload retains the current tab’s browsing context where browser storage is available. Preferences do not transfer between Dev and Production or to another browser or device.
Finding Profile settings
Profile groups settings into Identity & driver profile, App preferences, Connections & result emails, and Privacy & account data. App preferences contains navigation, driving interests, the tour, and the optional home-track starting view. Home city and home track remain separate choices. Saving a browser preference does not change the history you are currently browsing.