Supporter records and reveals

Supporter capture and resolving settings, and the audited single-record reveal.

Supporter capture and resolving#

Imports › Supporter capture and resolving (super admin) sets, per organisation:

1. What volunteers capture at sign-up: phone, ID number, names, birth year or date, gender and custom fields, each optional or required, plus the consent wording.
2. The resolving mode: off, volunteer checks the voter card, automatic on request, or automatic in the background.
3. The resolver call: method, HTTPS address, encrypted headers, a body with placeholders such as {{phone}} and {{document_number}}, and a timeout.
4. The success rule (2xx, JSON field equals, JSON field present or reply contains text), optional mapping of reply fields onto the supporter, and the result messages.
5. The charge per resolve and when it applies.

The page warns if the resolver host is not in the sub-processor register with a signed agreement, or if consent wording is missing.

Supporter records and single-record reveals#

Imports › Supporters (super admin only) lists an organisation's supporters with phone and ID number masked, plus campaign, ward and verification result, searchable by name.

To see one full value, choose Show:

1. Enter a reason.
2. Enter a fresh authenticator code.
3. The isolated reveal service records the audit in both chains before opening the value.
4. The value is shown without caching and clears from the screen after 30 seconds.

Under the owner decision of 9 October 2026, single-record reveals of a supporter's phone or ID number work on the public operator site with a reason and a fresh authenticator code; no hardware key is needed for these. All other reveals keep their stricter rules.

Contact privacy and approved exports#

Exports › Contact privacy handles other reveals and encrypted exports. Each reveal needs a reason, a new authenticator code and the hardware key. Exports need approval from two different eligible operators, are generated into encrypted storage and are downloaded through a short-lived signed link.

Reveal only when there is a lawful reason, and record it accurately. Reveal activity is reviewed.

Data imports#

Imports › Data imports (data officers and super admins) is the intake for supporter lists: declare the source and lawful basis, map columns, review the first 50 rows, then start. Rows needing review are resolved one by one. Imports can be rolled back for seven days. Import API tokens allow a data officer to automate uploads for one organisation from the operator network; tokens are shown once and can be revoked.