Where exactly is our data?

Your primary data (the database, sign-in, and file storage) lives in Australia, in AWS's Sydney region. The application runs on Vercel's Sydney edge.

Two services sit outside Australia and we disclose them plainly: error monitoring (Sentry, US, with all personal data scrubbed before it leaves the app) and transactional email (SendGrid, US, which carries some notification content). The full subprocessor list is maintained and available on request. The data residency and isolation page has the detail.

Can we white-label First Six?

Yes. Each institution gets its own branding (logo, accent colour, fonts) and a tenant-aware sign-in, so students see your identity, not ours.

What happens if we leave?

Your data can be exported, and cohorts can be archived (kept and queryable, just out of the active view). Account deletion for individual students runs through your institution, since you own the sign-in identity. The specifics of an off-ramp are part of the engagement conversation.

Can we self-host?

Not today. First Six is delivered as a managed, multi-tenant service. If your requirement is continuity rather than control, an on-demand export is usually the answer; raise it early and we will talk through options.

How does this work with FERPA and GDPR?

The controls that matter for both are in place: row-level isolation, an immutable audit log, data-subject erasure, and a documented breach process with the right notification clocks (the Australian NDB scheme, plus GDPR's 72-hour rule where EU data subjects are involved). Our privacy policy is the binding statement; this is the plain-language version.