Security

How Pythagoro protects organisation data.

Last updated 4 November 2026.

• Where data lives: in Sydney, Australia, in one database with separate areas for the platform and each app.
• Access on the server: who can see what is enforced by database rules, APIs and file storage, not only by hiding things on screen. One organisation can never read another's records.
• Least access: people get only the apps and records their organisation grants. Confidential registers are visible only to named people.
• Records that cannot change: confirmed minutes, accepted policy versions and signed report editions are locked on the server. A correction creates a linked new version.
• Audit: every grant, revocation and administrator action is recorded.
• Encryption: in transit and at rest.
• Sign in: email link and Microsoft work accounts, with passkeys when available. Two sign in methods with the same email never join automatically.
• Leavers: access ends at 23:59 on the end date in the organisation's timezone.
• Testing: every release is reviewed and tested against a real database before it ships.

Certifications: none claimed. This section will list a certification only once it is held.

To report a security issue, see Report a security issue.