Trust and security

School data stays with the school.

Apps on Quad can be built by anyone, anywhere, but real school data lives in one place only: your school's own environment, in your region. Builders work on a fictional school. Quad reviews code, never data. And nothing touches a real record until your school says yes.

Where things stand

This page describes how Quad is designed. Some parts arrive with the first school environment.

Running today

  • The public platform, where apps are built and tested on the fictional school
  • Package checks, policy checks and release builds in isolated jobs
  • An assurance report and a draft privacy notice for every release
  • Requests to connect an app to a school
Where things happen

Apps are built in one place and run in another.

Quad keeps building and real use apart by design. Where an app is built never holds school data, and where it runs is your school's alone.

Quad's public platformapp.quad.education
Where apps are built
  • A fictional school only. No real student, staff or parent data is ever allowed here, and no app runs here for real people.
  • Previews keep their data in the browser. Nothing a builder or tester types into a preview reaches Quad's servers or the AI.
  • Builders and testers are adults. Every account is 18 or over, and students never build here.
  • Hosted on AWS in the United States, with builders' own account details covered by our privacy policy.
Your school's environmentIn your school's region
Where apps run
  • Real data, from your school's own systems, reaches an app only after your school approves it, and only the data it was approved for.
  • Behind your school's sign-in. Only your school's SSO users can sign in. There is no guest access.
  • Regional schools are tenants of their region's shared school environment, which shares code and infrastructure, never data.
  • Enterprise schools get a dedicated environment in an AWS account of their own.

When an app moves to a school, only its code moves. Sharing, installs and copies never carry data, credentials or approvals with them.

Data location

Where your data lives.

Your school's region is chosen when it joins Quad, to meet the data residency rules that apply to you. Your school's data stays in that region.

Quad works for schools anywhere, so the public platform where builders work is hosted in the United States. It never holds school data.

WhatWhere it is heldWho can see it
Your school's dataStudents, staff, parents, classes and groups, and timetable, register or medical information where your systems supply itYour school's environment, in your regionOnly apps your school has approved, for the data they were approved for, and only what each signed-in person is allowed to see
What apps storeThe records an app keeps, such as consent forms or reading levelsYour school's environment, in a separate table for each appThat app alone, under its own access rules
AI building by your staffEnterprise onlyClaude on Amazon Bedrock, in your region's geography. For Australian schools, within AustraliaIt works on app code and simulated data. It never reads real school data
What Quad reviewsFor each app releaseQuad's review consoleQuad's reviewers see code, the app's manifest, screenshots from the fictional school and the security scan's report. Never school data
Builder accounts and app codeOn the public platformAWS, United States (us-east-1)The builder and the people they invite to a project

Regions open as schools join, once Claude's availability there has been checked. For example:

AustraliaAWS Sydney. AI within Australia, across Sydney and Melbourne.ap-southeast-2
United StatesA US AWS region, with AI in the US.
UK and EuropeA UK or EU AWS region, for schools in those markets.
Security stack

Our security stack at a glance.

Quad is built in layers. We run on independently audited infrastructure, and add our own isolation on top, so that safety never depends on an app, or the AI that wrote it, behaving well.

Infrastructure

Quad runs on Amazon Web Services. Each region's school environment has an AWS account of its own, apart from the public platform, and each Enterprise school's environment has its own account again. AWS's services and data centres are independently audited, including to SOC 2 Type II and ISO 27001.*

Each school kept apart

Schools in a regional environment share code and infrastructure, never data. Every record carries its school's tenant id and is scoped to it by default, and school data is protected by row-level security in the database. Each school has its own secrets for its sign-in and system connections, its own rate limits, and its own export and deletion.

Each app kept apart

Every app at every school has its own data table, locked by an access policy on that app's own functions, so one app can't read another's data, even through a bug. Apps have no server code of their own, and never receive database credentials, cloud credentials or anyone's session. Scheduled jobs run in an isolated function with no route to the internet.

Contained in the browser

Apps run on their own domain, quadapps.net, never on Quad's, each at its own address and inside a sandboxed frame. Their content security policy lets them load code and send data only to Quad's API and package CDN, so an app can't send your data anywhere else. The domain is HTTPS only, with HSTS preload.

