Data Sovereignty

Data collected at an Australian site stays in Australia. It is held on the customer edge unit and in the Sydney-hosted control plane.

For Australian operators

Offshore transfer of personal information is governed by APP 8. Where a vendor reads site data into an offshore region, the operator has made a cross-border disclosure.

The Canopy control plane runs on Australian infrastructure in Sydney. Support is in Australia. There is no offshore path in the architecture.

What is stored where

On your Edge Unit

Encrypted frames, for a rolling buffer of seconds. Model weights. Encrypted event queue. Nothing leaves without an explicit event payload.

In our Sydney control plane

Event aggregates, user accounts, device metadata, audit logs. No raw frames. No biometrics.

Single-tenant options

For regulated industries — property groups with sensitive tenancy data, transport operators with security obligations, government-adjacent sites — we offer a single-tenant deployment. Your control plane runs on hardware we host in a Sydney data centre, logically isolated from other customers. This is the default for security-critical sites.

Talk to us about your data residency requirements

Start a conversation

Frequently asked questions

Where exactly is my data hosted?

Sydney, Australia. Our control plane runs on Australian infrastructure. Your event data, user accounts, and audit logs never leave the country. There is no offshore path in the architecture.

Do you offer single-tenant deployments?

Yes, for regulated industries. Your control plane runs on hardware we host in a Sydney data centre, logically isolated from other customers. This is the default for security-critical or classified sites.

Can my data be used to train general models?

No, not without an explicit written agreement. We do not quietly use your events as "model improvement" under a buried EULA clause. If we ever want to, we will ask, in writing, and you will say yes or no.