System Cookie Telemetry Matrix
LIFECYCLE_MAP & AUTHORIZATION_SCHEMA
This document classifies every token injected into your local client storage by Subtle Scale platform surfaces. We enforce a zero-tolerance policy against marketing trackers, behavioral profiling engines, or third-party advertising scripts. All tokens listed below are functionally necessary or strictly opt-in.
| Token Registry ID | Target Scope | Classification | Lifecycle Bounds | Purpose |
|---|---|---|---|---|
| __SS_SYS_STATE | Operational | ESSENTIAL | Session Exit | Tracks wizard progress state across /discover page loads. |
| __SS_THEME_MODE | Presentation | ESSENTIAL | 365 Days | Retains local dark/light UI token render preferences. |
| __SS_AUTH_TUNNEL | Security | ESSENTIAL | 1 Hour | Validates the integrity of the dynamic FIPS-compliant routing tunnel. |
| __SS_ANALYTICS_TR | Telemetry | OPT-IN | 30 Days | Gathers aggregated, low-impact server latency, and routing failures. |
Essential System Cookies
Essential cookies are strictly necessary for the platform to function. They cannot be deactivated. These tokens manage session state across the /discover wizard, enforce FIPS-compliant routing tunnel integrity, and persist your UI rendering preferences.
No personal data is extracted from essential tokens. All values are cryptographically salted and expire within their stated lifecycle bounds.
Analytic Telemetry Cookies (Opt-in)
The __SS_ANALYTICS_TR token is injected only when you explicitly authorize analytic telemetry via the System Cookie Authorization HUD. It captures aggregated, non-personally-identifiable signals: server response latency bands, routing failure classifications, and page load distribution curves.
This token is never shared with third parties, never used for advertising profiling, and is wiped on the 30-day cycle boundary. You may revoke authorization at any time.
Manage Your Authorization State
Use the System Cookie Authorization HUD to review and modify your current telemetry settings. Changes take effect instantly — deactivated tokens are flushed from client storage on confirmation.
For full data handling terms and retention policy details, see the Privacy Policy & Data Sovereign Protocol.