Formsieve - changelog
By Thinking42. Documentation: https://formsieve.com/docs/

= 1.1.1 (2026-09-30) =
* First version published on WordPress.org. Translations come from translate.wordpress.org; the Spanish (Spain) files that 1.1.0 bundled are no longer in the plugin.
* The Formsieve entry in the WordPress admin menu shows the Formsieve mark instead of a generic filter icon, in the colours of your admin colour scheme. The Formsieve tab in Gravity Forms' settings shows the mark too.
* The notice about an incomplete installation shows only on the Plugins and Updates screens.
* A key whose plan is not active no longer also shows "This site is not on your Formsieve plan".

= 1.1.0 (2026-09-29) =
* One plugin, Formsieve (slug formsieve), with a module for Gravity Forms and one for Contact Form 7 (with Flamingo), each turned on when its form plugin is active.
* Free local checks on every enabled form, with or without a key: honeypot (Contact Form 7; Gravity Forms has its own), signed time-to-submit token, trivial-content skip, replay cache with bulk-duplicate blocking, per-IP rate limit, allow and block lists, WordPress Disallowed Comment Keys, disposable e-mail domains and heuristics.
* One AI check per submission that passes them, through the Formsieve service (api.formsieve.com) with a Formsieve key (free 14-day trial; FORMSIEVE_API_KEY in wp-config.php also sets it): calibrated spam probability, category and reason; allow, review and block bands; Low, Medium and High presets, numeric thresholds and per-form overrides.
* Gravity Forms: mark as spam (default), silent discard or validation error; spam note, entry panel with Re-check, sortable probability column and entry meta. Contact Form 7: its own spam status, spam log and spam message; Flamingo details; "[Possible spam NN%]" subject tag for the review band (never on mail to the visitor).
* Feedback loop: spam and not-spam corrections label the log and teach trusted and blocked senders (hashes only).
* One decision log ({prefix}formsieve_log, with a form plugin column), one settings screen and a Dashboard with a "Form plugins" card; the rate limit per IP, the replay cache, the circuit breaker, the plan state and the monthly cap are shared by both form plugins.
* One request for an honest WordPress.org review, on Formsieve's Dashboard only and for administrators, after 14 days and 25 stopped spam submissions, with no service error in the last 7 days. "Maybe later" waits 30 days (at most twice); "Leave a review" and "Don't ask again" end it for that user. FORMSIEVE_REVIEW_ASK set to false in wp-config.php, or the formsieve_review_ask filter, turns it off.
* Set-up wizard in three steps: Formsieve key (links to the trial and the account), what is sent (recipients, the Terms and Data Processing Agreement tick), Test connection (key verification with plan, usage and this site's slot, then one test check that uses no AI check).
* Billing states of the key (no active plan, site not on the plan, allowance paused) are delivered with "Not checked by AI: <reason>" and never produce spam, whatever the fail mode; the calls pause and are re-checked every 15 minutes.
* Fail modes: fail open (default), "hold for review" and "fail closed"; "fail closed" applies to outages and caps only.
* Dashboard plan card (plan, status, AI checks this month with 80% and 100% marks, sites, renewal or trial end); notices for the trial end, 80%, 100%, last warning, pause, inactive plan, site not on the plan and a needed plugin update, dismissible and on Formsieve's own screens only.
* "Protect your allowance": an hourly limit of AI checks per form; the plan limits monthly usage.
* The notice under forms is on by default with a Formsieve key, once the AI check can run.
* Privacy: consent (version 2) and privacy-policy text naming Thinking42 as processor and its sub-processors; no content stored by the service, request records kept 30 days; e-mail domain only, phone redaction, sensitive-field exclusion, personal-data export and erasure, log retention.
* Test mode (simulated verdicts, nothing sent). WP-CLI: status (plan, usage, slot), key set|verify|clear (the key is read from standard input), test and stats.
* Admin screens use the Formsieve design; interface in English and Spanish (Spain, es_ES), with a .pot file for other translations.

