Vorda legal
Cookie and Tracking Technologies Notice
This draft must be reconciled against observed production website and application behaviour. A package or configured vendor does not prove that a technology is active for every visitor.
1. Technology categories
Vorda does not currently intend to use third-party advertising cookies or cross-site behavioural advertising. Vendor settings must be reverified before publication.
- Strictly necessary: identity sessions, security, anti-abuse, consent state, and requested features.
- Preferences: locale, theme, and other remembered choices.
- Analytics and diagnostics: pseudonymous measurement of usage, reliability, attribution, and errors, optional where consent is required.
2. Inventory requiring verification
| Technology | Purpose | Status or duration |
|---|---|---|
| Vorda consent value | Store analytics choice and region policy | Name and duration TBD |
| Vorda visitor/session identifiers | First-party pseudonymous journey and session | Visitor record 13 months; browser keys TBD |
| Clerk cookies/storage | Authentication, sessions, verification, security | Clerk-controlled; production inventory TBD |
| Cloudflare cookies | Security, routing, or challenges when set | Deployment inventory TBD |
| PostHog storage | Analytics and diagnostics when enabled | Keys and duration TBD |
| Google Analytics cookies | Website measurement when enabled | Property, names, and duration TBD |
| Amplitude storage | Product analytics when enabled | Keys and duration TBD |
| Locale or UI preference | Remember interface choices | Key and duration TBD |
3. Consent and regional behaviour
Geolocation signatures, Global Privacy Control, withdrawal propagation, and cross-subdomain behaviour must be tested before this Notice becomes effective.
- Optional analytics remains off until opt-in where consent is required.
- Where consent is not required, an accessible opt-out should remain available.
- Unknown regions fail closed and require consent.
4. First-party analytics boundary
Vorda validates and minimises events through a first-party boundary before configured delivery to PostHog, Google Analytics, or Amplitude. First-party routing does not turn optional analytics into necessary processing. Events are designed to exclude raw credentials, balances, positions, symbols, quantities, order payloads, and arbitrary request bodies.
5. Controls
Users can change optional analytics preferences through Vorda's privacy control where available. Browser settings can block or delete site data, but blocking necessary identity or security technologies may prevent sign-in or core features.
6. Global Privacy Control and contact
[PRODUCTION GLOBAL PRIVACY CONTROL BEHAVIOUR MUST BE VERIFIED.] Vorda should honour GPC where applicable to a legal opt-out right. Questions or requests: [PRIVACY EMAIL].