What the AI sees, and what it does not.
AI-assisted matching is one optional step in Teamer, and a narrow one. Here is exactly what it touches, what leaves the country, and what stays in staff hands.
Last updated June 2026
When AI is involved at all
For most of what Teamer does, no AI is involved. Building surveys, collecting responses, managing enrolments, editing teams, and publishing them all run without it.
AI-assisted matching is one optional step. It helps group students by the free-text answers they give, for example a short description of a project they would like to work on, so that staff have a sensible starting draft to review. You decide whether to use it.
What the AI actually sees
Only the free-text answers themselves, with an internal reference code in place of the student. The request that goes out carries the survey question and the wording of each answer, and nothing that identifies who wrote it.
Names, emails, student numbers, and the rest of a student's record are never part of that request. They stay in Teamer's database in Australia.
What leaves Australia, and to whom
Teamer stores everything in Australia, in the Sydney region on Vercel and Supabase, which run on AWS. The one routine exception is this optional step: when AI-assisted matching is turned on, the de-identified free-text answers are sent to OpenAI in the United States, which returns suggested groupings.
Under OpenAI's API terms, content sent through the API is not used to train their models. Nothing else about a student, and no data at all when the feature is off, leaves the country by this route.
What stays a human decision
The AI suggests, it does not decide. Its output is a draft grouping that lands in front of staff, who can inspect it, move students, and change anything before it becomes a team.
No team reaches a student until a staff member publishes it. If you would rather not use AI at all, you can form teams by hand and the feature never runs.
What Teamer does not claim
Teamer is an independent product, built and run from Sydney. It is not endorsed or approved by any university, and it holds no SOC 2, ISO 27001, or IRAP certification. Nothing here is meant to imply otherwise.
This page is a plain account of how AI-assisted matching handles data, written so a course can pass it to the people who need to check.
For where all of your data is hosted and what else stays in Australia, see the Trust & data residency page. For any question your IT or security team has, email security@teamer.university.
Start a pilot