TRUE LANES · LEGAL
Cookie Policy
Cookies, browser preferences and mobile storage—with optional tracking kept separate.
Development draft · Updated September 28, 2026. These documents describe the local preview. The legal operator, contact details and launch terms must be confirmed before public registration opens.
Cookies and similar storage
Cookies are small values stored by a browser. Local storage and mobile databases can also remember information on a device. This policy covers these technologies in the current True Lanes preview.
What this preview uses
The website does not currently set application authentication, analytics or advertising cookies. It stores the color theme you choose under true-lanes-theme in local storage until you clear it. This is a display preference, not an advertising identifier.
The mobile app uses SQLite to keep account-separated room history, synchronization cursors and messages waiting to send. These support the offline chat you use. Disconnecting clears that account’s chat data. On Expo web, the same offline feature uses browser-backed storage.
Policy acknowledgements are recorded by the local API with a policy version and server time. They are not an advertising cookie or consent to optional tracking.
Optional cookies and consent
No optional analytics or advertising technology is enabled in this preview. There is nothing optional to accept now. Agreement to account terms and acknowledgement of this policy do not grant permission to add optional tracking later.
Before any optional technology is enabled, a separate choice must explain its purpose and provider. Where consent is required, optional technology must remain off until you choose it; rejection must be as easy as acceptance, and you must be able to change that choice.
Manage storage
You can clear website data in your browser settings to remove the theme preference and browser-backed offline cache. You can disconnect in the mobile app to clear local chat. Clearing an offline cache removes unsent messages; it does not delete records already sent to the API.
This inventory must be reviewed when authentication, analytics, advertising or third-party services are added. The operator’s confirmed privacy contact will appear in the Privacy Policy before public registration opens.
Version 2026-09-28-draft-v1
Back to agreement