Before an app reaches your school

Every release is checked twice: by Quad, then by you.

A release is checked and reviewed once, and every school then takes that same checked release. Nothing touches real data before your school approves it.

1

Package checks

Every package an app adds, and everything it depends on, is pinned and checked: no install scripts, a malware and known-vulnerability scan, and a licence check. Packages are re-scanned when new advisories appear.

2

Automated checks

Policy checks catch banned modules, raw queries, secrets written into code and data sent outside the SDK. Tests run, and the release is built in an isolated job with no network. An AI security scan adds findings for the reviewer.

3

Reviewed by Quad

A Quad reviewer looks at the code, the app's manifest, screenshots from the fictional school and the scan's report. Reviewers never need, or get, access to your school's data.

4

Approved by your school

Your IT lead sees one screen, in plain language: what the app reads from your systems, what it stores, and what it writes back. Only a school admin, signed in with your school's SSO, can approve it.

Upgrades ask again

Each school runs a pinned release and chooses when to upgrade. If an upgrade changes what the app reads, stores or writes back, or who can use it and see what, your school approves it again.

Stopped everywhere at once

If a release or package is found to be vulnerable, Quad can suspend it at every school running it, and tell those schools.

A record for every app

Each release comes with an assurance report: what it reads, stores and writes back, how it's isolated and where it runs, and the checks it passed.

Protection

How we protect your data.

Beyond the infrastructure, the platform itself enforces who sees what. Apps get their data only through Quad, so these rules apply to every app, whoever built it.

School sign-in

People use apps with your school's own accounts, through single sign-on. There are no separate passwords to manage, and apps are internal to your school: there is no guest access.

Scoped by default

Every field has a sensitivity level, from basic details to contact, academic, pastoral and medical, and an app asks for exactly the levels it needs. A reading tracker can't see medical notes because it was never granted them. Staff see all students, a parent sees only their own children, and a student sees only themselves.

Contact restrictions enforced

Where your school's system records that a parent can't be contacted about a child, for example under a court order, Quad applies it to every notification and task from every app. Apps can't opt out, and every suppressed message is audited. Where your system doesn't record restrictions, every linked parent is treated as contactable, and Quad tells you so when you connect an app.

Audited

Every read of pastoral or medical information is recorded, along with tasks, notifications and scheduled job runs. The record can't be edited, and your admins see it in your school's security centre.

Encrypted and backed up

Data is encrypted in transit and where it is stored. School databases keep point-in-time recovery, and an app's data is backed up before an upgrade changes it, so a school can roll back to the previous release.

AI kept away from school data

AI helps build apps; running one never uses AI. Quad's AI builder works only on app code and simulated data, and app data is never sent to it. Model access is held by Quad's AI gateway, never by the build environment, and under Amazon's terms for Bedrock your requests aren't used to train models.

For schools

What this means for your school.

Your school's data belongs to your school. Quad uses it only to run the apps your school has approved. We never sell or monetise school or student data, use it for advertising, or profile anyone.

A standard data processing agreement comes with setting up your school's console, and a formal signed version is available on request.

Your admins stay in control: they can suspend any app instantly, revoke what it can see, export its data, and see who has opened sensitive information.

Your data, your control

  • School data stays in your school's environment, in your region
  • Nothing touches real data until your school approves the app
  • Every app shows exactly what it reads, stores and writes back
  • Suspend any app instantly, revoke its permissions, or export its data
  • Apps move between schools as code. Data, credentials and approvals never move
  • We never sell or monetise school or student data
Questions and contact

Doing due diligence? Ask us anything.

We're happy to answer any question about how Quad handles your school's data. If you're an IT lead or privacy officer reviewing an app, start with its assurance report, then email us for anything it doesn't cover.

* Certifications mentioned on this page are held by Amazon Web Services, Quad's cloud infrastructure provider, not by Quad itself.

Quad handles personal information in line with the Australian Privacy Act 1988 and the Australian Privacy Principles. How we handle builders' own account information is set out in our privacy policy.

Build the thing you've been thinking about.

It starts free, it takes an afternoon, and nothing goes near your school's data until you say so.