Captcha plugin data paths

Where WordPress captcha plugins send visitor checks

A captcha can contact an outside service when a login, comment, or form page loads. Requests to that service include an IP address and browser information. Some plugins draw an image or hide a honeypot field on your own server. This table describes the setups below; your settings can change where requests go.

Based on plugin documentation, not tests of your site. Your settings can change what loads. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group captcha plugins

We compare the captcha setups named below. A plugin can check spam on your server and still offer an outside captcha. We have not tested when requests start relative to cookie consent or assessed how long captcha-service logs are kept.

Captcha and anti-spam plugins

No paid placement. On your server first, then outside captcha services, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorReceiving domainsHow long data is keptBefore consentLinksSource
Antispam Bee (local honeypot)

This row covers Antispam Bee in its default local mode: a hidden honeypot field on the WordPress comment form, plus on-server checks. The listing says it blocks spam comments without captchas and without sending personal information to third-party services. Country allow/block (iplocate.io) and language checks are optional extras and are not this row. Gravatar trust is also a different setup. Consent timing is not tested here.

On your serverNo outside captcha service in this setup. Other page requests are not covered.Not assessedNot tested
  • None
Really Simple CAPTCHA

This row covers Really Simple CAPTCHA when a calling plugin (often Contact Form 7) asks it to draw an image. The listing says it stores a temporary image file and a matching answer file on your server. It needs GD and FreeType on that server. There is no documented visitor request to an outside captcha network in this setup. Consent timing is not tested here.

On your serverNo outside captcha service in this setup. Other page requests are not covered.Not assessedNot tested
  • None
hCaptcha for WP

This row covers hCaptcha for WP when an integration is turned on for a login, comment, or form. The listing says the answering visitor IP address and browser data may be sent to the hCaptcha service on pages where protection is active. Plugin source sets API_HOST to js.hcaptcha.com and loads /1/api.js from that host. A hidden honeypot field in this plugin is a separate local check and is not this row. Consent timing is not tested here.

Outside captcha servicejs.hcaptcha.comNot assessedNot tested
  • None
reCaptcha by BestWebSoft

This row covers reCaptcha by BestWebSoft when Google reCAPTCHA v2, v3, or Invisible is enabled on a guarded form (login, comments, registration, or a listed contact form). Plugin source builds the visitor script as https://www.google.com/recaptcha/api.js, or https://www.recaptcha.net/recaptcha/api.js when the global-endpoint option is on. The listing names Google reCAPTCHA as the service that processes the check. Contact Form 7, Gravity Forms, and WPForms appear in the paid add-on list; those still load the same Google script. Consent timing is not tested here.

Outside captcha servicewww.google.com, www.recaptcha.netNot assessedNot tested
Simple CAPTCHA with Cloudflare Turnstile

This row covers Simple CAPTCHA with Cloudflare Turnstile when Turnstile is enabled on a WordPress, WooCommerce, or listed form plugin form. Plugin source loads https://challenges.cloudflare.com/turnstile/v0/api.js in the visitor browser. Failsafe mode that falls back to reCAPTCHA is a different setup and is not this row. Consent timing is not tested here.

Outside captcha servicechallenges.cloudflare.comNot assessedNot tested

What this table does and does not prove

This table describes the named captcha setups. It does not show what loads on your site. An outside captcha widget can send visitor requests off your server even when it looks like a simple human check. We have not tested consent timing, and we have not assessed how long captcha-service logs are kept. The site scan linked below checks for third-party requests; it does not access your WordPress database.

Documentation snapshot: Sep 30, 2026. Sources are linked in each reviewed row.

Scan your site for third-party requests

/wp-captcha-plugin-privacy