Trust Center
The technical controls and security posture governing Oakwood Planner — what is in place today, described plainly.
Last updated 25 September 2026.
Access Control
Row-Level Security
Database-enforced isolation across all fourteen business tables. Every rule asks whether the person belongs to the team that owns the row.
Session Management
Automatic termination of inactive sessions, shared across every open tab, with browser-held data cleared on sign-out.
Invitation Security
High-entropy single-use tokens with a strict lifetime. Only owners can create, view or cancel invitations.
Role-Based Access Control
Hub administrators, spoke users and platform administrators, each limited to their own environment and checked by the database on every read and write — never just hidden buttons.
Rapid Removal
A member can leave, or an owner can remove them. Access to that team's records ends on their next request.
Credential Hashing
Passwords are checked and stored as salted hashes by the authentication service. Oakwood Planner's own records never hold a readable password.
Two-Step Sign-In
Users can add an authenticator-app code (TOTP) to their sign-in, and organisation admins can require it for everyone. Once enrolled, the database refuses access to a session that has not completed the second step.
Data Security & Privacy
Private Storage
Team files live in isolated buckets with no public access policy. Reading or changing a file requires membership of the team that owns it.
Zero Tracking
No advertising pixels, no analytics, no session recording, no heatmaps. The only third-party file loaded is the web font.
Client-Side Reports
Word and PDF exports are assembled in your browser from data you have already loaded — never posted to a document service.
No Anonymous Access
Not one rule grants access to a signed-out visitor. Somebody outside your team cannot read a single record, including through the public web address.
Data Portability
Export your full risk register and every response plan to Word or PDF whenever you like. Email us to have records and accounts deleted.
No Data Selling
We don't sell your data, use it to train models, or send it to advertisers. There are no advertising relationships to opt out of.
Continuous Monitoring
Continuous Scanning
Automated scans run against the backend configuration, application behaviour and code dependencies every day. Access rules, exposed data and vulnerable packages are checked without anyone having to ask.
Weekly Deep Scan
A fuller sweep of the whole stack — database policy, third-party packages and application logic — runs on a seven-day cycle, catching what a daily check can miss.
Immediate Remediation
Findings are triaged and fixed as soon as they surface rather than parked in a backlog. A control that stops working is treated as an incident in its own right.
Current Scan Record
Three independent scanners cover the platform, and their latest results carry no open findings. The current record is available on request.
Infrastructure & Operations
Managed Cloud Hosting
The application database is hosted in Europe (Ireland). This describes database residency; it does not imply that every infrastructure provider or support process operates only in Europe.
Daily Backups
The managed provider takes automated daily backups of the database.
Incident Log
Every entry in a live incident is timestamped and attributed to the person who logged it — your reconstruction record afterwards.
Review-Dated Plans
Every playbook carries a last-reviewed date, and the app flags plans that have run past their review point.
Change Timestamps
Records carry created and last-changed timestamps, so the history of an edit is visible rather than assumed.
Error Reporting
If a screen crashes, a short technical report — the error, the page, the browser — goes to the hosting platform so we can fix it. Not a copy of your records.
Security reports and due-diligence questionnaires are answered directly.
info@oakwoodriskgroup.com