Legal
Privacy policy
Version 1.2.1 · Effective 2026-10-14 · Earlier versions: /terms/versions/
Formsieve is a service of Thinking42, Inc., a Delaware corporation, 1480 NW North River Dr, Apt 2318, Miami, FL 33125, USA ("Thinking42", "we"). For the personal data described in §3, Thinking42 is the controller. Contact: support@formsieve.com.
This policy covers the data we handle for our own purposes: when you visit formsieve.com, use the AI chat on our website or ask a person through it, create an account, start a trial, use the Free plan, subscribe, use your key, or write to us.
It does not cover the form submissions that the Formsieve plugin sends to our spam-check service from our customers' websites. For those we are the website owner's processor: the website owner decides, and its own privacy policy applies. Our Data Processing Agreement (/dpa/) governs that processing. §11 summarises it.
| Data | Where it comes from |
|---|---|
| Account: e-mail address; optional name and company | You, when you start a trial, subscribe or sign in |
| Sign-in: one-time codes, a short-lived cookie while you sign in, and the IP address and browser of each signed-in session, which WordPress keeps with your account | Generated by us; the IP address and browser come from your browser |
| Anti-bot check: on the forms that e-mail you a sign-in code (starting a trial, signing in, subscribing) and on the AI chat (on each page, when you first go into the chat's text box or its "Ask a person" form, which with a mouse happens as soon as you open them, and again when our server asks for a new check, after 30 minutes or from another network), Cloudflare Turnstile checks that the request comes from a person; Cloudflare receives your IP address and browser details for that check | Your browser, through Cloudflare |
| Billing: name and billing address, optional business tax ID and its validation result, subscription and invoice details, the brand, last four digits and expiry date of your card | You, through Stripe's checkout; Stripe gives us these details. We never see or store your full card number |
| Consent records: the text you agreed to (Terms, DPA, automatic renewal and, for consumers in the EU, the EEA and the UK, the immediate start), its version, the plan and price shown, the time, your IP address, your country and your browser. On our public cancel and withdraw pages, also the e-mail address, name and key or invoice number typed into the form, even if they match no account. For a trial, a hash of your e-mail address (not the address), so that each address gets one trial | Our start, subscribe, cancel and withdraw pages, and your account |
| Key and service data: your Formsieve key (we also keep a one-way hash of it), plan and status, the sites that use your key (site address, WordPress environment type, form plugin, plugin version, first and last seen, and whether the site has used a trial or a free allowance), AI checks per day and month, and the amount of text processed per month (counted, never stored) | The plugin and our service |
| Request records: for each request to our spam-check service (a check, a test, or a key or usage query), the time, a request ID, key and site identifiers, plugin and version, status, latency, the model version and cost reported by our AI provider, the spam band of the result, and technical details of the call: which endpoint and question set, the form plugin, the number of input tokens, how long the AI provider took, whether the answer was a replay of an earlier one, and the AI gateway's reference for the call. When one key's requests are refused more than 20 times in a minute, we may only count the further refusals of that minute. Never the content of the submission | Our service |
| Plugin updates: when a copy of the plugin downloaded from formsieve.com checks for updates, it sends your key, the plugin version and the site's address to updates.formsieve.com. We keep a log of each check and download: the time, the plugin and version, the site's host name, the first 8 characters of a hash of your key, the result, and a hash of the network the request came from (its IP address shortened to a /24 or /48 range), made with a key we replace every day | The plugin, through our update service |
| Support: what you write to us and our replies, by e-mail or in the plugin's public support forum on WordPress.org | You |
| AI chat: the questions you type into the chat on our home, product, pricing and start pages (at most 600 characters each; a Formsieve key in them is hidden except its last four characters before it leaves your browser), and the chat's answers. Your browser sends each question with the earlier messages of the conversation; we pass the question and up to six earlier messages, with text from our published pages, to the AI model (§6) and send back the answer. We do not keep the conversation on our server: it stays in your browser tab (§5). While our server handles a question or "Ask a person", a long conversation can pass through temporary files on its encrypted disk. They are deleted when the request ends, but deleting a file does not erase its bytes from this disk: they can stay in the disk's free space until they are overwritten, and in the snapshots of the disk made before then (§8). Our server keeps only daily totals (numbers only, such as how many answers and errors there were, the tokens used and the cost), and, for the limits on how many questions one network or one conversation can ask, short-lived counters named by a keyed hash of your network (your IP address, or its /64 range for IPv6) and of a random conversation ID. If you use "Ask a person": your e-mail address, your name if you give it, your note, the conversation in your tab and the page you were on. Before we e-mail it to our support address, we check what you typed (your name, your note and your own questions, not the AI's answers) and the domain of your e-mail address with Formsieve's own spam check (§6); the result only labels the e-mail for us | You, through the chat; the answers come from the AI model |
| Website and security: IP address, browser and request details in web-server and security logs; aggregated, cookieless visit statistics | Your browser, through our hosting and Cloudflare |
Ad click identifier: if you reach formsieve.com by clicking one of our ads on Google, Google adds an identifier for that click to the web address (for example gclid=…). If you then start a trial or buy a plan, we keep that identifier with your account, together with when you arrived from the ad, what you did (trial started or plan bought), when, and for a purchase the amount paid (without tax) and its currency. A plan you buy later is reported on your trial's click only if it is your first paid plan and you buy it within 90 days of arriving from the ad. We do this only for accounts created on or after 2026-10-01, 15:00 UTC; for an account created before then we never do it, even after a later click on one of our ads. If you open our payment page and do not pay, we delete what we kept for that payment within three days; a trial you started stays recorded, as §8 says. We keep it, and report a purchase, only if you visit from the United States (we go by the country Cloudflare reports for your connection), and never if your browser sends a Global Privacy Control signal. If you forward the address of one of our pages that carries this identifier, a trial or purchase started from it within 30 days of your first arrival may be reported on your original click, even if someone else starts it. Like any web address, it also appears in our web-server logs |
The web address of the page you arrive on, read by our server, which then carries it, with the time you arrived, in the addresses of the formsieve.com pages you open next. No cookie or script is used |
We do not buy personal data, and we do not use advertising or tracking cookies.
| Purpose | Data | Legal basis (EU/UK GDPR) |
|---|---|---|
| Provide the account, trial, Free plan and subscription, and plugin updates; sign you in; send service e-mails (trial, usage alerts, renewal reminders, cancellation and withdrawal confirmations) | Account, sign-in, key and service data, plugin updates | Contract (Art. 6(1)(b)) |
| Take payments, issue invoices, handle tax and refunds | Billing | Contract; legal obligation for tax records (Art. 6(1)(c)) |
| Keep proof of your consents to the Terms, to automatic renewal and to the immediate start | Consent records | Legal obligation (for example California Bus. & Prof. Code 17602) and legitimate interest in proving the contract (Art. 6(1)(f)) |
| Count AI checks, enforce plan and fair-use limits, answer billing questions | Key and service data, request records | Contract |
| Protect the service: detect key sharing, abuse, fraud and card testing; keep the service secure; back it up so that we can restore it; check that it works (our status page and monitoring) | Request records, logs, IP addresses, the anti-bot check; backups hold everything we store | Legitimate interest in security and in keeping the service running (Art. 6(1)(f)) |
| Prevent abuse of the free trial and the Free plan: we refuse temporary e-mail addresses, allow one trial per e-mail address and one free allowance per site, limit how many trials can start from one network in a day, and compare the e-mail domains and networks of sign-ups | Account e-mail domain, a hash of your e-mail address (not the address), sign-up network (hashed), sites | Legitimate interest in preventing abuse (Art. 6(1)(f)) |
| Answer support requests | Support | Contract, or legitimate interest where you are not a customer |
| Answer your questions about Formsieve in the AI chat, from our own pages; keep the chat within its limits (questions per network and per conversation, a daily spending cap) and protect it from abuse | AI chat (questions, answers, the counters), the anti-bot check | Our legitimate interest in answering visitors' questions and in keeping the chat available and affordable (Art. 6(1)(f)); where you ask before buying, steps you ask for before a contract (Art. 6(1)(b)) |
| When you use "Ask a person": send your question to our support team so that a person can answer you by e-mail, after checking it for spam | Your e-mail address, name, note, the conversation and the page | Steps you ask for before a contract, or our legitimate interest in answering you and in keeping spam out of our support inbox (Art. 6(1)(b) and (f)) |
| Understand how the website is used, in aggregate | Cookieless statistics | Legitimate interest |
| Find out which of our Google ads lead to trials and purchases, so that we can adjust the ads and what we bid for them. We do not use it for remarketing or audience lists. | Ad click identifier, with what you did, when, and for a purchase the amount paid | Our legitimate interest in measuring our advertising (Art. 6(1)(f)). Our ads target people in, or regularly in, the United States, and we keep the identifier only for visits from the United States (§3). You can object or opt out (§10, §13) |
| Comply with the law and defend legal claims | As needed | Legal obligation; legitimate interest |
We do not sell personal data for money. If you start a trial or buy a plan after clicking one of our Google ads, we tell Google (§6). Some US state laws may treat that as "sharing" personal data, a "sale" or "targeted advertising"; you can opt out as §13 explains. We do not use personal data for automated decisions with legal or similarly significant effects.
formsieve.com sets only cookies needed for the site to work: while you sign in (fsv_account_pending, 30 minutes), while you are signed in (WordPress's login cookies), and the cookie Cloudflare Turnstile may set on the forms it protects. Stripe sets its own cookies on its checkout and customer-portal pages, which Stripe runs. Visit statistics, where we use them, come from Cloudflare Web Analytics, which sets no cookie. Measuring our Google ads (§3, §4) uses no cookie and no browser storage, and formsieve.com loads no Google advertising or analytics script. The AI chat sets no cookie of its own: it keeps the conversation (your questions, the answers, a random conversation ID and a 30-minute proof that you passed the anti-bot check) in your browser tab's session storage (fsChat.v1), and notes there that its button has been shown (fsChatSeen). Session storage is deleted when you close the tab; "Start over" in the chat deletes the conversation sooner. When the chat runs the anti-bot check (§3), Cloudflare Turnstile may set its cookie, as on the forms.
| Recipient | What for | Data |
|---|---|---|
| Stripe, Inc. (USA) | Payments, subscriptions, invoices, tax calculation, customer portal | Billing, account e-mail |
| Resend (Plus Five Five, Inc., USA) | Sending our e-mails, including the e-mail that "Ask a person" in the AI chat sends to our support address | E-mail address, e-mail content (never submission content); for a chat handoff, everything listed under "Ask a person" in §3 |
| Google LLC (USA) | Google Workspace: our hey@, hello@ and support@formsieve.com addresses since 2026-09-29, and Thinking42's own mail | Support mail, including the e-mails "Ask a person" sends, and the alerts, daily reports and daily summaries of our server's error logs that we e-mail our staff (§8) |
| Google LLC (USA): Google Ads | Measuring which of our ads lead to trials and purchases. Google fetches a private list of these conversions from our server, over an encrypted connection, on a regular schedule. Google uses the data as an independent controller under its own terms and privacy policy (https:// |
For each trial or purchase that followed a click on one of our ads: the click identifier, "Trial started" or "Subscription purchased", the time, and for a purchase the amount paid (without tax) and its currency. We never send Google your e-mail address, name, Formsieve key, IP address, billing details or anything you typed (Google has its own record of the ad click, under its privacy policy) |
| Cloudflare, Inc. (USA) | DNS, network security, the encrypted tunnel to our server, the anti-bot check, cookieless statistics, and storage of our nightly backups | IP addresses and request data in transit; an encrypted copy of the databases and files on our server (encrypted on our server before upload; Cloudflare does not hold the key) |
| Amazon Web Services, Inc. (USA, us-east-1) | Hosting our server and database | Everything we store |
| OpenRouter, Inc. (USA) | Gateway to the AI models: the spam-check model, and the AI chat's model. Every request we send it asks for zero-data-retention routing | For a customer's checks, a pseudonymous identifier of your account (a keyed hash, not your e-mail or name), sent with each check so that the gateway can tell our customers apart; the form content it receives is covered by §11, not by this policy. For the AI chat, your question and the earlier messages of the conversation (§3). For "Ask a person", what we check for spam (§3) |
| Google LLC (Vertex AI) or Amazon Web Services, Inc. (Amazon Bedrock), in the USA; OpenRouter picks one of the two for each question | Running the AI chat's model, Claude Haiku by Anthropic, PBC, in the USA only: we let OpenRouter use only Google's US endpoint and Amazon's us-east-1 endpoint for the model, which it lists as keeping no data. Anthropic does not run these requests itself | Your question and the earlier messages of the conversation, with text from our pages |
| TypeSafe AI, Inc. (USA), through OpenRouter | Running the Jev model of Formsieve's own spam check on what you send with "Ask a person" | Your name and note, your own questions in the chat, and the domain of your e-mail address (not the address) |
| Professional advisers, authorities | Legal, tax and accounting advice; when the law requires | As needed |
A buyer of our business would receive the data under this policy.
We are in the United States, and our service providers above are US companies. Cloudflare runs a global network. OpenRouter is hosted in the USA, but requests reach it through Cloudflare's global network, and it does not promise to handle a request only in the USA. The AI chat's model runs only in the USA, on the Google and Amazon endpoints named in §6. If you are in the EU, the EEA, the UK or Switzerland, your data is transferred to the USA. Where a provider is certified under the EU-U.S. Data Privacy Framework (and its UK and Swiss parts), that certification applies; as of 2026-09-27 Cloudflare, Amazon (for AWS), Stripe, Resend and Google were certified; OpenRouter and TypeSafe AI were not. Thinking42 itself is not certified. Otherwise we rely on the European Commission's standard contractual clauses and the UK Addendum. Ask us for a copy.
| Data | Kept for |
|---|---|
| Sign-in codes | 10 minutes |
| Sign-in sessions (IP address and browser) | While you have an account. A session lasts at most 14 days; WordPress removes an ended session's record the next time you sign in or out, or when your account is deleted |
| Request records (no submission content) | 30 days (deleted by a daily job once they are 30 days old), then daily and monthly totals per key and site (numbers only, such as AI checks, errors, the amount of text processed and its cost; never a site's address) for 25 months, also after the key and its sites are deleted |
| Account, key and site data | While you have an account. A lapsed, cancelled or revoked key and its sites are deleted 12 months after its subscription ends. A key's sites include our spam-check service's record of each site that used the key: its address, when it was first and last seen, and whether it used a trial or a free allowance, which we use so that each site gets one free allowance |
| Consent records, including the hash of your e-mail address for a trial | 3 years, or 1 year after the contract ends, whichever is longer |
| Invoices and billing records, and your customer record at Stripe | 7 years, as tax law requires. They are kept in our Stripe account |
| Support mail | 24 months after the last message. Posts in the plugin's support forum on WordPress.org are public; WordPress.org keeps them under its own terms and privacy policy |
| AI chat | We keep no copy of the conversation on our server once a request is answered, but a long one can leave bytes of its temporary files in the free space of our server's disk until they are overwritten, and in the disk's snapshots (§3; the backups row below). Your browser tab keeps it until you close the tab or choose "Start over" (§5). We ask OpenRouter for zero-data-retention routing, so it sends the chat's questions only to endpoints that it lists as keeping no data; OpenRouter and the company that runs the chat's model (Google or Amazon) may still hold a request briefly in memory to answer it and to reuse our pages' text (prompt caching). The counters that enforce the limits are deleted within a day after the hour (for "Ask a person", the day) they count; the daily totals (numbers only) are kept for the last 30 days on which the chat was used. "Ask a person" becomes support mail (the row above); our spam-check service keeps its request record of that check, without the content, for 30 days, as for any check. TypeSafe AI, which runs the spam check's model, is listed by OpenRouter as keeping no data, but its own terms let it use what it processes, without a time limit, to derive telemetry and to monitor for fraud and abuse (as of 2026-10-08). Our web-server logs hold the chat's requests (the address of the request, not what you typed) for 30 days, as for any page |
| Web-server and security logs | 30 days |
| Other records we keep to run the service | Alerts about the service (key numbers and counts; they can also name the first 8 characters of a hash of a key, the Stripe IDs of subscriptions whose cancellation Stripe has not confirmed, and, in our tax alerts, a customer's billing country and the day of their payment): 13 months. Copies of these alerts, of our daily reports (figures about the service and our sales, which can name key numbers and the facts of our tax alerts) and of our daily summaries of our server's error logs (in which e-mail and IP addresses, keys and payment IDs are masked, but key numbers and, rarely, the first 8 characters of a hash of a key can remain), which we e-mail our staff, stay in our staff mailbox at Google (§6); we have not yet set a fixed period for them. Our log of the e-mails we send you (address and subject, never the text): 25 months, or until your account is deleted. The plugin update log: 30 days. Copies of billing data from Stripe in our admin screens: up to 31 days. The Stripe IDs of the refunded charges our alerts have reported: the latest 200. Our record of the payment notifications Stripe sends us (their IDs and types, the Stripe object they concern, such as your customer, subscription or invoice ID, and the result); our log of what our staff did on an account (account and key numbers, the action, the staff member's reason and the action's details, which can name your sites; your e-mail address, keys and card numbers are masked); our record of the first payment without a business tax ID from each region of the EU, the EEA and the UK (the key number, the billing country, the invoice ID and the date and time of payment); and the daily copies of our revenue figures in our admin reports, which list each subscription's Stripe ID and amount: we keep them as long as we need them to show what happened on an account, to report our revenue and to meet our tax obligations, and have not yet set a fixed period |
| Ad click identifier, with what you did and when | Until 90 days after the arrival on formsieve.com through the ad's link that the trial or purchase followed, then deleted; earlier if you opt out (§13) or your account is deleted. What we keep when you open our payment page and do not pay: within three days (a trial you started keeps its own record). Each trial or purchase stays in the list Google fetches for up to 90 days. If, after a trial that came from an ad, you open our payment page from outside the United States or with a Global Privacy Control signal, we keep a note without the identifier (when you opened it, for up to three days; if you pay, the invoice number and payment time, for 90 days) so that the purchase is never reported. A record that you opted out is kept while you have an account |
| The same data at Google | Under Google's own rules (https:// |
| Backups (nightly backups on our server, their encrypted copies stored with Cloudflare, and snapshots of our server's disk) | We delete every backup, encrypted copy and snapshot of our server's disk within 14 days of making it. |
You can delete your account on your account's privacy page once your subscription is cancelled, or ask us to. Your keys stop working at once. We then delete your account, your sign-in sessions, our notes about you and our log of the e-mails we sent you. We keep: invoices, billing records and your customer record in our Stripe account; your consent records, and a record of the deletion; your keys, until they are deleted under the rule above; and the other records in the table above, for the periods it gives.
We protect data with encryption in transit, a server that accepts no inbound connections except through an encrypted tunnel, keys that our spam-check service keeps only as hashes, least-privilege access and multi-factor authentication. Details: /security/.
Depending on where you live, you can ask us to: tell you what we hold and give you a copy; correct it; delete it; restrict or object to our use of it (including where we rely on legitimate interest); receive it in a portable format; and stop telling Google about your trial or purchase after an ad click (§4), which some US state laws call "sharing" or "targeted advertising" (§13). Write to support@formsieve.com. We answer within one month (EU/EEA/UK) or 45 days (US states), and we may need to confirm your identity. We will not treat you differently for using these rights.
If you are in the EU, the EEA or the UK, you may complain to your data protection authority (in the UK, the Information Commissioner's Office). We would like the chance to help first.
When a website owner connects the Formsieve plugin with a Formsieve key, the plugin sends certain data about each form submission that passes its local filters to our spam-check service: the text of the ordinary form fields with their labels (phone numbers redacted by default; fields that look like passwords, card, bank, health or ID data excluded), the domain of the sender's e-mail address (not the full address), the site's name, the form's name, the site's languages and the descriptions the website owner writes for the site and form, the host names of links in the sent fields, and a few signals such as how long the form took to fill in, how many submissions came from the same IP address in the last hour (a count, not the address) and whether the sender was marked as spam or not spam on that site before. IP addresses and full e-mail addresses are not sent.
We send it to the AI model named at /subprocessors/ through OpenRouter, Inc., with zero-data-retention routing requested, and return a spam result to the website. We do not store the content of submissions. We keep request records without the content for 30 days (§3, §8). We do this only on the website owner's instructions, under our Data Processing Agreement. If you submitted a form on a website that uses Formsieve, please contact that website's owner with any request; we will help them answer it.
Thinking42 has not yet appointed a representative in the European Union under Art. 27 GDPR or in the United Kingdom under Art. 27 UK GDPR (as of the effective date above). This section will name them once they are appointed. Until then, people in those territories can write to support@formsieve.com with any question or request about their data.
California. If you start a trial or buy a plan after clicking one of our Google ads, we tell Google the click identifier and what you did (§3, §6). California law may treat this as "sharing" personal information for cross-context behavioural advertising. So we treat it as sharing, and you can opt out:
What we share is an identifier (the click identifier) and commercial information (that you started a trial or bought a plan, when, and the amount), with Google LLC. We do not sell personal information for money, and until 2026-10-01 we did not share it either. There is no agreed standard for "Do Not Track" signals, so we do not respond to them; use GPC instead. The categories of personal information we collect, their sources, purposes and recipients are in §3 to §6. Thinking42 is below the thresholds of the California Consumer Privacy Act as of the effective date; we still offer the rights in §10 and the opt-outs above.
Other US states: this policy serves as the required notice, and the rights in §10 are available to you. If a state law treats telling Google about trials and purchases after an ad click as "targeted advertising" or a "sale", you can opt out in the same ways (GPC or e-mail).
formsieve.com and the service are for businesses and adults. We do not knowingly collect data from anyone under 18.
We post changes here with a new version date. For material changes we e-mail account holders at least 30 days before they apply.
Thinking42, Inc., a Delaware corporation · 1480 NW North River Dr, Apt 2318, Miami, FL 33125, USA · support@formsieve.com