Privacy at qeti
Current practices · September 27, 2026
What qeti stores
qeti stores your account details, workspace membership, application configuration, test journeys, release results, and audit history. Browser runs can produce screenshots, videos, page snapshots, and sanitized console and network metadata.
How the service uses your data
This data is used to authenticate your team, run the tests you request, show evidence, and deliver results to integrations you enable. Cloudflare provides hosting, execution, and private evidence storage. Supabase provides authentication and database services; older evidence may remain in private Supabase storage until it expires.
Test credentials and AI
Dedicated test credentials are encrypted at rest. Login takes place before recording. Configured AI features can receive product context and a redacted page snapshot; deterministic journeys do not require an AI provider. Use synthetic data and dedicated staging accounts.
Cookies and browser storage
Authentication cookies keep you signed in. A separate cookie enables the recorded demo. Browser storage remembers your language, the staging URL entered before sign-up, and a safe return destination during sign-in. The current application does not include advertising trackers.
Evidence retention and access
Browser evidence is retained for 7 days. Release verdicts and audit history remain in the workspace. Evidence access is restricted to the workspace; the public demo uses synthetic data. Workspace administrators manage access and configuration.