Privacy Policy | Who You With?

1

Plain English summary

The important points before the detail.

Your individual political answer is not published.

Public results are aggregate only. Small local samples are hidden until display thresholds are met.

No unnecessary identity fields No full name, full address, telephone number, party membership number or photo ID is requested.

Email is for account control Email verification helps stop repeat fake entries and lets a user return to update or delete their entry.

Postcode is not stored with the entry The postcode is used for area lookup only. The matched voting areas are stored instead.

Entries do not count forever Online entries count for 24 months, then become dormant unless refreshed.

2

Controller and contact

Who is responsible for the site’s data handling.

Data controller Who You With?

Contact contact@whoyouwith.org.uk

ICO registration ZC136486

ICO registration confirms the data-controller registration. It does not mean the ICO endorses the site or its results.

3

What this service does

The purpose of collecting any data.

Who You With? lets verified users record their current political support and related political-context answers. The purpose is to produce anonymous aggregate results by party, movement type and voting area.

The site is a participation-based political preference tracker. It is not a traditional weighted opinion poll and should not be treated as an election forecast.

4

Data collected

The data is grouped here so the purpose is easier to understand.

Account and access data

Email address entered at sign-in, used to send secure login links.
The public voter email is stored as a protected keyed lookup hash rather than plain text.
The link between the email verification record and the political entry is encrypted.
Session cookies, anti-abuse cookies and remember-this-device tokens where used.
Consent records and timestamps.

Political preference data

Current political support answer.
Previous UK General Election answer.
Previous local election answer.
Current political party membership answer, if voluntarily supplied.
Previous political party membership answer, if voluntarily supplied.
Aggregate entry-change counts, without old/new individual party history.

Area matching data

Postcode entered for lookup only.
Derived area data, including country/nation, region, Westminster constituency, district/borough/unitary council, county council division and ward where available.
The postcode itself is discarded after lookup and is not stored with the entry.

Reminder and anti-abuse data

Optional encrypted contact email for expiry reminders, only if reminder emails are switched on.
Hashed IP address, hashed browser/user-agent and hashed device signals for basic abuse prevention and rate limiting.
Technical anti-abuse signals are kept separate from the political entry where practical.

Donation and payment data

Donation amount, currency, payment status and donation reference.
SumUp checkout ID, transaction ID and payment timestamps where returned by the payment provider.
Optional receipt email if supplied, stored encrypted and used only for donation/payment records.
Hashed IP address and hashed browser/user-agent for basic fraud prevention, abuse prevention and payment troubleshooting.
Donation records do not contain political answers, party choice, postcode, ward, constituency or tracker entry ID.

No-email assisted entries

An authorised admin may create a no-email assisted entry where a person cannot use the online form.
These entries use a private access code instead of email.
The plain access code is shown once to the person and is not stored. Only a keyed hash is stored for later renew/delete matching.
No-email assisted entries use a shorter active period of 12 months and a 3 months recovery period.

5

Data not requested

Data minimisation is part of the design.

No full name No full address No telephone number No membership number No photo ID No public individual answer list

6

Donations and payments

Donation records are kept separate from political tracker entries.

Donations are separate from political answers.

A donation record is not linked to a person’s party choice, political answers, postcode-derived areas, ward, constituency or tracker entry.

Who You With? accepts voluntary donations to support hosting, security, development, data maintenance, postcode and area matching, public awareness, and advertising the Who You With? tools and service.

Payments are processed using SumUp Hosted Checkout. Card details are entered on SumUp’s secure payment page and are not stored by Who You With?.

Donation totals may be published publicly as aggregate figures, such as the past 90 days, past 365 days and all time. Donor names, donor email addresses, payment references and political preferences are not published.

Donation/payment records may be kept where needed for payment reconciliation, fraud prevention, accounting, legal obligations and transparency reporting.

7

Political answers and lawful basis

Political opinions need stronger protection under UK GDPR.

Political opinions and political party membership information are special category data under UK GDPR. Who You With? asks for explicit consent before storing these answers for the stated purpose of producing anonymous aggregate political preference results.

The lawful basis for processing account, login and anti-abuse information is legitimate interests: operating a secure one-user-one-entry tracker, preventing manipulation, and maintaining service integrity.

