Product
Solutions
Trust
ResourcesDocs
Live previewBook a demo
Trust Centre

Subprocessors

Who we rely on, what each one does, and where it runs.

Australia
Where your data of record lives
30 days
Notice before a new one is added
One list
Kept on our knowledge base
Stated
Purpose, region and data seen

Who handles data on our behalf, where your data of record sits, and how you hear about changes.

Last reviewed 26 October 2026

A subprocessor is a third-party service that handles data on our behalf for a specific job. Your data of record is hosted in AWS Sydney, and the list names every service with its purpose, region and exactly what it can see. We give at least 30 days' notice before adding one. Read the current subprocessor list.

How we manage subprocessors

Each service has to earn its place on the list. This is how one gets there, and how you hear about it.

  1. Add only when it earns its place

    A third party is added only when it does a job we can't do as well ourselves, and only with access scoped to that job.

  2. Scope what it can see

    Each service is scoped to a specific job, and the list states what it receives.

  3. Bind it by agreement

    Data protection terms are built into the service agreements we accept, and the Knowledge Base records the position provider by provider.

  4. Disclose and review

    The list is public, dated and reviewed. We give at least 30 days' notice of an intended new subprocessor, and you can object during that time.

What the list tells you

Each entry answers the questions a privacy reviewer asks. The entries themselves live on our knowledge base, so there is only one copy to keep current.

Where your data of record sits

The database, sign-in and file storage are hosted in Australia, in AWS Sydney, isolated per institution. Everything else on the list supports that core for a specific job.

What each service is for

The job each one does, stated plainly, so you can judge whether it needs to be there.

Where it runs

The region for each service, including the ones outside Australia.

What it can see

Exactly what data each service receives, stated plainly.

How changes reach you

At least 30 days' notice of an intended new subprocessor, with the right to object, and a dated list you can check at any time.

FAQs

Can't see your question? Ask us, or email security@firstsix.com.au.

Does any student data leave Australia?

Your data of record stays in Australia, in AWS Sydney. Some services, such as email delivery, process data in transit, and each is listed with what it sees. Encrypted backups are held in two places, readable only with a key kept offline.

How will we know if your subprocessors change?

We give at least 30 days' notice of an intended new subprocessor, and your institution can object during that period. The live list on our knowledge base is updated when anything changes and shows the date it was last reviewed.

Is our identity provider a subprocessor?

No. Your IdP is your own system. First Six links a sign-in to an existing person; it never receives or stores your directory.

Are subprocessors bound by agreements?

Yes. Data protection terms are built into the service agreements we accept. Where you switch on Slack or Teams alerts, or a webhook to your help desk, the receiving system sits under your own agreement.

Do you use student data to train AI?

No. Student data is never used to train AI, and the AI provider's terms prohibit it. The student app has no AI, and our AI features are drafting tools for staff.

Questions about where your data sits?

We're happy to walk your security and procurement teams through the full list, the regions, and the agreements behind each one.