Security

Customers put their proprietary knowledge into Dextome. The trust posture: it's just Postgres, the managed service is locked down, and Enterprise customers can run it in their own cloud.

Tenant isolation

Every customer-data row carries org_id and is scoped at the access layer. Two-org isolation tests run in CI on every change and gate every release. API keys resolve to exactly one project — they never accept org/project ids from the client.

Authentication

People sign in through Supabase Auth: email + password with required email confirmation and rate-limited sign-up. Programmatic access uses API keys that are stored only as SHA-256 hashes, shown once, and revocable.

Authorization (RBAC)

Org roles: owner / admin / developer / viewer. Project-level RBAC is on the Team+ roadmap. Role checks are unit-tested per action with a central allow-table.

Encryption

TLS everywhere with HSTS. Managed Postgres + object storage encryption at rest (provider-managed keys). BYO provider keys encrypted with AES-256-GCM using DEXTOME_ENC_KEY; per-record nonces; never returned via API.

Data handling

Document content is customer data. Application logs are designed to record IDs, sizes and timings, not document text. Deleting a document removes its text and vectors immediately; original files are removed when your account is deleted, or sooner on request. We do not use customer data to train models.

Application security

Zod validation at every boundary. Parameterized SQL only (Drizzle). The metadata filter compiler refuses non-allowlisted field names and never inlines user values. URL ingestion blocks private-network addresses and caps fetches at 10s / 5MB. Every API key is rate-limited.

Compliance roadmap

Today: tenant isolation tested on every release, encryption in transit and at rest, role-based access, and deletion on request. Not yet: audit logs, SOC 2, HIPAA, or SSO/SAML — we will say so here when they exist. See our Privacy Policy for exactly how data is handled.

Disclosures and reports: hello@dextome.com. Responsible disclosure: security@dextome.com.