Privacy

There is no tracking on this site

Worth saying first because it removes most of what a privacy policy usually has to explain. Votense carries:

• no analytics of any kind — no Google Analytics, no alternatives
• no advertising, and no advertising identifiers
• no third-party trackers, pixels or social embeds
• no cross-site profiling, and nothing sold or shared for marketing

There is no cookie banner because there is nothing to consent to. The only cookie we set is the one that keeps you signed in.

If you build surveys

Your account

You sign in with Google or GitHub. We receive your email address, your display name and a user ID from whichever you chose. We never see your password for either service.

Your surveys

The questions you write, your field IDs, your settings and your appearance choices are stored so the survey can be served and edited. Your survey password, if you set one, is stored only as a salted scrypt hash — it cannot be read back, by you or by us, and it is never returned by any part of the API.

What we store, and why

Cookies and local storage

One cookie, access_token, holds your sign-in token so the API knows it is you. It is SameSite=Lax, short-lived, and cleared when you sign out. Your browser also remembers two preferences locally — your light or dark choice, and whether the editor's field panel is open. Those never leave your device. If you vote in a poll, your browser also keeps a random voter identifier and a note of which polls you have voted in; see “If a poll or survey limits voting” below for what is sent and when.

If you are filling in a survey

You do not need an account and we do not create one for you. Your answers belong to the person who built the survey; they can read, export and delete them, and they chose any other destination the answers are sent to.

What is recorded with your answers

• the answers themselves, and when you submitted them
• your email address and name, but only if that survey asks for them
• your browser's user agent, the referring page, and the page you submitted from — the same request details any website receives

If the survey has a file field, the file you choose is stored as part of your response, up to 200 KB.

Please do not send passwords or payment details

A Votense survey is not the right place for credentials, card numbers or government identifiers, and no legitimate organisation should ask for them this way. If a survey does, do not fill it in — see the terms, which forbid it.

Who else sees any of this

A small number of providers, each doing one job, and none of them receiving anything for their own purposes:

Beyond those, responses go wherever the survey's owner has told them to: their own webhook endpoint, a Telegram chat, a Slack, Discord, Microsoft Teams or Google Chat message, an Airtable record, a Notion page, or an email to an address they chose. Those destinations are the owner's choice and the owner's responsibility — once a response reaches one, that service's privacy policy governs it, not ours. Each guide says exactly what is sent to that destination; webhooks is the one to read first, because it shows the raw shape.

If a poll or survey limits voting

An owner can limit a poll or survey to one vote per browser, per network or per signed-in account. To enforce that, we store a ballot record alongside — but separately from — the answers.

• The record holds a one-way hash of the browser identifier, the IP address or the account id, whichever the rule uses, combined with that survey's id. The same person therefore has a different hash on every survey, and the hash cannot be turned back into the identifier.
• It records that a vote was cast and when. It does not contain the answer, and the stored answer does not contain the hash.
• Ballot records are deleted automatically after 180 days, and immediately when the owner deletes the survey.

For “one per browser”, a random identifier is kept in your browser's local storage so the same browser can be recognised. It is sent only when you submit a vote or open a results page, and is not used for anything else.

A public results page shows totals, percentages and scores. It never shows who answered, and never shows written answers.

Cloudflare Turnstile: bot protection

Every public survey is checked by Cloudflare Turnstile before a submission is stored. We operate votense.com and the embed frame the widget runs inside, so we are the one place this can be disclosed — the widget itself carries no privacy notice of its own, and on the invisible option it shows the respondent nothing at all: no checkbox, no Cloudflare branding, no terms.

To run that check, Turnstile processes:

• the respondent's IP address
• a TLS fingerprint and their browser's User-Agent
• the sitekey the widget was issued under, together with the origin it ran on

It sets no tracking cookies and is not used for advertising. Cloudflare's own Turnstile Privacy Policy covers exactly this processing.

If you embed a Votense survey on your own site, your visitors go through this same check on your page. That is processing we do not control your disclosure of — you may need to say so in your own privacy policy, particularly if the survey you embed uses the invisible option. See spam protection for what each option means for your respondents.

Deleting things

Deleting a survey deletes its responses. That is deliberate: answers should not outlive the survey that collected them. It cannot be undone, so export first if you need them.

If you responded to someone's survey and want your answer removed, ask the person who runs that survey — they can delete it directly and they are the ones who decided to collect it. If you cannot reach them, write to us and we will help.

To delete your own account and everything in it, or to ask what is held about you, email privacy@seagit.com.

Changes to this policy

If this policy changes in a way that affects what we collect or who sees it, the date at the top changes with it. We will not quietly broaden what we do with data you have already given us.