Security, substantiated.
Three claims. Each one backed by a mechanism you can ask us about — not a badge.
Encrypted in transit
Every connection to Darbase is served over TLS, terminated at the edge, with HSTS enabled.
Per-tenant isolation
Every product table carries an indexed tenant_id. Scope is resolved from the authenticated request context on every query — never from a client-supplied parameter — and enforced by a dedicated guard.
Every action audited
Mutating admin actions are recorded in a cross-tenant, metadata-preserving audit log with multiple filters, so "who changed what, when" is always answerable.
Access control
Every route checks role and permission before it runs. Three separate JWT audiences — platform admin, broker, public token — are rejected symmetrically outside their own surface.
Support sign-in you control
When you ask us to look at something, a support engineer can open a session signed in as your account owner — never as one of your agents. It lasts 15 minutes with no renewal; the link that starts it works once and expires after 60 seconds; and an undismissable banner sits across every screen for as long as it lasts. Both the grant and the sign-in are written to the audit log. Any account can switch support sign-in off entirely, from Settings → Support access.
Responsible disclosure
Found a security issue? Email hello@darbase.com — we read every report personally.
What we do not claim yet
A short honest list outperforms a long vague one:
- · No SOC 2 report yet.
- · No ISO 27001 certification yet.
- · No published SLA yet.
- · No signed Data Processing Agreement yet — see our DPA page.