What we can prove, what we inherit, and what we don't have yet

Workspace data is stored in Supabase (PostgreSQL), hosted in the EU.

Covers: All workspace, workflow, and scoring data · Source: Production project configuration (Supabase EU region) · Verified 2026-07-12

The application runs on Cloudflare Workers — a global edge network. Compute is global; storage stays in the EU database. We do not claim EU-only processing.

Covers: Request handling and rendering · Source: Deployment configuration (Cloudflare Workers via OpenNext) · Verified 2026-07-12

Traffic is encrypted in transit (TLS); data is encrypted at rest by the storage providers.

Covers: Transport and storage encryption · Source: supabase.com · Verified 2026-07-12

This site sets only essential cookies (session and authentication). There are no third-party trackers, analytics pixels, or ad scripts — which is why there is no cookie banner.

Covers: everform.io marketing + app surfaces · Source: Site source audit, 2026-07-12 (first-party telemetry only) · Verified 2026-07-12

Eve's intelligence — interviews, drafting, explanations, estimates — runs on OpenAI models (GPT-5.6 Sol).

Covers: Eve chat, workflow drafting, model-derived estimates · Source: Production provider configuration · Verified 2026-07-12

Everform does not use your workspace content to train models. The data-handling terms of our model-provider integration are being pinned with counsel; until they appear here with a source, provider-side handling is stated as provider + purpose only.

Covers: Everform's own use of workspace content · Source: Everform data-handling commitment (this ledger) · Verified 2026-07-12

Structural workflow scoring makes zero model calls — a deterministic 12-criterion engine. The same input always produces the same score. No workflow content leaves the platform for scoring.

Covers: All structural scores shown in the product · Source: src/lib/scoring/structural.ts (frozen module, 777 lines) · Verified 2026-07-12

Every table carrying workspace data enforces row-level security scoped to the organization — isolation is a database policy, not an application convention.

Covers: All multi-tenant data access · Source: Supabase RLS policies (migrations, org-scoped) · Verified 2026-07-12

Sign-in is handled by Supabase Auth (Google, GitHub, or email magic link). We never see or store passwords.

Covers: Authentication · Source: supabase.com · Verified 2026-07-12

Payments are processed by Stripe. Card details never touch our servers.

Covers: Billing · Source: stripe.com · Verified 2026-07-12

Database backups run automatically on the Supabase platform.

Covers: Workspace data · Source: supabase.com · Verified 2026-07-12

Data export and account deletion are fulfilled on request — reply to any Everform email (sign-in emails work) or use your Stripe receipt contact. Fulfilment is currently manual and we say so.

Covers: Data-subject rights · Source: Privacy policy, exercisable-channels section · Verified 2026-07-12

A dedicated security-vulnerability reporting channel with a published safe-harbor policy.

Covers: Security disclosures · Source: This ledger — listed as planned until the mailbox passes a live send/receive test · Verified 2026-07-12

SOC 2 certification. Our providers (Supabase, Cloudflare, Stripe) hold their own certifications — those cover their layers, not Everform.

Covers: Everform the company · Source: supabase.com · Verified 2026-07-12

An independent penetration test.

Covers: Everform application · Source: This ledger · Verified 2026-07-12

A contractual uptime SLA or a bug-bounty program.

Covers: Service terms · Source: This ledger · Verified 2026-07-12