Docs

reCAPTCHA and spam protection

Keep spam out without losing real enquiries. When FormHam is unsure, it holds the submission for you to review instead of deleting it.

The four modes

Choose one on the form's Security tab. Whichever you pick, the honeypot, domain locking and rate limits still apply.

ModeHow it works
Built-in check (default)The embed script solves a small proof-of-work puzzle in the visitor's browser and notes whether they actually interacted with the form. The server combines that with other signals into a score. No Google, no cookies, nothing to configure.
Google reCAPTCHAThe submission carries a reCAPTCHA token, which we verify with Google.
BothreCAPTCHA decides. The built-in check runs alongside and only records what it would have said, so you can compare before switching.
OffNo spam scoring.

Platform keys or your own

Platform keys. By default a reCAPTCHA form uses FormHam's own reCAPTCHA Enterprise key. Google only accepts a token from a domain registered on that key, so your site's domain has to be approved on it first — ask us before switching a form to reCAPTCHA, or its submissions will be held.

Your own keys. If you already have reCAPTCHA keys from Google, enter the site key and secret key on the form (or once for your whole account) and they are used instead. Your secret key is stored encrypted and never shown again.

v2 and v3

  • v3 is invisible and returns a score from 0.0 (likely a bot) to 1.0 (likely a person). This is what the embed script uses.
  • v2, the checkbox, is accepted if you render the widget yourself and post the g-recaptcha-response field. The embed script does not drive v2.

A v3 token scoring below the threshold is refused. The threshold is set for the whole platform: 0.3 for your own v3 keys and 0.5 for the platform Enterprise key. Tokens older than ten minutes are not accepted as proof.

Quarantine: held, not deleted

A submission is held for review rather than refused when the evidence is not good enough either way. It is stored in full, nothing is sent, and you are alerted. That happens when:

  • reCAPTCHA could not be checked — no token arrived, or Google could not be reached — but the browser says the submission came from your own domain;
  • the built-in check's score is suspicious but not conclusive;
  • the submission came from a domain not on your allowed list;
  • the name field contains a link;
  • a platform-key token was issued for a different action than a form submission.

Some failures are clearly the visitor's environment, not a bot — a reCAPTCHA token that expired because the page was left open, or a browser error inside reCAPTCHA. Those are let through and delivered, up to a limit per visitor so the exception cannot be abused. Holding is capped too: past 20 held submissions in ten minutes from one address to one form, further ones are refused.

Review held submissions in the dashboard. Release moves one into your normal list; Release and notify also sends every notification and webhook it would have triggered. Held submissions nobody opens are removed after 30 days.

Cookies on your site

The built-in check sets no cookies. Google reCAPTCHA runs Google's script on your page, which may set its own cookies and collect information about the visitor's browser — make sure your cookie notice and privacy policy cover it if you use it.