Your context. Your control.
Private by default. Source-aware History. Approvals when policy requires it. Advanced integrity underneath.
Private by default
Your project History and Now stay in your workspace. Agents receive only what policy allows.
Sensitive-context controls
Classify and sanitize before anything leaves the private boundary. External research requires validation — and approvals when policy says so.
Source tracking
Important state links back to History & Sources so you can jump to the original conversation — not a floating answer without evidence.
Approvals & model routing
When policy requires a human, Review surfaces it. Private models can be required for non-public synthesis — no silent public fallback.
Advanced integrity
Under the product shell: append-only History, cryptographic receipts, and Merkle chains remain available for teams that need them. We do not claim SOC 2 or regulated certification unless independently obtained.
Cryptographic signing (advanced)
Every verification receipt is signed with Ed25519 via the Web Crypto API. Signing keys are stored exclusively in Cloudflare Secrets — never in source control, environment files, or databases.
Append-only assertions
Assertions cannot be updated or deleted through normal operations. To correct a fact, you retract the old assertion and insert a new one. The original record is preserved for audit. This design ensures a tamper-evident history.
Namespace isolation
All data is scoped to namespaces. Your assertions, artifacts, and memory are accessible only to API keys authorized for your namespace. There is no cross-namespace data leakage.
Encrypted token storage
OAuth tokens for connected integrations (GitHub, etc.) are encrypted at rest using AES-GCM-256 before storage. Encryption keys are managed via Cloudflare Workers secrets.
Transport security
All API traffic is served over TLS via Cloudflare's edge network. API keys are required for every authenticated endpoint. Rate limiting is enforced per-IP at 60 requests per minute per worker.
Infrastructure
- Compute: Cloudflare Workers (edge, no persistent server)
- Database: Supabase Postgres with Row-Level Security enabled
- Object storage: Cloudflare R2
- Secrets: Cloudflare Workers Secrets (no plaintext keys in config)
Reporting vulnerabilities
If you discover a security vulnerability, please report it to support@verifiedstate.ai. Do not open public issues for security bugs. We will acknowledge receipt within 48 hours.