Australian student data, hosted in Australia.
A plain account of where your data sits and how it is handled, written so a course can pass it to the people who need to check.
- Hosted in Sydney, Australia
- Encrypted in transit and at rest
- Role-based access control
Where your data lives
Teamer runs in the Asia Pacific (Sydney) region, ap-southeast-2. The app runs on Vercel and the database and file storage on Supabase, both on Amazon Web Services in Sydney. Everything a course needs to run is stored there, in Australia: names and emails for staff and students, enrolment and tutorial structure, the teams Teamer generates, survey responses including free-text answers about things like skills and availability, and any attachments sent through complaint workflows.
Passwords and sign-in links are never stored in readable form, only as one-way hashes. Data is encrypted at rest, kept on a private network, and served only over HTTPS.
What leaves Australia
Almost nothing. Transactional email, the invitations and notifications a course sends, runs through SMTP2GO on its Australian servers, so that stays onshore too.
The one routine exception is AI-assisted matching. When it is turned on, de-identified free-text answers, never names or emails, are sent to OpenAI in the United States to suggest draft groupings that staff then review. Nothing else routinely leaves the country.
What Teamer does and does not claim
Teamer is an independent product, built and run from Sydney. It is not endorsed or approved by any university. It holds no SOC 2, ISO 27001, or IRAP certification, and nothing here is meant to imply otherwise.
What this page offers is a plain, honest account of where your data sits and how it is handled, so a course can pass it to the people who need to check.
Questions from IT or procurement
If your university's IT or security team needs a fuller summary, or you have any questions, email security@teamer.university, read our Privacy Policy, or see how AI-assisted matching handles data.
Get in touch