How we protect your organisation’s data

Your platform data — documents, board records, donor and financial information — is stored in Ireland, in Amazon Web Services' eu-west-1 region, which AWS's ISO 27001 and SOC 2 certifications cover. The website's pages are served from Belgium. Transactional email, the deployment pipeline and font delivery use providers in the USA, and card payments run on Stripe's global network; each is listed below, with what it sees. No customer data is sent to any AI model.

Every connection to the platform is encrypted with TLS, so data in motion can't be read in transit. Data at rest is encrypted by our cloud provider.

The most sensitive fields go further: PPS numbers are additionally encrypted with AES-256 at the application layer and can be decrypted only by an authorised administrator of your organisation, never by ordinary users and never in bulk.

EasyGovernance is multi-tenant — many organisations share the same platform — so this is the boundary that matters most. It's enforced by Row-Level Security in the database itself, on every table, not merely in the application. Your organisation's records are invisible to any other organisation at the deepest level, so even an application error cannot leak data across that line. This isolation is re-verified automatically on every release.

Access is granted by role and capability: an owner or administrator, a board member, a treasurer, someone who handles income. Each person reaches only the areas their role permits, and the system is fail-closed — if a permission hasn't been explicitly granted, access is denied by default rather than allowed. Administrators manage their own team's access from within the platform. When someone leaves, their access ends at once, across every record.

Accounts are protected by a managed authentication service. Two-step sign-in with an authenticator app is available to every user, and an organisation can require it. We never see or store your password in readable form. Team invitations use single-use links tied to a specific person, and password resets are self-service — so access can be granted and revoked cleanly as your team changes.

All card payments are handled by Stripe, a PCI-DSS Level 1 provider. Card numbers are entered directly into Stripe's secure systems and never pass through or rest on EasyGovernance. We record that a payment happened, not the card that made it.

Every change to the governance record is logged, per feature, and visible to your organisation — across documents, board meetings, donor records and consent actions. The logs are append-only for members: entries are added, never edited or removed by a user. This is what lets you produce evidence on demand for a regulator, auditor or the board, and show not just the current state but how you got there.

Your documents in the vault are backed up automatically every night to separate, encrypted storage in the EU, so they can be restored in the event of a failure. The database that runs the platform is additionally protected by our cloud provider's managed daily backups.

Security isn't a one-off review. Automated checks run in our build pipeline and block insecure changes from ever shipping — verifying that data-isolation rules cover every table, that database functions can't be reached by anyone unauthorised, and that no view exposes data across organisations. A strict content-security policy limits what can run in the browser.