Privacy

What this site does today

• No accounts, no logins, no personal profiles. There is nothing to sign in to.
• No cookies are set by this site, and no cookie banner is shown, because there is nothing to consent to.
• No analytics, no tracking pixels, no advertising or social embeds. No third-party script runs on these pages.
• No fonts, images or files are loaded from another party. Everything is served from this site’s own origin, so no external service learns that you visited.
• The forms do not submit. The enquiry form and the volunteer expression-of-interest form have no destination and collect nothing. Anything typed into them stays in your browser.

The one thing outside our control is the hosting provider, which — like every web host — may record technical request logs. The provider has not been chosen yet, and the arrangement will be described here when it has.

What will apply once the forms are live

Published in advance so it can be judged before anything is collected.

• Only what is needed. A name, a way to reply, and what you chose to tell us. No enrichment, no third-party data appends, and no wealth screening of visitors or donors — a practice that is common elsewhere and would contradict everything on the principles page.
• Separate consent for updates. The mailing list is a separate, unticked, optional choice. Submitting an enquiry never subscribes you to anything.
• Stated retention. Enquiries kept for a defined period and then deleted, with the period published here rather than decided case by case.
• Your rights. Access, correction, deletion, restriction, objection and portability, with a named route for exercising them and a supervisory authority to complain to.
• Processors named. Whoever handles the form, the mailbox and the mailing list will be listed, with the data-processing agreements in place.

Data in the research work, as distinct from this website

This note covers the website. The research operation is a separate question, and it is not live: no monitoring is running and no records exist. The commitments that will govern it — minimisation, retention limits, role-based access, audit logging, and a data protection impact assessment before any operational deployment in the EU — are set out on principles and are described there as planned, because that is what they are.

Civic Shield does not and will not build profiles of individuals, publish names, or hold private communications. That is a design commitment, not a privacy-policy formality.