Data locations

Pyron is hosted by Amazon Web Services in Australia. Customer Data, meaning the records, forms, files and attachments in a workspace, together with its audit trail and its backups, is stored in the AWS Asia Pacific (Melbourne) region, and some services run in the AWS Asia Pacific (Sydney) region. Credentials a workspace keeps in the Pyron Vault are stored, encrypted, in the same Australian environment. Pyron AI runs on Amazon Bedrock within Australia.

A few of our service providers process limited information outside Australia. Each one, what it receives and where, is listed below.

Where each kind of data is held

Data	Where
Records, forms, pages, automations, files, comments, the audit trail and backups	AWS Asia Pacific (Melbourne)
Logins kept in the Pyron Vault	AWS Asia Pacific (Melbourne), encrypted under keys in AWS Key Management Service
What people ask Pyron AI, and its answers	Amazon Bedrock, through its Australian cross-region profile, which keeps each request within the Sydney and Melbourne regions
Text turned into the index behind search by meaning	Amazon Bedrock in AWS Asia Pacific (Sydney). The index itself is stored with the records, in Melbourne
Email Pyron sends	Amazon Simple Email Service, AWS Asia Pacific (Sydney)
Single sign-on	Amazon Cognito, in AWS in Australia
Web searches the assistant and automations make	Amazon Bedrock AgentCore, through our gateway in AWS Asia Pacific (Sydney). AWS states that such a query is served within AWS and is not sent to a third-party search engine
Logs, metrics and traces of how the service is running	Grafana Cloud, Australia
Traffic, page rendering, the running of pages and automations, live updates, printing reports as PDFs, and reading public web pages for the assistant	Cloudflare, at its data centre nearest the user: normally in Australia, but not guaranteed. Kept only while it is processed
People's names, email addresses and roles, the names of places, and a record of access decisions	Permit.io, United States
Error reports	Sentry, European Union
Pages visited by browser automation and what is entered into them	Steel, United States, and only where a workspace sets it up
Alert text, which may name a workspace	All Quiet and Slack, outside Australia

Every service provider

Provider and what it does	What it receives	Where
Amazon Web Services: hosting, storage, backups, email delivery, single sign-on and the Amazon Bedrock service used by Pyron AI	All Customer Data	Australia
Cloudflare: network security and delivery, page rendering and the running of customer automations	Traffic and data in transit, kept only while it is processed	Its data centre nearest the user, normally in Australia but not guaranteed
Grafana Labs: operational logs, metrics and traces	Technical records of how the service is running	Australia
Permit.io: authorisation	User names, email addresses, role assignments, the names of places in a workspace, and a record of access decisions	United States
Functional Software (Sentry): error reporting	Error reports, which can contain fragments of the data being processed	European Union
Steel: remote browsers for browser automation, an optional feature that nothing uses by default and that runs only where a customer sets up an automation to use it	The pages visited, what is entered into them (which can include sign-in details the customer keeps in the Pyron Vault for that site) and saved sign-in sessions for those sites	United States
All Quiet and Slack: alerting our on-call staff	Alert text, which may name an affected workspace	Outside Australia

Browser automation is optional and nothing uses it by default. Where a customer sets up an automation that uses it, the remote browser runs in the United States.

We remain accountable under the Privacy Act 1988 (Cth) for how each overseas recipient handles personal information we disclose to it. Changes to this list are recorded in the revision history of our Privacy Statement.

How long we keep it

• Audit trail records: 24 months.
• Customer Data: as configured by the customer, and for the subscription term. On termination, a 30-day export window, then deletion within 90 days. Backup sets are deleted on their normal rotation and remain encrypted and inaccessible until then.
• Security logs, meaning records of activity on our cloud accounts and infrastructure: 12 months. Application logs: up to 30 days. Error reports: up to 90 days.
• Enquiries and business contacts: 7 years, or until you ask us to remove them.

How it is protected

Encryption at rest to AES-256, and in transit over public networks to a minimum of TLS 1.2. Multi-factor authentication for privileged access. Structural access enforcement through the platform's permission engine, whose default answer is no. An audit trail of every change, kept for 24 months: records are only ever added, never edited, and each is cryptographically linked to the one before it, so tampering would be evident.

The Security overview says how each of these works, and what we don't have yet.