Security, specifically
Security pages are usually wallpaper. This one makes specific claims about how Vedential actually works — the same architecture we would walk your security team through on a call.
One isolated workspace per organisation
Every record in the platform carries your organisation's identity, and the database enforces row-level security on every read: a query from your workspace physically cannot return another organisation's rows. This isn't an application-layer filter — it's enforced by the database itself.
Writes are enforced twice
Browsers get read-only database access. Every create, update and delete goes through our server, where each request independently re-verifies who you are, which organisation you belong to, and whether your role allows that specific action on that specific project — before anything is written. Client-side checks are mirrors for usability; the server is the authority.
Role-based access, least privilege
Admins, project managers, contributors and viewers, plus per-project membership and granular capability flags (who may approve changes, manage budgets, manage risks). Contributors and viewers see only the projects they are assigned to. Organisation owners can never be locked out of their own workspace.
An audit trail that survives
Every mutation writes an audit entry — who, what, when. Audit attribution is preserved even after a user account is deleted, and approval events on change requests are stamped server-side and cannot be supplied by a client.
Backups you can actually restore
Daily automated backups, plus a manual snapshot before any risky operation as standing practice, with documented restore procedures. We practise restores — a backup that has never been restored is a hope, not a plan.
Your data is never hostage
Full workbook export (Excel/CSV, every register) is available on every plan and in every account state, including lapsed trials. Data-safety features are never used as a retention lever.
Boring, proven infrastructure
The platform runs on tier-one cloud infrastructure with data stored in the Sydney, Australia region. We deliberately keep the stack small: fewer moving parts, fewer places to make mistakes. A full sub-processor list is available to customers on request.
On the enterprise roadmap
Labelled honestly as roadmap, not shipped: SAML single sign-on, SCIM directory sync, audit-log export with retention controls, and a dedicated single-tenant instance in your preferred region for organisations that require hard infrastructure isolation. Talk to us if one of these gates your evaluation — enterprise pilots shape the order we build them in.
Security questions, disclosure reports or questionnaire requests: sales@vedential.com.