Security & trust
Planning data is sensitive: who works on what, what people cost, which projects are in trouble. ResourcePlan is built so that trust is a property the database enforces, not a promise the interface makes.
This page describes how the product is built today. It is an honest engineering overview, not a compliance certificate — where an independent attestation is in progress, we say so.
Tenant isolation, enforced and tested
Every customer’s data lives behind row-level security in the database, so isolation does not depend on the application getting every check right. A test suite rebuilds the whole schema from scratch on every change and asserts that one tenant cannot read another’s data before anything ships.
Sensitive data, scoped by role
What a person costs is readable by admins and executives only — never browsable by the wider team, and never leaked through a derived figure. A project lead controls who may edit their project.
Tamper-evident records
Decisions, approvals and delivery evidence, once taken, can be added to but not silently rewritten. The record of what was decided, and what it rested on, stays as it was.
Break-glass support access
Nobody at ResourcePlan has standing access to your data. Support access is granted for a bounded time, with a stated reason, and the grant itself is the audit record — visible to you.
Your data is yours
Export your organisation’s complete data on request, and have it erased when you leave — the controls a data-processing agreement expects.
Authentication
Email-and-password, Google and Apple sign-in today, with single sign-on (SSO) and enforced multi-factor authentication for Enterprise. Credentials are handled by the identity provider; the application never stores a password.
The controls a SOC 2 audit examines — isolation, access control, audit logging, data lifecycle — are in place and documented. An independent Type II report requires an observation window with an auditor; if you need one to buy, tell us and we will share our current status and timeline.