03 / Your data

Student work never leaves your control.

Apollo has no server. No account in the middle holding your students’ work, so there is nothing for anyone to breach. Including us.

01

Nothing is stored

Submissions are held in memory while the assessor works, then cleared when Apollo closes. No database of student work, on your machine or ours.

02

De-identified before sending

Names, student IDs, emails and phone numbers are removed first, painted out of scans and photographs. It happens on the trainer’s machine, before anything is transmitted.

03

Your own AI account

Apollo marks using your organisation’s own Anthropic API key. Billed to you at cost, visible in your console, under your own terms. We never see it.

04

The assessor decides

Apollo drafts; a qualified person places and confirms every mark. The returned document carries their name and the time of sign-off.

04 / Being precise

What actually leaves the building.

01

What is sent

De-identified assessment text and, where a submission is an image, the redacted page image. It goes from the trainer’s browser directly to Anthropic using your key.

02

Where it goes

Anthropic’s API. Processing occurs outside Australia. Anthropic does not use API data to train its models. Your RTO should satisfy itself as to Australian Privacy Principle 8 before adopting, as it would for any offshore processor.

03

What is never sent

Student names and identifiers, your unit library, your standing guidance beyond the unit being marked, and anything at all once the assessor closes the app.

04

The one limit worth stating

Identifiers cannot be reliably stripped from handwriting. Where a page is handwritten, Apollo tells the assessor before it sends and lets them decide.

05

Spend is capped by you

A monthly limit sits on your own Anthropic account, and usage is visible to you at all times.

NEXT / Why Apollo → How it compares to the platforms that run your college, and how the figures were measured. Download Apollo