Security & Trust
How OriginVox isolates workspaces, keeps a human in the loop, and refuses to fabricate — and what isn't in place yet.
Tenant isolation by default
OriginVox is multi-tenant with Postgres Row-Level Security on every tenant table. Each row is scoped to a workspace, and no workspace can read or write another's data without an explicit policy. Isolation is enforced in the database, not just the application.
A human always approves
Content moves through draft → in review → approved → scheduled. Auto-publish is off by default, and nothing reaches a published state without a person approving it. You are always in the loop.
No fabricated claims
A built-in claim-checker blocks unverifiable metrics and statistics before content can be approved. The product is designed for founders who cannot afford to overclaim — including in regulated domains.
Least-privilege administration
Platform administration is deny-by-default and authorized on the server by identity — never a client-side flag or an email-domain guess. Every privileged action (suspensions, invitation revokes, entitlement changes) is written to an immutable audit log.
Careful secret handling
Service credentials never reach the browser bundle. Invitation links are stored hashed and are never returned by the API. Authentication is handled by Supabase Auth — the app never stores your password.
Your data stays yours
Your workspace content and leads belong to you. Nothing is sold. Analytics show only real, imported metrics — with no data yet, screens stay honestly empty rather than inventing numbers.
What isn't in place yet
- This is a private beta, not a certified production service. There is no SOC 2 / ISO certification yet and no production SLA.
- Real social-account OAuth and publishing are not enabled yet — scheduling produces an export, and nothing posts on your behalf.
- Self-serve billing is not live; plan changes go through our team.
Security questions or an enterprise review?
We're happy to walk a security or compliance team through the details.