Skip to content

Run your workspace

Spam, privacy and security

Formpik keeps spam out of your inbox without adding friction for real visitors, and keeps what people send you private.

On this page you will learn

  • Every layer of spam protection, and how to turn each one on
  • The limits that protect your endpoint
  • What Formpik stores about visitors, and what it leaves out
  • How sign-in, sessions and API keys are protected
  • Who in your team can see webhook addresses and secrets
  • What happens when you delete data

Spam protection

Spam is stopped in layers. The first two work at the endpoint, before any flow runs. The third works inside a flow.

  1. 01Endpoint checksAllowed websites, pauses, rate limits and repeats refuse a request.
  2. 02Spam trap and bot checkStored as spam with the reason. No flows run.
  3. 03Validate stepThrowaway emails and link-heavy messages take the failed path.
LayerHow it worksWhere you set it
Spam trapA hidden _gotcha input. People never see it, bots fill it in. Those submissions are stored as spam and no flows run. The HTML snippets in the Connect tab include it.Spam trap field in the form's settings, on by default.
Bot checkAdd a Cloudflare Turnstile or Google reCAPTCHA widget to your form. Formpik checks the token it adds (cf-turnstile-response or g-recaptcha-response), and a missing or failed check is stored as spam.Bot check in the form's settings, off by default.
Spam filterInside a Validate step: the spam trap, throwaway email domains in email fields, and long text answers with more than three links. A hit marks the submission as spam and takes the step's failed path.The Validate step of a flow.
Allowed websitesOnly the websites you list, and their subdomains, can post from a browser or show the form’s embed. With an empty list, any website can. The form’s own share link always works.Allowed websites in the form's settings.
Rate limitsAt most 120 submissions a minute from one address, and an hourly limit per visitor on each form (30 by default).Limit per visitor in the form's settings.
RepeatsThe same answers from the same source within 10 seconds are stored once. An Idempotency-Key header makes retries safe for 24 hours.Always on.

Allowed websites are read from the Origin or Referer header a browser sends. Requests from a server or a terminal usually send neither, so they are not checked against the list. That is why the bot check and the spam trap matter even with a list in place.

Example: a form that gets spam

A marketing agency's contact form starts getting a few bot submissions a day. Here is the order to tighten it, from least to most friction for real visitors:

  1. 01

    Check the spam trap

    Make sure the hidden _gotcha input is on the page and stays empty and hidden. Copy it from the HTML snippet in the Connect tab if it is missing.
  2. 02

    List the allowed websites

    Add the agency's own domain under Allowed websites, so browsers on other sites cannot post to the form.
  3. 03

    Filter in the flow

    Put a Validate step with the spam filter at the start of each flow, so throwaway addresses and link-stuffed messages never reach the team.
  4. 04

    Add a bot check

    If spam still gets through, add a Turnstile or reCAPTCHA widget to the form and choose it under Bot check.

What happens to spam

  • Spam is stored, never dropped. It shows under Spam or invalid in the inbox, with the reasons it was held.
  • No flows run for spam, so nothing is emailed, posted or sent to a webhook.
  • Choose Not spam to release a submission caught by mistake. Its flows run right away.
  • Spam the endpoint stores counts toward the monthly submissions of your plan, like any submission that arrives through a source.

Privacy

  • IP addresses are anonymized by default: only the network part is kept, such as 203.0.113.0, or the first three groups of an IPv6 address. Turn Anonymize IP addresses off in Settings if you need full addresses.
  • For the hourly limit per visitor, Formpik keeps a one-way hash of the address that only works inside your workspace, so the limit works while addresses stay anonymized.
  • Besides the answers, a submission keeps the page it was sent from, the browser, the country and the IP address as set above.
  • Uploaded files are stored privately. They have no public address and open through a link that works for 15 minutes, for people in your workspace only.
  • Submissions and their files are deleted after the retention time of their form.
  • Emails Formpik sends can be tracked for opens and clicks, so mention it in your privacy policy. Mention the use of AI too, when your flows ask AI to read submissions.

Sign-in and sessions

  • There are no passwords. Formpik emails a sign-in link and a 6-digit code that work once and for 15 minutes.
  • A code stops working after 5 wrong tries. Sign-in emails are limited per address and per network, so nobody can flood an inbox with them.
  • New accounts, new sign-in emails and invitations cannot use an address with a + in it (name+tag@company.com) or a temporary mailbox. The list of temporary mailbox domains is updated every day. Accounts that already use such an address keep working.
  • Your session is kept in an HTTP-only, secure cookie for 30 days and renews while you use the app.
  • On your account page, Sign out everywhere else ends every other session at once.
  • Sign-in links, codes, invitation links, session ids and API keys are only ever stored as hashes.
  • Links in sign-in and invitation emails are left out of click tracking.

Access inside your team

  • Every change in the dashboard is checked against your role on the server, whatever the browser shows.
  • Webhook addresses and signing secrets are shown in full only to roles with the Webhook secrets permission, which owners and admins have. Everyone else sees a masked address, and saving a destination with the masked address keeps the real one.
  • API keys are created and revoked by admins and owners. A key is shown once, and Formpik keeps only a hash of it.
  • Changes to your workspace are only accepted as JSON from the app, which protects against requests forged by other websites.

Delivery safety

  • Webhooks and chat messages only go to public https addresses, never to private networks.
  • Each delivery waits at most 10 seconds for an answer.
  • Webhooks are signed with a secret per destination in the X-Formpik-Signature header, so your server can check they came from Formpik. See Webhooks.
  • Auto-replies go to one address only, leave out long free text answers, and send at most 3 emails a day to an address a visitor typed, so a form cannot be used to send spam to others.

Deleting data

You deleteWhat is removedWho can do it
A submissionIts answers, runs and files.Editors and up
A formIts sources and its stored submissions. Flows that use it are paused.Editors and up
A workspaceEverything in it, including files and the team. A paid plan is canceled first. Confirmed by typing the workspace name.The owner
Your accountYour sign-in, your memberships, and workspaces where you are the only member. Confirmed by typing your email.You

Questions

Is the source key a secret?
No. It sits in your page's HTML, like an address. Protect a form with allowed websites, the spam trap and a bot check, and use an API key only from your own server.
Will the bot check slow down real visitors?
Turnstile and reCAPTCHA usually run without a puzzle. If you would rather not add one, the spam trap alone works well for most sites.
Can I see the full IP address of a visitor?
Only if Anonymize IP addresses is off when the submission arrives. Submissions stored while it was on keep only the network part.
Who can open uploaded files?
Anyone signed in to your workspace, through a link that works for 15 minutes. Files have no public address.

Next steps