Your data, in your own database.
An agency’s client list, rates and margins are the business. Verbial is built so that losing them, leaking them, or getting stuck without them is not on the table.
Every Verbial workspace runs in its own Postgres database: no shared tables, no tenant column to get wrong. Databases are snapshotted daily with retention and dumped to object storage on a schedule; every action on the workspace is audit-logged; compensation and margin data is visible to admins only, on every surface; you can export everything as JSON at any time; and deleting a workspace keeps the data for a grace period first.
What we do
Database per customer
Workspaces are isolated at the database level. Requests are pinned to their workspace by hostname before any query runs; a query with no workspace context is refused.
Backups you can see
Daily snapshots with retention plus logical dumps to object storage. Backup health is shown on your account page; a stale heartbeat is an alert, not a surprise.
Export and delete
Full JSON export on demand. Deletion is scheduled with a grace period and can be cancelled; nothing is removed the moment you click.
Role-gated money
Hours for members and managers; budgets and revenue for account leads; cost, salary and margin for admins only. Enforced in every page, API and integration.
Sign-in
Google sign-in only, bound to the Google account id rather than the email, so a changed address does not lose access and a re-used address cannot hijack one. Admin impersonation is audited and cannot perform irreversible actions.
Secrets
Database credentials are encrypted at rest and never logged or exported. Payment details live with Stripe; Verbial stores none. Contact consent is recorded on every imported or captured contact.
Public surfaces
Rate-limited, token-scoped share links for proposals, reports and the client portal. Content-security policy and security headers on every response. Webhooks verify signatures and fail closed.
Audit trail
Every write to settings, roles, billing, contracts and imports is recorded with who did it and when, and is visible to admins in the audit log.
AI access with your permissions
Claude connects with a personal token that carries the person’s own identity; it sees exactly what they see and never cost, salary or margin unless they are an admin.
Frequently asked questions
- Where is my data stored?
- In a dedicated Postgres database provisioned for your workspace alone, hosted on Neon in the region chosen at provisioning. No other customer’s data is in it.
- How are backups done?
- Daily point-in-time snapshots of your database with retention, plus periodic logical dumps to object storage. Restores are operator-run, always preceded by a fresh snapshot, and you are emailed when one happens.
- Can I get all my data out?
- Yes. Settings → Account → Data produces a complete JSON export of your workspace, with credentials redacted, delivered by a single-use download link.
- What happens if I cancel?
- The workspace becomes read-only at the end of the paid period. If you delete it, the database is kept for a grace period (30 days by default) before it is removed, and you can cancel the deletion during that time.
- Who can see salaries and margins?
- Only workspace admins, everywhere: pages, APIs, exports and the Claude integration all apply the same rule. Team members and managers see hours only.
Questions for your security review?
We answer questionnaires and walk through the architecture with your team.