Where your data lives, who can see it, and how you keep it.
What a business manager or IT committee asks before signing, answered from the controls we run. Where we hold no certification, we say so.
Where it runs.
Managed hosting is one server per school in Sydney. Self-hosting is the same software on hardware or cloud you control.
Australia, or your own server
Managed deployments run in Sydney, and your application database stays there. Or run Plugboard on your own infrastructure and choose its external connections yourself.
A server of your own
Each managed school gets its own server, database, disk and backups. No other school’s deployment is on the machine.
Every record belongs to one school
Tenant-aware queries and PostgreSQL row-level security enforce the boundary in the database as well as the application. Self-hosted deployments run with the same restricted application role.
In transit, and for every secret
TLS encrypts traffic in transit. Connector credentials are envelope-encrypted with key rotation and kept out of normal responses and logs. Disk encryption on a self-hosted server is yours to configure.
Nightly, encrypted, kept 90 days
Backups are on by default: every night, encrypted, and kept for 90 days, with restore tooling and a documented restore procedure. On managed hosting, each night’s backup is also copied offsite, to Oceania, best effort.
Hosted and pseudonymised, or local
Cloudflare runs embeddings and typed decisions, and chat uses Anthropic’s Claude, processed by Anthropic in the United States, outside your hosting region. Names, emails, phone numbers and IDs are pseudonymised before every call, and a school can switch AI off. Self-hosted, a local model keeps it on your server. Email, SMS and other connectors are processed by their providers. Where AI runs
Who can see what.
Staff sign in with the identity provider you already run. Students tap cards and parents follow links; neither ever sees the technician console.
Your identity provider, your policy
Staff sign in with Entra, Google, custom OIDC or SAML, tested before you switch it on. Require MFA across the team, and offer or require passkeys. A wipe or an MFA reset asks for fresh verification there and then.
Deprovisioned from your directory
Provision and deprovision technician accounts from your identity provider. When someone leaves the school, you remove them once, in the directory.
Built-in roles, or your own
Start from the built-in roles or write your own, and grant a role on one campus or across the whole school. Every guarded action has its own permission.
Audit row first, command second
Plugboard records covered operations and writes the audit row for a privileged command before sending it. Export records and set retention. Sign-in events and some settings changes are not covered, and the documentation lists which.
Export and erasure, per person
Export or erase one person’s records, and set retention. We are your processor: the data is the school’s, we do not train models on it, and the sub-processor list is published.
Scanned, signed, with an SBOM
Every release image is scanned for vulnerabilities, signed with cosign and published with an SPDX software bill of materials. Your team can verify what it is running.
Vulnerability disclosure.
Report a security issue to security@plugboard.app, and say if you want to encrypt the report and we will send a key. Report issues found on plugboard.app or in your own deployment; customer deployments need the customer’s written permission.
We ask for 90 days before public disclosure, or until a fix has shipped and schools have had a fair chance to apply it, whichever comes first. We credit reporters in the release notes unless they prefer not to be named.
- Acknowledgement
- 2 business days
- Initial assessment and severity
- 5 business days
- Fix or mitigation, critical
- 7 days
- Fix or mitigation, high
- 30 days
- Medium and low
- Next scheduled release
Three commitments in every agreement.
A school should not depend on one supplier to keep running. These commitments are part of every agreement and hold whatever happens to Plugboard.
- Your data exports in full, any time, in a machine-readable format.
- The same software runs self-hosted. If managed hosting ever stopped, your export runs on your own server with the same features.
- On exit, we delete it. We hold your data for the window in your order so you can move it, then delete it, including from backups.
What we don’t claim yet.
No SOC 2 or ISO 27001 certification, no ST4S assessment and no independent penetration test. If any of these is a condition of purchase, tell us and we will say where each one stands.
What we do have is the control inventory above, sourced from the platform and reviewed against the code, and the operational evidence for your deployment on request.
Questions before you sign
Bring your business manager’s or IT committee’s questions to a demo, or send them to hello@plugboard.app.
We reply within one working day.