Your evidence stays attached to your workspace.
QueueProof retrieves the minimum source context needed to answer a work question, keeps the supporting receipt, and makes missing proof visible.
What QueueProof stores
QueueProof stores your account identity, workspace membership, connector state, source metadata, grounded answer receipts, priority packets, proposed changes, approval records, and product audit events. A shared public demo is kept separate from signed-in personal workspaces.
The browser also keeps a short, workspace-namespaced list of recent question text and provider labels on that device. It is cleared for that workspace when you sign out and can be removed one row at a time from History.
Credentials and connected sources
Your HydraDB API key is encrypted at rest and is never returned to the browser after configuration. Provider credentials used to establish a HydraDB connector are sent to HydraDB for that connection flow and are not stored by QueueProof.
QueueProof only retrieves from connectors that have passed its resource-scope and data-verification checks.
ChatGPT, Codex, Claude, and MCP
When you connect an AI client, QueueProof verifies the bearer token, audience, scopes, expiry, and your workspace before a tool runs. Read access is the default. Proposed changes and source sync require separate scopes, and external provider execution still requires an owner approval in QueueProof.
Service providers
QueueProof uses Supabase for passwordless account authentication and OAuth authorization, HydraDB for connector indexing and retrieval, Turso/libSQL for durable application records, and Vercel for application hosting. Data sent to an AI client is also governed by that client provider's terms and privacy controls.
Your choices
You choose which sources to connect and which MCP scopes to grant. You can revoke QueueProof-issued MCP tokens from Connect AI.
QueueProof does not claim an automatic deletion window in this release. Workspace records remain until an implemented product flow deletes them or the verified publisher processes a supported request. Copies held by connected providers and AI clients follow those providers' policies. For account-data access, correction, or deletion requests, use the QueueProof support page; ownership is verified before action.