For political answers and voluntary party-membership answers, the Article 6 lawful basis is consent. The Article 9 special category condition relied upon is explicit consent for the stated tracker purpose.

Consent can be withdrawn by deleting the live entry or by contacting contact@whoyouwith.org.uk.

8

Postcode and area lookup

The postcode is used to attach an entry to voting areas.

The postcode is used for lookup, not stored with the political entry.

The application stores the matched area fields only, such as region, constituency, council area, county division and ward where available.

The postcode lookup is performed using Postcodes.io. That means the postcode entered is sent to Postcodes.io to return the relevant geographic and electoral-area data.

9

Public results

What the public can and cannot see.

Public results are shown as aggregate totals, percentages, comparisons and movement tables. Individual answers, email addresses and raw postcodes are not shown publicly.

Local results are hidden until minimum sample thresholds are reached. Small result groups are suppressed to reduce the risk of identifying individuals in small areas.

The admin dashboard is also designed around aggregate operational data rather than individual voter records.

10

Technical honesty

Anonymous public results are not the same as saying the live service holds no personal data.

Public output is anonymous and grouped. The underlying service records are still treated as personal data because an email-verified account system exists and each user can return to control one current entry.

The database is designed so that the email verification record and political entry are separated, with the bridge encrypted. This reduces the usefulness of a database-only leak, but the live system is still handled as sensitive personal-data processing.

11

Retention

Entries are time-limited unless refreshed.

Active for 24 months Email-verified entries count from the most recent submission or update.

Dormant for 12 months The entry stops counting publicly, but the same verified user may return and refresh it.

Deleted after 36 months If the entry is not refreshed, it is deleted from the live system.

Older entries are excluded from live results, unlock thresholds, maps and public percentages.

Reminder emails are optional and off by default. If switched on, the contact email is encrypted and used only to warn before the active counting period ends. Reminder emails do not include political answers, postcode, ward, constituency or council area.

If deletion is requested or completed through the delete page, the live login record and current entry are removed. Historic aggregate snapshots may not be recalculated, but they do not identify the user.

When an entry is deleted, a minimal deletion log may keep a hashed version of the email address, deletion method and deletion time for up to 12 months. It does not include political answers, postcode, area records or account records.

Login tokens are temporary. Remember-this-device tokens expire automatically. Technical anti-abuse records may be retained for security and rate-limiting purposes.

Donation records are separate from tracker entries and may be retained as payment, accounting, fraud-prevention and transparency records where needed. Optional receipt email addresses are stored encrypted and are not published.

12

Sharing and processors

The service needs some technical providers to operate.

Data may be processed by hosting, email delivery and technical infrastructure providers necessary to run the service. Postcode lookup requests are sent to Postcodes.io. If you donate, payment and checkout data is processed by SumUp. Party logos are served from local site files rather than third-party image domains.

Who You With? does not sell individual user data.

Individual user data is not sold to political parties, candidates, advertisers or data brokers.

13

Your rights

How users can control their entry and make requests.

Delete online Logged-in users can use the Delete my entry page to remove their account and tracker answers from the live system.

Assisted entries No-email assisted participants need their private access code to ask for renewal or deletion of that assisted entry.

Email request You can request access, correction, deletion, restriction, objection, portability or withdrawal of consent by emailing contact@whoyouwith.org.uk.

ICO complaint You also have the right to complain to the Information Commissioner’s Office if you believe your data has not been handled properly.

Who You With? aims to respond to rights requests within one month unless the law allows more time because a request is unusually complex.

14

Security

The main technical safeguards used by the service.

Email verification Keyed email lookup hashes Encrypted identity-to-entry bridge Token hashing HttpOnly and SameSite session cookies CSRF protection Prepared database statements Rate limiting Output escaping Minimal data collection

Hosting, database and backup access must remain restricted. The service is designed to reduce what is exposed if one layer fails, but no online system can honestly claim zero risk.

15

Changes to this notice

This page may change as the service develops.

This notice may be updated if new processing activities are added, if the technical setup changes, or if the wording needs to be made clearer.

Last updated: 6 May 2026.