Privacy

Who is responsible for what

The organisation running a canvass decides what to ask at a door, who to ask, and what to do with the answers. In data-protection words, it is the controller. Knockna Limited Liability Company — the Arizona company that operates DoorPoll — is the processor: we hold the data and act on that organisation’s instructions.

That split has a practical edge. If you answered a door and want your details removed, the campaign that knocked is the fastest route, and you can also write to us and we will pass it on and follow it up. If you run a campaign, obtaining consent at the door and answering requests about it is your obligation — as the terms say — and the product is built to make it possible, not to discharge it for you.

What is collected

From somebody who answers a door

• Contact details, only if you give them. First name, last name, email, phone — whichever of those the campaign’s questionnaire asks for. Every field can be left blank, and where the campaign has set consent wording, the tick is required before anything is recorded at all.
• The answers given. Whatever the questionnaire asked — support, issues raised, whether a follow-up was wanted — attached to the address rather than to a named person unless contact details were given.
• The address and the outcome. The door, the unit, when it was visited, and what happened: answered, nobody home, come back later.

From the people using DoorPoll

• The account itself. Email address, display name, the workspace and role, and sign-in times.
• Where the canvasser was standing. When a visit is recorded, the device’s own position is stamped on it. This is the canvasser’s location, not the resident’s: it is how an organiser tells a door knocked from the doorstep from one filled in from a parked car. If the canvasser declines the location permission, nothing is stamped and the visit saves anyway.

From the campaign’s own files

Address lists, boundary layers and past visit records that a workspace imports. These arrive from you already assembled; having the right to use them is your side of the bargain.

Who else touches it

Four suppliers, named rather than described:

• Supabase — the database and the sign-in system. This is where the data actually sits.
• Vercel — runs the application, and counts page views. Those counts are aggregate: no cookie, and no following anyone between sites.
• Resend — sends the product’s email. An address reaches it only when a message is actually being sent to that address.
• OpenFreeMap and OpenStreetMap — the map backdrop. Map tiles are pieces of a street map: your addresses are drawn on top of them in your browser and are never sent to the tile servers.

Which region a workspace’s database sits in is fixed when it is created. Ask before you import anything and we will tell you in writing which one yours is, and confirm it in a data-processing agreement if your organisation needs one.

What we never do

• Sell, rent or share the data with anyone not listed above.
• Use it to train machine-learning models.
• Let one workspace see another’s. Separation is enforced by the database itself, not by remembering to filter a query.
• Market anything to somebody whose details a canvasser recorded. They gave them to a campaign, not to us.

How long it is kept

For as long as the workspace exists. A campaign is a season, not forever: when yours is over, ask us to delete the workspace and we will, along with its visits, contacts and imported files. Export what you want to keep first — responses come out as CSV from the product at any time, without asking us.

Getting a copy, a correction, or a deletion

Anyone whose details are in a workspace can ask for a copy of them, ask for them to be corrected, or ask for them to be removed. Write to the campaign that knocked, or to us and we will route it. We answer within thirty days, and there is no fee.

Every email the product sends to somebody who is not a user carries an unsubscribe link that works on its own — no sign-in, no form, one button — and it keeps working long after the message that carried it.

Cookies, and what they are for

One kind: the cookie that keeps you signed in. There is no advertising cookie and no third-party tracker on this site. Canvassers’ phones also store queued visits locally so a door recorded with no signal is not lost — that stays on the device until it syncs.

Changes to this page

When what we collect changes, this page changes in the same release and the date under the heading moves. If a change affects data already collected, we write to the workspace owners rather than rely on you noticing a date.

Asking us

Write to stanley@serenialabs.space. It reaches Knockna Limited Liability Company, the Arizona company that operates DoorPoll, and a person rather than a queue.