Campaign groups can host a petition on their own domain. The form records name, email, and optional organisation so the list is not locked inside a petition SaaS if the vendor changes terms.
Notify the campaign lead.
The HTML fields do not contain the petition text—your page does.
Count only vs names vs comments.
CSV to the decision-maker, plus your own backup.
A petition form is a public list of people who endorse a specific ask: change a policy, save a building, fund a service. US advocacy orgs and UK local campaigns both need a statement above the form and a signature record they can export. It is not a statutory UK Parliament petition and not a ballot.
The signup pack fits: identity, email for updates, and an interest field you can ignore or relabel to ‘keep me posted vs signature only’. The legal force of an online signature is political, not magically binding on a legislature.
Name and a contact method beat 10,000 fake rows. You will be asked how you verified this.
Do not scrape these emails for a commercial list. US and UK campaign-finance and privacy rules can both bite.
Change.org, 38 Degrees, and paper in the high street all have a place. Self-hosted HTML is for ownership.
You own the CSV. You write the privacy sentence.
Reach vs lock-in. Use them for amplification; export if they allow.
Still better for some high streets. Transcribe into the same dashboard if you can.
Use the government site when you need that process. This form is not that.
A one-page Netlify site with the ask, the form, and a privacy line is a complete petition.
If you publish names, say so before they submit. If you only send to a councillor, say that instead.
It is a recorded endorsement. It is not a notarised wet signature. Check local rules if you need something stronger.
Those must be created on petition.parliament.uk. This page is for your own campaign.
Dedupe by email in the dashboard before you quote a number.
Follow your country’s rules. Many campaigns set 16+ or 18+ in the copy.