Every version of the Formsieve Terms of Service, Privacy Policy, Data Processing Agreement and Refund and cancellation policy, newest first. The current version of each is the one in force. Each earlier version is described by how it differs from the version after it.
Terms of Service
- Version 1.0.1, effective 2026-10-14 (current): /terms/. A correction: section 9.2 says what a refund does, as we do it: a full refund ends the subscription it paid for, and revokes your key only if the key is still on that subscription. Consent records made from 2026-10-14 20:28 UTC store Terms version 1.0.1, and the confirmation e-mails for them call it "1.0.1" (the list of consent records in your account still shows "2026-09-26", the version of the consent box texts).
- Version 1.0, effective 2026-09-29 and replaced 2026-10-14: confirmation e-mails sent before 2026-09-30 06:21 UTC call this version "2026-09-26"; later ones call it "1.0" when their consent record was made before 2026-10-14 20:28 UTC. Consent records, and the list of them in your account, show "2026-09-26", the version of the consent box texts; records made from 2026-09-30 06:21 UTC and before 2026-10-14 20:28 UTC also store Terms version 1.0. Its text was the same as 1.0.1, except that section 9.2 ended "A refund ends the subscription and revokes the key."
Privacy Policy
- Version 1.2.1, effective 2026-10-14 (current): /privacy-policy/. Corrections that describe what we already do; nothing new is collected, shared or used. Section 11 names everything about the site and the form that each check sends to the AI model: the site's name, the form's name, the site's languages and the descriptions the website owner writes for the site and form. Section 8 says that alerts about the service can name the first 8 characters of a hash of a key, the Stripe IDs of subscriptions or, in our tax alerts, a customer's billing country and the day of their payment; that we keep the Stripe IDs of the latest 200 refunded charges our alerts have reported; that we keep a record of the first payment without a business tax ID from each region of the EU, the EEA and the UK and have not yet set a fixed period for it; and that daily and monthly totals per key and site stay for 25 months, also after the key and its sites are deleted. It also says that the copies of the alerts, daily reports and daily summaries of our server's error logs that we e-mail our staff stay in our staff mailbox, for which we have not yet set a fixed period. Section 6 says that our Google Workspace mailboxes also hold the alerts, daily reports and daily summaries of our server's error logs that we e-mail our staff. Section 3 says that refusals beyond 20 a minute for one key may only be counted. Sections 3 and 8 name the plugin's public support forum on WordPress.org. Sections 6 and 7 no longer name Zoho, which no longer holds our mail.
- Version 1.2, effective 2026-10-08 and replaced 2026-10-14: two kinds of change from 1.1. First, it adds the AI chat on formsieve.com and its "Ask a person" handoff (sections 2, 3, 4, 5, 6, 7 and 8): what the chat collects and why; that we do not keep the conversation on our server, and that your browser tab keeps it in session storage (a long one can pass through temporary files while a request is handled; deleting them does not erase their bytes from our server's disk, so they can stay there until they are overwritten, and in the disk's snapshots); who processes your questions (OpenRouter as the gateway, and Google's Vertex AI or Amazon Bedrock, in the USA only, running Anthropic's Claude Haiku model on endpoints that OpenRouter lists as keeping no data); that "Ask a person" e-mails your question to our support address after Formsieve's own spam check (TypeSafe AI through OpenRouter; TypeSafe's terms let it use what it processes, without a time limit, to derive telemetry and to monitor for fraud and abuse); and how long each part is kept. The anti-bot check now also protects the chat. Second, corrections that describe what we already did; for them, nothing new is collected, shared or used. Sections 3, 4, 7, 8, 9 and 11 now state: the IP address and browser of each sign-in session, which stay with your account until you next sign in or out, or your account is deleted; the full billing address and the card's expiry date; what our public cancel and withdraw pages record; the hash of your e-mail address that allows one trial per address, and the daily limit on trials from one network; the technical details in request records; the plugin update log; backups and monitoring as purposes; that Zoho may also process data in India and that Cloudflare runs a global network; that 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; that revoked keys, too, are deleted with their sites 12 months after their subscription ends, and that a key's sites include our spam-check service's record of each site that used the key; that invoices, billing records and your customer record at Stripe are kept in our Stripe account; how long other service records are kept, and that for some of them we have not yet set a fixed period; that when you delete your account we keep more than invoices: your customer record at Stripe, your consent records and a record of the deletion, your keys until they are deleted under section 8, and the other records in section 8; that your account on formsieve.com keeps your key itself, and only our spam-check service keeps keys as hashes; and the signals the plugin sends about a submission. Measuring our Google ads is unchanged from 1.1. Its text was the same as 1.2.1, except that: section 3 did not say that refusals beyond 20 a minute for one key may only be counted; in section 6, the data of Google's Workspace row read "Support mail, including the e-mails "Ask a person" sends"; in section 8, the row on request records read "30 days (deleted by a daily job once they are 30 days old), then daily totals per key and site for 25 months", the row on other records began "Alerts about the service (key numbers and counts): 13 months." and did not name the copies in our staff mailbox, did not name the IDs of refunded charges, and its list of records with no fixed period did not name our record of the first payment without a business tax ID from each region and ended "we keep them as long as we need them to show what happened on an account and to report our revenue, and have not yet set a fixed period", and the support rows did not name the WordPress.org forum; section 11 named "the site's own description" where 1.2.1 names the site's name, the form's name, the site's languages and the descriptions the website owner writes for the site and form; and section 6 named Zoho Corporation (USA/India) for "Our hello@ and support@formsieve.com addresses until 2026-09-29", which section 7 also named.
- Version 1.1, effective 2026-10-01 and replaced 2026-10-08: from this version we measure our Google ads by telling Google when a click on one of our ads leads to a trial or a purchase, without cookies, for accounts created from 2026-10-01, 15:00 UTC on; accounts created before then are never measured (sections 3, 4, 5, 6, 8, 10 and 13). Section 6 added Google Ads to the recipients. Section 8 also said that we delete every backup, encrypted copy and snapshot of our server's disk within 14 days of making it. Its text was the same as 1.2, except that: section 2 did not name the AI chat or "Ask a person". In section 3, the sign-in row read "one-time codes and a short-lived cookie while you sign in" (source: "Generated by us"), the anti-bot row named only "the forms that e-mail you a sign-in code (starting a trial, signing in, subscribing)", the billing row read "name, billing country and postal code, optional business tax ID and its validation result, subscription and invoice details, the last four digits and brand of your card", the consent records row ended with "the time, your IP address, your country and your browser" (source: "Our subscribe, cancel and withdraw pages"), the key and service data row listed for each site "site address, WordPress environment type, form plugin, plugin version, first and last seen", the request records row read "for each check, the time, a request ID, key and site identifiers, plugin and version, status, latency, the model version and cost reported by our AI provider, and the spam band of the result. Never the content of the submission", and there were no rows on plugin updates or the AI chat. In section 4, the first purpose read "Provide the account, trial, Free plan and subscription; sign you in; send service e-mails (trial, usage alerts, renewal reminders, cancellation and withdrawal confirmations)" (data: "Account, sign-in, key and service data"); the security purpose read "Protect the service: detect key sharing, abuse, fraud and card testing; keep the service secure" (data: "Request records, logs, IP addresses, the anti-bot check"; legal basis: "Legitimate interest in security (Art. 6(1)(f))"); the abuse purpose read "Prevent abuse of the free trial and the Free plan: we refuse temporary e-mail addresses, allow one free allowance per site, and compare the e-mail domains and networks of sign-ups" (data: "Account e-mail domain, sign-up network (hashed), sites"); and there were no rows on the AI chat or "Ask a person". Section 5 did not describe the AI chat's session storage. In section 6, Resend's row read "Sending our e-mails" (data: "E-mail address, e-mail content (never submission content)"), the data of the Google Workspace row read "Support mail", OpenRouter's row read "Gateway to the AI model" (data: "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"), and there were no rows on Google's Vertex AI, Amazon Bedrock or TypeSafe AI. Section 7 began "We are in the United States, and so are our service providers above. If you are in the EU, the EEA, the UK or Switzerland, your data is transferred to the USA." In section 8, there were no rows on sign-in sessions, the AI chat or other records we keep to run the service; the request records row read "30 days, then daily totals per key and site for 25 months"; the account, key and site data row read "While you have an account; a lapsed or cancelled key and its sites are deleted 12 months after the subscription ends"; the consent records row was labelled "Consent records"; the invoices row was labelled "Invoices and billing records" and read "7 years, as tax law requires (kept by Stripe and by us)"; and the paragraph after the table read "You can ask us to delete your account after your subscription has ended. We then keep only what the law requires (for example invoices)." Section 9 named "hashed keys" where it now names "keys that our spam-check service keeps only as hashes". In section 11, the first sentence ended with "the site's own description and a few numbers such as how long the form took to fill in".
- Version 1.0.2, effective 2026-09-30 and replaced 2026-10-01: the same text as 1.1, except that it did not describe measuring our Google ads and that section 8 described backup retention differently. Sections 3, 4, 6 and 8 had no rows on the ad click identifier or Google Ads, section 5 had no sentence on it, and section 10 did not list the right to stop us telling Google. In section 4, the sentence after the table read "We do not sell or 'share' personal data (as the California Consumer Privacy Act defines those words), and we do not use it for automated decisions with legal or similarly significant effects." In section 13, the California item read "We do not track visitors across other websites, so we do not respond differently to 'Do Not Track' signals. We honour Global Privacy Control signals as an opt-out of sale or sharing, although we do neither. The categories of personal information we collect, their sources, purposes and recipients are in §3 to §6. We do not sell or share personal information and have not done so in the past 12 months. 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 item on other US states ended with "the rights in §10 are available to you". In section 8, the backups row read "Each backup, copy and snapshot is deleted about 14 days after it is made. A snapshot of our server's disk also holds the backups on the disk at that moment, so a backed-up copy of your data can remain for up to 28 days".
- Version 1.0.1, effective 2026-09-30 and replaced the same day: the same text as 1.0.2, except that in section 6 Zoho's row read "The support@formsieve.com mailbox" (data: "Support mail") and Google's row read "Google Workspace for Thinking42's own mail" (data: "Support mail forwarded there"), and in section 8 the backups row read "Up to 14 days, then deleted".
- Version 1.0, effective 2026-09-29 and replaced 2026-09-30: the same text as 1.0.1, except that in section 6 Cloudflare's row read "DNS, network security, the encrypted tunnel to our server, the anti-bot check, cookieless statistics" (data: "IP addresses and request data in transit"), and in section 8 the backups row read "Backups: 14 days, then overwritten".
Refund and cancellation policy
- Version 1.0.1, effective 2026-10-14 (current): /refund-policy/. A correction: section 2 says what a full refund does (it ends the subscription it paid for, and revokes your key only if the key is still on that subscription; we cancel at once and keep trying until our payment processor confirms), and that a payment dispute decided for you also ends the key's subscription, whichever of the key's payments it concerns. Section 4 says the same of a withdrawal.
- Version 1.0, effective 2026-09-29 and replaced 2026-10-14: the same text as 1.0.1, except that in section 2 "What a refund does" read "it ends the subscription at once and revokes the key; the plugin's local filters keep working. A partial refund (for example after a price change under Terms §8.3) does not revoke the key." and "Chargebacks" ended "if the dispute is decided for you, the key is revoked, as with a refund.", and section 4 ended "When the withdrawal is processed, the subscription ends and the key is revoked."
Data Processing Agreement
- Version 1.0.2, effective 2026-10-14 (current): /dpa/. A correction: Annex I names the form's name among the data the plugin sends; nothing new is processed.
- Version 1.0.1, effective 2026-10-08 and replaced 2026-10-14: corrections that describe the processing and the security measures as they are; nothing new is processed. Section 12.2 and Annex II items 7, 10 and 14 now state how backups, keys and idempotency records are kept and deleted (item 7 also states that your account on formsieve.com keeps your key itself, that only the spam-check API keeps keys as hashes, and which AI-provider keys it describes: those the spam-check API uses), section 10.5 states that onward transfers go to companies in the United States and that Annex III gives where each sub-processor processes the data, and Annex I names the signals the plugin sends and the people named in a submission. Its text was the same as 1.0.2, except that Annex I named "the website's name, address, languages and the descriptions the Customer writes for the site and form".
- Version 1.0, effective 2026-09-29 and replaced 2026-10-08: the same text as 1.0.1, except that: section 10.5 read "Onward transfers from Thinking42 to its sub-processors happen within the United States under contracts that meet §7.3 and SCC Clause 8.8 and Clause 9."; section 12.2 read "Backups are overwritten within 14 days." where it now reads "Thinking42 deletes every backup, encrypted copy and snapshot of its server's disk within 14 days of making it."; in Annex I, the data subjects were "Visitors who submit forms (or, where offered, comments) on the Customer's websites" and the categories named "numeric signals (for example number of links, seconds from page load to submit)"; in Annex II, item 7 read "Formsieve keys are looked up by a SHA-256 hash; logs hold only a short prefix of the hash. Thinking42's AI-provider keys live only in a root-owned configuration file on the server, never in code or logs.", item 10 ended with "Nightly database backups kept 14 days." and item 14 read "Automatic deletion jobs for request records (30 days), idempotency records (10 minutes) and backups (14 days)."; and its header had no link to earlier versions.