Privacy kit
Formsieve sends form content to Formsieve's check service, run by Thinking42, Inc., which uses an outside AI model. So it comes with the tools you need to do that carefully: consent before anything is sent, data minimisation, a visitor-facing notice, privacy-policy text, a Data Processing Agreement, personal-data export and erasure, and log retention. As the site owner you remain the controller of your visitors' data; Formsieve does not make a site compliant with any law by itself. Where the data goes: Data processing.
Consent before anything is sent
Nothing leaves your site until an administrator has entered a Formsieve key and completed the consent step of the set-up wizard. The consent screen names every recipient, in order, with its country and role: Thinking42, Inc. (USA, your processor), then its sub-processors Cloudflare, Inc., Amazon Web Services, Inc., OpenRouter, Inc. and TypeSafe AI, Inc. (all USA), with links to the Formsieve Terms, Privacy Policy and Data Processing Agreement, to each sub-processor's privacy policy, and to OpenRouter's and TypeSafe's terms. It shows what is sent and what is never sent, that submission content is not stored and request records are deleted after 30 days, that Thinking42 processes the data in the USA and its sub-processors are US companies (Cloudflare runs a global network, and OpenRouter does not promise to handle a request only in the USA), and that transfers from the EU and the UK rely on the standard contractual clauses and the UK Addendum in the Data Processing Agreement.
Two boxes are required:
- "I agree to the Formsieve Terms of Service and the Data Processing Agreement.", with links to both;
- "I agree that form submissions are sent to the companies above as described, and I will mention this in my privacy policy."
The record stores a hash of the recipients, the consent version, the time and the administrator. Version 1.1.0 uses a new consent version, so a consent given in version 1.0 for your own AI provider does not carry over: you are asked again.
- Withdraw consent on the plugin's Privacy tab at any time: AI checks stop immediately and submissions are delivered after the local filters only.
- Test mode needs no consent record, because it sends nothing. Test connection sends one canned sample (not a real submission), only when you click it and only after consent.
The Data Processing Agreement
When your forms collect personal data, the law in many places (for example Art. 28 GDPR) requires a contract with any processor. The Formsieve Data Processing Agreement (https://formsieve.com/dpa/) is that contract. You accept it with the first box above, or when you subscribe. It covers the processing instructions, security, sub-processors (with 30 days' notice of changes), breach notice, deletion, audits, the EU standard contractual clauses (Module 2, and Module 3 when you are an agency acting for a client), the UK Addendum, and US state privacy terms. Your account's Data and privacy page keeps your acceptance record and a PDF copy.
Data minimisation
- Only the domain of the sender's e-mail address is sent (switch off Email domain under Settings → Privacy to send none).
- Phone numbers are redacted in field values by default (Phone numbers under Settings → Privacy).
- No IP address or user agent is ever sent. IPs are hashed on your server for the rate limit and never leave it. On a Gravity Forms form set not to store IP addresses (Personal Data settings), Formsieve does not use the IP at all. When a form uses Contact Form 7's
do_not_storesetting, or the visitor leaves aconsent_for:storagebox unticked, Formsieve's log keeps the verdict but no IP or e-mail hash. - Passwords, payment and card fields, uploads, hidden fields, consent and CAPTCHA fields are never sent.
- Sensitive fields are excluded automatically: fields whose label, name or type suggests health or medical data, national ID or social security numbers, passports, driving licences, bank or card numbers, or secrets. Forms that look medical or legal show a warning on the settings screen so you can review them.
- Exclude any other field per form (Per-form settings for Gravity Forms, Per-form settings for Contact Form 7).
- HTML is removed and every value is capped (2,000 characters per field, 4,000 for the message, about 12 KB in total).
Notice to visitors
AI notice under forms (Settings → Privacy) adds "Submissions are screened for spam by an automated AI service." under the form. Automatic (the default) turns it on when a Formsieve key is connected. The Formsieve Terms ask you to tell people who submit your forms about the screening, and this line does that where they will see it. Choose Always show or Never show to override it globally, or Show / Hide in a form's own Formsieve settings. If you hide it, tell visitors another way, for example in your privacy policy.
Privacy-policy text
Formsieve adds suggested text to WordPress's Settings → Privacy → Policy Guide, generated from your privacy settings. With the default settings and a Formsieve key, version 1.1.3 suggests (the plugin's version is the one to copy):
When you submit a form on this site, the text you type into the form (with its field labels), the domain part of your email address (not the full address), the host names of links in that text and a few signals, such as how long the form took to fill in, how many links the message contains, how many submissions came from your IP address in the last hour (a count, not the address) and whether your email address is on this site's list of trusted or blocked senders, are sent to an automated AI service that estimates whether the submission is spam. This site's name and languages, the form's name and the descriptions we write for the site and the form are sent with them. Your IP address, your full email address and your browser details are not sent. Fields that look like passwords, payment or bank details, identity numbers or health information are left out automatically. Phone numbers are replaced with a placeholder before sending.
They are sent to Formsieve, a spam-filtering service of Thinking42, Inc. (USA; privacy policy: https://formsieve.com/privacy-policy/). Thinking42 checks them with an AI model of TypeSafe AI, Inc. (USA), reached through OpenRouter, Inc. (USA); its service is hosted by Amazon Web Services, Inc. and Cloudflare, Inc. (USA). The full list of sub-processors is at https://formsieve.com/subprocessors/.
Thinking42 processes this data for us under a data processing agreement. It does not store the content of your submission and deletes its request records (such as the time, status, timing and the spam band of the result, without the content) after 30 days. OpenRouter and TypeSafe state that they do not train AI models on it. The data is processed by US companies; transfers from the European Union and the United Kingdom rely on the European Commission's standard contractual clauses and the UK Addendum.
We rely on our legitimate interest in keeping this site free of spam.
The service returns a spam probability. It is used only to decide whether your submission is delivered normally, marked for review or treated as spam, and a site administrator can correct that decision.
This site keeps a record of each check (the decision, the spam probability and the time) together with a keyed hash of your email address and IP address, so that the record can be found and deleted on request. Your message is not stored in this record. The record is deleted automatically after 90 days. If a site administrator marks your submission as spam or not spam, a keyed hash of your email address is also kept on a list of trusted or blocked senders, with no time limit, until it is erased at your request or the site owner removes the plugin's data.
The text changes with your settings: without the e-mail domain it leaves that part out, with phone redaction off it no longer says that phone numbers are replaced, and it states how long your site keeps Formsieve's decision log (never the message). Copy it into your privacy policy and adapt it with your own advisers.
Versions before 1.1.3: their text and consent screen said that the data is processed in the United States and named fewer of the details kept in the request records; their text also named fewer of the signals each check sends, and not the UK Addendum. Thinking42 and every company it uses are US companies, and Thinking42 processes the data in the United States, but Cloudflare runs a global network, and OpenRouter does not promise to handle a request only in the USA (Data processing). In version 1.1.3 the consent screen says so, and the suggested text says that the data is processed by US companies. If you copied the earlier text into your privacy policy, copy it again from the plugin.
Legitimate interest
Most sites screen submissions on the basis of a legitimate interest (Art. 6(1)(f) GDPR): keeping the site and its inbox free of spam, phishing and abuse. If you rely on it, note your balancing test in your records. Points in its favour: only what the visitor typed into the form is checked, with the e-mail reduced to its domain and no IP address; Formsieve's service stores no submission content; the result is used only to route the message; uncertain messages are delivered with a tag or held for a person rather than discarded; and visitors are told under the form. Your own advisers decide whether this fits your site.
Forms with sensitive data
Formsieve is not for forms that collect health information (including information covered by HIPAA), payment-card or bank details, passwords, government ID numbers or documents, or information about children; the Formsieve Terms and Acceptable Use Policy do not allow it. The plugin excludes fields that look sensitive and warns on forms that look medical or legal (see Data minimisation), but you remain responsible: exclude such fields per form, or switch Formsieve off for that form.
Export and erasure
Formsieve registers with WordPress's personal-data tools (Tools → Export Personal Data and Tools → Erase Personal Data), matching by e-mail address through its hash:
- Export lists each Formsieve decision linked to the address (date, form, entry reference, verdict, probability, category, deciding stage, reason code, route and any correction) and whether the address is on a learned list.
- Erasure deletes those log rows and removes the address from the learned trusted and blocked lists.
Matching uses a hash keyed with your site's authentication salt. Rows logged before a salt change can no longer be matched to an address; they hold no readable address and are deleted by the retention task (Troubleshooting).
The submission itself is stored by Gravity Forms as an entry, or by Flamingo as a message, and is exported and erased by that plugin's own tools.
Retention
The decision log holds numbers and identifiers only, never what the visitor typed. A daily task deletes rows older than the retention period (Keep decision log for under Settings → Privacy): 30 days, 90 days (default), 1 year, or keep until deleted. The replay cache keeps hashed verdicts for 7 days (only while Replay cache is on), rate-limit counters (only while Rate limit is on) expire after their window, and the counter of the per-form hourly cap (only while it is set) expires after two hours. The learned trusted and blocked senders (e-mail hashes) are not subject to the retention period: they stay until an erasure request for that address, or until the plugin is deleted with Uninstall on.
Uninstall
Deactivating Formsieve deletes nothing. Deleting the plugin always removes its scheduled daily task, and removes its data (settings, key, consent, learned lists, log table and transients, plus the Formsieve details stored on Gravity Forms entries, and the Formsieve form settings and details stored on Contact Form 7 forms and Flamingo messages) only when Settings → Advanced → Uninstall ("Delete all Formsieve data when the plugin is deleted") is on (off by default), so a reinstall keeps your setup.