by Daniel Sturm 0 (0 reviews)

Privacy CAPTCHA for Cap

Name: Privacy CAPTCHA for Cap
Author: Daniel Sturm

Privacy-friendly spam protection for comments, login, registration, WooCommerce, and Gravity Forms, powered by your own Cap server.

Privacy CAPTCHA for Cap ranks #19,472 among WordPress.org plugins with 60+ active installations, is #757 of 2,900 in the Discussion & Community category, and was last updated Aug 12, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 7.0.6 (Current: 7.1.2)

v1.3.1 Current Version v1.3.1

Updated 1 month ago Last Update on 12 Aug, 2026

Refreshed 13 hours ago Last Refreshed on

#757 of 2,900 in Discussion & Community Top 50% by installs Downloads -60.7% this week

View on WordPress.org

Rank

#19,472

— No change

Active Installs

60+

+328.6%

KW Avg Position

116

78 better

Downloads

545

+3 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 70

Total Progress 30%

60+ 70+

1,449

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 7 more installs to reach 70+

Rank Changes

Current #19,472

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.3.1
Last Updated: Aug 12, 2026
Requires WP: 6.5+
Tested Up To: 7.0.6
PHP Version: 8.3 or higher
Author: Daniel Sturm

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

captcha comments Proof of Work spam woocommerce

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,760

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

30K+ installs

#1,009

Akismet Anti-spam: Spam Protection

5M+ installs

WPForms - AI Form Builder for WordPress - Contact Forms, Payment Forms, Survey Form, Quiz & More

5M+ installs

Jetpack - WP Security, Backup, Speed, & Growth

3M+ installs

#18

Disable Comments - Remove Comments & Stop Spam [Multi-Site Support]

1M+ installs

#38

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance

View all Discussion-and-community plugins

Frequently Asked Questions

Common questions about Privacy CAPTCHA for Cap

No. Cap is an independent open-source project by tiagozip (https://trycap.dev/), licensed under Apache-2.0. This plugin is an unofficial third-party integration and is not affiliated with or endorsed by the Cap project. We reference the "Cap" name only to indicate which software this plugin works with.

You provision those in your self-hosted Cap server. See the Cap documentation at https://trycap.dev/.

By default: from the copy bundled inside this plugin at wp-content/plugins/privacy-captcha-for-cap/assets/wasm/cap_wasm_bg.wasm. You can optionally switch to your own Cap server's /assets/cap_wasm_bg.wasm endpoint under Settings → Privacy CAPTCHA for Cap → Privacy. Either way the file is served from your own infrastructure — no third-party CDN is contacted.

The bundled assets/wasm/cap_wasm_bg.wasm is the WebAssembly module the Cap widget uses to run the proof-of-work challenge in the visitor's browser. Bundling it locally is the privacy-friendly default: it means no third-party CDN (jsdelivr) is contacted at page load, so visitor IPs are never shared (DSGVO/GDPR-clean). It is the unmodified upstream file from the @cap.js/wasm npm package (Apache-2.0), part of the open-source Cap project. The plugin does not alter it. Its source and build live in the Cap repository at https://github.com/tiagozip/cap, and the vendoring step is reproducible via scripts/build-assets.mjs (bun run build), which copies the file verbatim and bun run build:check verifies it matches upstream.

Yes. Define CAP_CAPTCHA_SECRET_KEY in wp-config.php and the plugin will use it instead of the value saved in wp_options.

When enabled, the plugin lets submissions through if the Cap server is unreachable. Off by default — only turn it on if temporary outages must not block legitimate users (logins, checkouts). It applies only when Cap genuinely can't be reached; a CAPTCHA the server actively rejects is always blocked. You can set fail-open per form (e.g. open for logins, closed for contact forms) under the global toggle, and any submission accepted this way is flagged for review (Gravity Forms entries, WooCommerce orders, comments, and new users get a cap_captcha_fail_open marker; orders also get a note).

Yes. On a multi-page form the CAPTCHA is only required on the page that shows it, or on the final submit. When a form is protected automatically, the field is placed on the last page — which on a form built with a preview step (a page break plus {all_fields}) is the preview page, right next to the submit button. If that last page can be hidden by conditional logic, place the CAPTCHA field manually on a page that always renders, or move it with the cap_captcha_gf_field_page filter — the plugin will not enforce a CAPTCHA the visitor was never shown.

No third-party CDN requests. All widget assets are bundled and served from this plugin, including the pako decompression library (assets/js/vendor/pako_inflate.min.js), which older browsers without the native DecompressionStream API load locally instead of from jsdelivr. The only network requests the widget makes are to your own Cap endpoint to fetch and verify challenges.

Yes. Every surface passes through the cap_captcha_protect filter — ($enabled, $context) returning a boolean — before the widget renders and before a submission is verified. For example, to skip the CAPTCHA for logged-in users everywhere: add_filter('cap_captcha_protect', fn($on, $ctx) => is_user_logged_in() ? false : $on, 10, 2);. There is also a per-surface filter, e.g. cap_captcha_protect_woocommerce_login. Context ids: gravity_forms, contact_form_7, comments, login, registration, woocommerce_checkout, woocommerce_login, woocommerce_registration, woocommerce_lost_password.

Yes — useful for legally required or accessibility-sensitive forms. For Contact Form 7, set the mode to Manual (Settings → Form placement) and add the [cap_captcha] tag only to the forms you want protected; or, in Automatic mode, add cap_captcha: off to a form's Additional Settings to skip just that one. For Gravity Forms, each form has a Privacy CAPTCHA setting (Default / Always / Never) so you can exclude individual forms even when "protect all" is on.