Security and Trust Centre
See how access, Australian data location, encryption, backups, retention and incident response apply to Insia—and where a control has a specific limit.
How data is protected
Each control names what it protects and any exception that matters. Insia does not imply a certification or universal assurance that has not been evidenced.
This does not mean every supporting service or provider processes data only in Australia; service and data-class scope matters.
No access system is described as risk-free; production configuration is reviewed separately from the code contract.
This is not an end-to-end or universal-encryption claim across every provider, data class and device.
No public recovery-time, recovery-point, uninterrupted-availability or no-data-loss promise is made.
Identity checks, law, security, disputes, backups, audit records and broker obligations can affect timing and what can be deleted.
No guaranteed prevention, response time, notification deadline or independently certified response programme is claimed.
This public summary is not a contractual or exhaustive subprocessor schedule; request the current feature-specific data-flow scope for review.
Private reporting route
Keep credentials, customer information and unnecessary exploit detail out of the first message. The team can arrange an appropriate secure follow-up.
