Supporter and volunteer databases
One record per person with the history of contact.
Supporter records, consent and reporting for campaigns and advocacy groups. Built by the team that migrated a national platform of sensitive records with zero downtime.
The ICO treats political opinions as special category data, which raises the bar for holding and using it. A campaign needs to know who agreed to what, and be able to show it.
a national platform migration of sensitive records with zero downtime and security testing during delivery
We have no published politics case. We say so on the first call and show the closest work.
One record per person with the history of contact.
What each person agreed to, when and how.
Campaign messages and events tied to the right consent.
Records moved from spreadsheets or a legacy tool, with the mapping documented.
Door-knocking data captured offline and synced later.
Who was contacted, on what basis, and the response.
The imprint point comes from the Electoral Commission and the data points from the ICO. Both are pointers, and your lawyers decide how they apply.

Different sector, same sensitivity. A Norwegian technology company needed its national platform modernised after a previous vendor missed the deadline. A dedicated team moved years of sensitive records, with penetration testing, static analysis and network assessment during delivery.
Teams whose data grew in spreadsheets.
Organisations with supporters, donors and volunteers.
Builders of tools for voters and councils.
Firms that need a data platform behind their client work.
Related reading: social networking software, news and media software and education software.
Not yet published. We say so on the first call and show the closest work, which is a national platform migration of sensitive records.
No. That advice comes from your lawyers and your data protection lead. We build the records and controls they specify.
In your cloud accounts, in the region you choose. You own the accounts from the first commit.
You do, from the first commit. Repositories and cloud accounts stay in your name.
Thirty minutes with the engineers on what you hold, how consent is recorded and where the data lives.