Answers your reviewers can check for themselves
What a security, privacy or procurement reviewer can verify in the product and its documents: who looked at what, who can see the figures, who at First Six can reach a record, and where the data sits.
What you can track
Each figure below is already in First Six, and each card shows where to find it.

Sensitive reads in the audit trail
Every individual profile open, contact reveal, bulk export and break-glass read is written to an append-only audit trail; update and delete are revoked at the database.
In the console: Settings, Audit trail, viewable by institution admins and exportable as CSV.

First Six access to student records
There is no standing access. The only path is a break-glass grant your admin opens for one student, with a reason, for at most 72 hours. It is redacted and can be revoked.
In the console: Settings, First Six access, with every grant and read recorded in your own audit trail.

Small groups withheld in downloads
Downloaded reports withhold any figure from fewer than five students and say how many weeks or categories were held back, so a missing figure is always explained.
In the console: The Support for Students report, which states the rule and what was withheld.

Data location and subprocessors
The data of record sits in AWS Sydney. Every subprocessor is listed with its purpose, region and what it can see, with 30 days' notice before a new one is added.
On our Knowledge Base: The live, dated subprocessor list.

Sign-in and session control
Single sign-on through your identity provider is the only way in, with your MFA. Staff sessions end after 8 hours idle and student sessions after 30 days.
In the console: Team, where you can deactivate a leaver and revoke their sessions in one action.
The documents your review will ask for
A pre-filled HECVAT-Lite, a DPA and our security documents, ready for your security, privacy and procurement teams.
See it with your own students
Walk your security review through the product and its documents.

