Privacy
Minimal telemetry. No advertising tracking.
The public evaluation experience collects only the product telemetry needed to understand usage, friction, and evaluation progress. Analytics is never Truth Engine evidence.
What we do not use
No advertising surveillance layer.
Access protection
Security traffic is separate from product telemetry.
The public Playground uses Cloudflare at the edge, Turnstile for access protection, and a short-lived first-party session to enter the evaluation environment.
It is used to reduce automated abuse before traffic reaches the private Playground service.
A temporary first-party access session is used to keep an authorized evaluator inside the Playground.
Edge protection, access checks, and rate controls do not determine engine truth or proof.
Data boundary
Evaluation data only.
Credentials are not product telemetry.
The public evaluation environment is not designed to receive those categories of data.
It can describe product use, but it cannot create or modify Truth Engine authority, evidence, proof, or occurrence history.
Analytics never determines SATISFIED, NOT_SATISFIED, UNKNOWN, retry authority, provider occurrence, release lineage, or Runtime history.
Non-authoritative telemetry
Supabase does not control the engine.
Supabase is used only for product and external-validation telemetry. It is outside the authoritative truth path.
None of these may be written or controlled by product analytics.