WordPress plugin intelligence profile

Quarivo Form Shield

Keep Contact Form 7 inquiries in a local review inbox, even when mail sending fails, and quietly quarantine only high-confidence spam.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.3
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.7 · PHP 7.4
Directory statusactive
Last directory update1 Sept 20262mo ago
Active installations20Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Quarivo Form Shield version 1.0.3 as active, updated 2mo ago and tested up to WordPress 7.1.

Overview

About this plugin

Quarivo Form Shield adds an independent, local inbox for Contact Form 7. It stores a reviewable record before Contact Form 7 attempts email, so a local mail error does not make the original inquiry disappear.

The important distinction

WordPress can report that its mail method processed a request without an error. That is not a mailbox delivery receipt. Quarivo Form Shield therefore shows Mail handoff accepted — delivery not verified separately from a mail error, skipped spam mail, and mail that was not attempted.

Conservative spam handling

  • Balanced mode is the default and treats every language equally.
  • Japanese-site enhanced and Strict Japanese modes are explicit administrator choices.
  • One URL, one foreign-language message, missing JavaScript, or a public email address does not cause automatic quarantine by itself.
  • Compound signals include URL/link structure, cross-field rotating-campaign patterns, a honeypot, browser-observed timing, local rate evidence, repeated promotion structure, executable markup, and bounded local moderator feedback.
  • Only high-confidence Quarivo results are quietly quarantined. Lower evidence stays visible as Needs review and ordinary mail remains available.
  • Akismet, reCAPTCHA, Cloudflare Turnstile, Flamingo, and other Contact Form 7 decisions are not disabled or overwritten. An existing spam result remains spam.
  • No message is automatically deleted.

Local inbox

The responsive WordPress administration inbox provides:

  • All, unread, read, important, normal, needs review, auto-quarantined, spam, mail-error, and invalid counts.
  • Search, form filtering, 25/50/100-row pagination, and bounded per-page bulk actions.
  • Full submitted fields, source form/page, sender information, score/reasons, Contact Form 7 status, and mail-processing status.
  • Reversible normal/review/spam decisions and local learning from explicit moderator choices.
  • A deliberate plain-text resend to the validated site administrator address. Submitted data is never reused as an email header and attachments are not automatically resent.
  • Private JSON and formula-safe CSV export.

Failure-safe storage

The first database insert occurs before validation, spam handling, upload processing, and email. Later Contact Form 7 hooks enrich the same unique row, preventing duplicate records from one request.

If a database write fails, Quarivo retries before mail, writes an authenticated-encrypted local recovery record, shows an administrator health warning, and processes a small recovery batch when the database becomes available. The original mail path is left available. A simultaneous database, private-filesystem, and mail outage cannot be made loss-free by an in-process plugin; Quarivo reports that failure instead of silently claiming success.

Protected attachments

Validated Contact Form 7 temporary uploads are copied before Contact Form 7 removes them. Quarivo enforces a 25 MB default storage limit and stores each file as AES-256-GCM authenticated ciphertext under a random opaque name in a protected plugin directory inside the site’s configured WordPress uploads directory. It does not create a public attachment URL.

A capability and nonce checked administrator request verifies and decrypts a download. If authenticated encryption or private storage is unavailable, Quarivo does not retain the attachment and displays a storage warning.

Privacy and retention

  • No API key, CAPTCHA, remote request, telemetry, external font, or third-party asset is required by Quarivo Form Shield.
  • Password, token, API-key, PIN, CVV, and card-number-like field names are redacted automatically. Administrators can add exact excluded field names.
  • Contact Form 7 do-not-store and storage-consent metadata is respected: operational metadata may remain, but submitted field values are not copied when the form prohibits storage.
  • Visible IP storage defaults to anonymized. Full IP display is opt-in; a keyed local hash supports rate checks.
  • Read, non-important entries and encrypted attachments have separate retention controls. Unread and important entries are not removed by scheduled entry retention.
  • WordPress personal-data export and erasure tools include exact sender-email matches.
  • Plugin deletion retains data by default. Permanent removal must first be selected in settings and confirmed by typing DELETE.

Contact Form 7 dependency

Contact Form 7 is not bundled. If it is absent or inactive, Quarivo Form Shield does not cause a fatal error. The existing inbox remains available and a clear administrator notice explains that new capture is paused.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • contact form
  • contact form 7
  • email
  • inbox
  • spam
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.7 · PHP 7.4
Update activity1 Sept 20262mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.