Help / Security, privacy & your data / Where your data lives
Where your data lives
Reference1 min
In one sentenceYour workspace records sit in a database in Sydney, Australia; sign-in identity, outbound email and error reports go to named providers in the United States.
| What | Where, and who runs it | When it applies |
|---|---|---|
| The workspace database - deals, companies, contacts, quotes, time entries, candidates, employee records | A Postgres database on a DigitalOcean server in Sydney, Australia. Backups stay in the same region. | Always |
| Your sign-in identity - name, email address, sign-in metadata | Clerk, United States. Headway never sees or stores a password. | Every sign-in |
| Social sign-in | Google, or the provider you pick, shares your name and email with Clerk | Only if you choose to sign in that way |
| Files and attachments - a CV on an application, a file on a deal | Amazon Web Services S3, Sydney, Australia | Only when attachment storage is switched on for the service |
| Email the product sends - a message to a candidate, the daily digest | Resend, United States. It handles the recipient's address and the message. | Only when email sending is configured |
| Error reports - technical details of a fault and the request around it | Sentry, United States | Only when error reporting is enabled |
Traffic is encrypted in transit. Apart from these flows, and any integration you switch on yourself, workspace records are not routinely moved outside Australia. No third-party analytics runs inside the application; it keeps its own per-workspace counts, with no names or record contents in them. The privacy policy at headwaystack.com/privacy is the authoritative list.
Did this answer it? Not quite - tell us