Skip to content
LEGAL

Privacy policy

What Formkit collects, how long it is kept, who can see it, and how to get rid of it. Your account is ours to look after; the answers in your forms are yours.

Last updated 17 October 2026

What this covers

Formkit is a form builder. You write questions, share a link, and the answers come back to you. This policy explains what we do with two different sets of data: the information about you as a Formkit user, and the answers your respondents send through your forms.

The two are treated differently, and the difference matters. Your account is ours to look after. The answers in your forms are yours. We hold them on your behalf and do not use them for anything of our own.

What we collect

Four things, and nothing else:

Your account. A name, an email address, how you sign in (a hashed password, a passkey's public key, or your Google account if you sign in with Google), and a company name if you choose to add one. A company is optional and most people never add one.
Your forms and their answers. Questions, themes, settings, every response, and any file somebody uploads (up to 20 MB per file on Free, more on paid plans).
Technical records. Sign-in times, the pages you opened in the app, the browser and rough location (city level) a request came from, and errors. We keep these to work out what broke and to spot someone attacking the service.
What you set up and send us. If you turn on push notifications, the address your browser gives us to reach that device. If you connect a service such as Google Sheets or Notion, the token it issues, stored encrypted. If you write to support, even without an account, your name, email address and message.

What we do with it

We use your account data to sign you in, send the notifications you asked for, and answer you when you contact support. We use the technical records to keep the service up and to investigate abuse.

We do not sell anything to anyone. We do not run advertising, we do not build profiles of your respondents, and we do not train anything on your responses.

The answers belong to you

When somebody fills in your form, you decide what was asked and what happens next; we store it and show it back to you. In data-protection language you are the controller and we are the processor.

That means two practical things. If a respondent asks us to delete their answer, we will point them to you, because it is your record to delete. And if you ask for something sensitive, it is on you to have a reason and to say so on the form.

Who else touches it

A small number of companies handle data for us because they run the machines: Convex and Vercel host Formkit, Resend delivers its email, Polar handles billing for paid plans, Google's Gemini models power the AI features, Cloudflare runs the spam check on forms that have it on (see Cookies), and Sentry receives reports of errors anywhere on Formkit, published forms included (what went wrong, without answers or account details). They are bound to use it only to provide that service. If you allow it on our public pages, Google Analytics also receives visit data from those pages (see Cookies).

AI features send Google only what they need. Ask Formkit sends your prompt and the form you are working on, and, when you ask it to read responses, counts and written answers without names, email addresses or phone numbers. If you turn on AI replies, AI logic or AI insights for a form, each response to it is sent as it arrives, so the reply, decision or summary can be written. If you ask for a voice question's recordings to be written out, each recording is sent once, to be transcribed. If you turn on search by meaning for a form, each response's answers, without names, email addresses or phone numbers, are sent once to be indexed. Google may not use any of it to train its models.

Apps you connect, such as an AI assistant you allow to use your Formkit, can read and change what you let them on the consent screen, and nothing else. What they do with it is between you and them. You can disconnect any of them in Settings → Developers.

Services you connect to a form, such as Slack, Google Sheets, Notion, Airtable, HubSpot or your own Stripe account, receive the responses you send them, and what they do with them is between you and them. The keys and sign-in tokens Formkit keeps for them are stored encrypted.

If you turn on push notifications, each one reaches your device through your browser's push service (run by Apple, Google, Microsoft or Mozilla). It is encrypted on the way, so that service cannot read it.

Formkit staff can reach your account for support: to answer a ticket, look into a report, or investigate abuse. When they do, it is logged, and a support view is read-only: staff can see what you see and change nothing.

How long we keep it

Responses stay until you delete them. Deleting a form moves it to Deleted, where it sits for 60 days before it goes for good.
Close your account and everything (forms, responses, uploads) is removed within 30 days. Backups age out within 90.
Technical records are kept for 12 months, then deleted.

What you can do about it

At any time, without asking us:

Export every response as CSV, Excel, JSON or PDF.
Delete a response, a form, or your whole account, from Settings.
Turn off any email we send you, including the weekly report.
Correct anything about you that is wrong, in Settings → Account.

Cookies

Inside the app, Formkit sets a few cookies of its own: two keep you signed in, one remembers your time zone so dates show in your local time, and signing in with Google sets a short-lived one for that step.

Your published forms set no cookies. To stop duplicate and automated submissions, a form keeps a random device code in the respondent's browser storage. It identifies a browser, not a person, and it is never shared or used for advertising. On Pro, a form also records where each response came from (the link, a QR code or the referring site) and what kind of device sent it, for the form's own analytics.

When a form's spam protection is on, Cloudflare Turnstile checks that a person, not a script, is sending it. Cloudflare sees the respondent's browser and connection for that check only, and does not use it for advertising.

On our public pages (the homepage, templates, help and the rest of formkit.app outside the app), we use Google Analytics to count visits and see which pages people find useful, but only if you say yes. Until you do, it is not loaded at all: no script, no cookie, nothing sent to Google. If you accept, it sets a few cookies whose names begin with _ga, which last up to two years. Google's advertising features are switched off.

Your answer is remembered in your browser, not in a cookie. To change it, use Cookie settings at the foot of any public page; withdrawing removes the Google Analytics cookies.

Where the data lives

On servers in the United States and the European Union. If you are somewhere else, your data crosses a border to reach us, under the standard contractual clauses our providers sign.

Children

Formkit is not for people under 16. If you run a form aimed at children, that is your responsibility and you need the right consent to do it.

Changes, and how to reach us

If we change anything that affects you, we will tell you in the app and by email before it takes effect. Not quietly, and not after the fact.

Questions, requests and complaints go to privacy@formkit.app. We answer within five working days.

If you want a copy of everything we hold about you, ask at privacy@formkit.app and we will send it as a single file.