No compliance badges to wave around yet — we're early, and said so on our homepage. This page is the technical detail instead: exactly how isolation, access, and backups work today.
Every company that signs up gets its own PostgreSQL database — not a row in a shared table filtered by a tenant ID. A bug in query logic in one workspace cannot leak rows from another, because there is no shared table for it to leak from.
Documents, logos, and attachments are stored under a path prefixed with your workspace slug and served through an authenticated view — not a raw static file alias. Sensitive files (employee documents, HR attachments) require login; only a small public set (logos, payment QR codes) is served without one.
Plain HTTP requests are redirected to HTTPS site-wide, session and CSRF cookies are marked secure-only, and HSTS is enabled so browsers remember to use HTTPS on repeat visits.
Every module and admin action is gated by role — HR, accounting, and system settings are separately permissioned, not all-or-nothing. Staff changes to a plan or a workspace are written to an audit log.
From your workspace: Administration → Download workspace backup. It's a self-service action, available whenever you want it — not something you have to ask us for.
A full PostgreSQL database dump plus every file your workspace has uploaded — not a partial export.
The same backup can be restored back into your workspace — useful before a risky change, not only for disaster recovery.
The Customized plan includes full source code delivery and an on-premise option, if you'd rather not depend on us hosting it at all.
If any of these are a hard requirement for you today, talk to us before signing up — we'd rather tell you now than after.
Email sales@toss-erp.com — we'll answer directly, not with a sales deck.