Now in early access · We are onboarding campaigns now. Get set up →
Security & compliance

Built for organisations that take trust seriously.

Electoral registers, voting intentions and supporter records are some of the most sensitive data a campaign holds. Cadrify keeps that data in the EEA, encrypts it in storage and in transit, and scopes every record to a single organisation. Here is how that works, in plain terms.

EEA hosting Encrypted in transit and at rest Strict organisation separation Full, exportable audit trail
Where your data lives

Hosted in the EEA

Your register and door-knock data is stored in a PostgreSQL database in Frankfurt, Germany, on infrastructure run by Render. Data does not leave the European Economic Area at rest.

What you can rely on

  • Register and door-knock data stored in Frankfurt, within the EEA
  • Data does not leave the EEA at rest
  • Email runs through a specialist provider that never receives register data
Britain & GDPR

Privacy by design

For British parties, unions and membership bodies, where records sit and who can reach them matters. Cadrify is built around data minimisation and purpose limitation, and every record is bound to a single organisation.

What you can rely on

  • EEA hosting for register and supporter records
  • GDPR-aligned processing with data minimisation and purpose limitation
  • Breach notification within 72 hours where required by UK GDPR
  • A Data Processing Agreement available for your due diligence
Data protection

Encryption by default

Every connection to Cadrify is encrypted, and stored data is encrypted at rest by the underlying infrastructure. Passwords are never stored in a readable form.

What you can rely on

  • TLS (HTTPS) on every connection, with no unencrypted HTTP allowed
  • Encryption at rest for database records and backups
  • Secure passwords with minimum strength requirements
  • Login rate limiting and account lockout after repeated failed attempts
Access on a need-to-know basis

People see only what their job needs

Your register and supporter data stays under lock and key. Cadrify lets you grant each person only the functionality and data their role calls for, so exposure stays limited and nothing is shared more widely than it needs to be.

What you can rely on

  • Limit each user to only the functionality they need for their job, to limit data exposure
  • Activists cannot browse the register, only the round assigned to them
  • Door-knock rounds expire, so access ends once the task is done
  • Thorough auditing across the app, fully exportable, so you can see who did what and when
For IT & procurement

Technical details

A concise summary for security questionnaires. For the full policy, audit log requests and the Data Processing Agreement, see the links below or email security@cadrify.org.

Application hosting
Render, Frankfurt EEA
Database
PostgreSQL on Render, Frankfurt EEA
Transactional email
Resend, for invitations, password resets and notifications. Routes through Dublin, Ireland (EEA). Does not handle register data.
Integrations
Optional, off by default. A customer may connect an external CRM (Action Network, NationBuilder, Salesforce, Movement) using their own account; only supporter contact data syncs, never register or door-knock data.
Encryption
TLS (HTTPS) in transit, encryption at rest by the underlying infrastructure.
Passwords
Secure storage with minimum strength requirements.
Sessions
256-bit random token in a secure, HttpOnly cookie, 24-hour expiry, invalidated on logout or password change.
Tenant separation
Every record is bound to one organisation and queries are scoped so organisations cannot read each other's data.
Breach notification
Within 72 hours where required by UK GDPR.
ICO registration
Registered with the Information Commissioner's Office as a data controller. Reference ZC158949.
Organisation certification
Cadrify is not ISO 27001 or SOC 2 certified as an organisation. Our infrastructure providers maintain their own independent certifications.

We say what is true today, not what sounds good. Cadrify is not certified as an organisation against ISO 27001 or SOC 2. Multi-factor authentication, single sign-on and external penetration testing are on our published roadmap. The security whitepaper sets out current controls and what is planned.

FAQ

Common questions

Where is my data hosted?

Your register and door-knock data is stored in a PostgreSQL database in Frankfurt, Germany, on infrastructure run by Render. Data does not leave the European Economic Area at rest.

Is my data encrypted?

Yes. Every connection uses TLS (HTTPS), with no unencrypted HTTP allowed, and stored data and backups are encrypted at rest by the underlying infrastructure. Passwords are never stored in a readable form.

Can other organisations see my data?

No. Every record is bound to one organisation and queries are scoped so organisations cannot read each other's data. Within your organisation, each person sees only the functionality and data their role calls for.

Is Cadrify ISO 27001 or SOC 2 certified?

Cadrify is not certified as an organisation against ISO 27001 or SOC 2. Our infrastructure providers maintain their own independent certifications. Multi-factor authentication, single sign-on and external penetration testing are on our published roadmap.

Do you offer a Data Processing Agreement?

Yes. A Data Processing Agreement is available for your due diligence. You can read it online, or request it along with our security policy and whitepaper from security@cadrify.org.

Questions about security?

Read the full policy and whitepaper, or book a demo to go through your due diligence.