Legal review required
Cookie and Telemetry Policy
Draft description of necessary storage and optional telemetry controls.
Not approved or effective. This text is a versioned product draft for owner and qualified-attorney review. It must not be treated as legal advice, a launch approval, or a final statement of Traderbase obligations.
- Version
- Version: draft-2026-07-14-v0.1
- Last revised
- Last revised: 2026-07-14
Current categories
Necessary storage supports authentication, security, checkout continuity, app state, and the saved privacy choice. It remains available because disabling it in the app would break requested functions.
Analytics and diagnostics cover the optional Vercel Analytics and Speed Insights integrations. Marketing technology is a separate optional category, but no marketing script or replay tool is currently installed.
Default behavior and consent
The current browser-choice schema is 2026-07-14.phase-e-draft-v1. Optional categories default to off. Vercel telemetry components are not mounted until analytics is affirmatively allowed. Reject optional is available beside the allow action without preselected optional choices.
A changed or invalid version fails closed and requires a fresh choice. Anonymous visitors can use public pages while optional categories remain off.
Changing or withdrawing a choice
Use Cookie preferences in the public footer or account settings. Saving analytics off unmounts telemetry and reloads the page if needed so the optional integration is not left active. The new deny choice is timestamped in local storage.
Clearing browser storage removes the saved choice and causes the banner to return. Marketing email consent is managed separately in account settings.
Global Privacy Control
When the browser exposes an active Global Privacy Control signal, Traderbase conservatively records optional analytics and marketing as off and prevents them from being enabled while the signal remains active.
The legal effect and regional behavior of GPC still require counsel review; the technical default is intentionally privacy protective.
Telemetry minimization
The Vercel integration accepts only explicit public routes. Query strings and fragments are removed, blog and documentation slugs are collapsed, and auth, account, support, admin, API, referral, ticker, screener, and workspace routes are rejected for page analytics and performance telemetry.
Custom events use a strict two-event taxonomy with categorical marketing locations only and no Vercel user identification or free text. Vercel console activation, retention, DPA, region, sample rate, and taxonomy approval remain manual launch gates. No session replay or third-party marketing pixel is approved.
Unresolved before approval
- Legal entity name and service address
- Supported jurisdictions and governing law
- Approved contact and privacy-request channels
- Consent legal basis and regional behavior
- Approved Vercel retention, region, DPA, and sampling settings
- Final inventory of browser storage and cookie durations
The official legal and privacy contact channel is not yet approved. Review the draft Trading Disclaimer and Privacy Policy for related open items.