Privacy Policy

Roles

The organisation running a campaign on Election OS is the controller of the voter and supporter data it uploads; Election OS acts as a processor on that organisation’s instructions.

What we process

• Voter/roll records a campaign imports (name, contact details, area, and campaign-specific fields).
• Consent, contact, pledge, canvass and outreach activity generated in the Service.
• Account data for staff/admins (email, hashed password, 2FA), and audit logs of admin actions.
• Contribution records where fundraising is used (processed via third-party payment processors).

How we protect it

• Tenant isolation: each campaign’s data is scoped to its own tenant and access is membership-gated.
• Contact PII from official rolls is minimised and, where shown publicly, aggregated or synthetic — never exposing the underlying roll.
• Passwords are hashed; sessions are signed; server errors are captured with PII redacted.
• Consent is enforced before any message, call or text; unsubscribes and suppression are honoured automatically.

Your rights

Subject to the controller’s instructions and applicable law, individuals may request access, correction, or erasure of their data. The Service provides a per-voter data export (DSAR) and an erasure workflow; direct requests to the campaign that holds your data.

Retention

Data is retained for the campaign’s configured retention window and then swept, unless a longer period is required by law (e.g. campaign-finance record-keeping).

Sub-processors

Depending on configuration, the operator may use third parties for email/SMS delivery, payment processing, and hosting. The operator is responsible for listing and contracting these sub-processors.

Contact

Privacy questions should be directed to the operator of this Election OS deployment or the campaign controlling your data.