PRIVACY CAPTCHA FOR CAP
Privacy CAPTCHA for Cap compatibility with REEID Translate
Privacy CAPTCHA for Cap compatibility with REEID Translate is being evaluated from available plugin evidence. Self-hosted proof-of-work CAPTCHA integration for multiple WordPress security surfaces (comments, wp-login, registration, WooCommerce checkout/My Account login/registration/lost-password, and Gravity Forms). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Privacy CAPTCHA for Cap.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Privacy CAPTCHA for Cap is documented in the Security category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Privacy CAPTCHA for Cap compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Self-hosted proof-of-work CAPTCHA integration for multiple WordPress security surfaces (comments, wp-login, registration, WooCommerce checkout/My Account login/registration/lost-password, and Gravity Forms).
- Cap server token verification against a user-provisioned endpoint (requires a reachable Cap server; plugin verifies tokens against the configured Cap server).
- Granular enable/disable controls via per-surface toggles and developer filters (e.g., `cap_captcha_protect` and `cap_captcha_protect_{context}`) to gate protection before widget rendering and before submission verification.
- Fail-open behavior when the Cap server is unreachable (off by default; can be enabled per form/surface; submissions accepted via fail-open are flagged with a `cap_captcha_fail_open` marker and related notes).
- Gravity Forms field integration with per-form display-mode/placement behavior for multi-page forms (auto-injected field placed on the last page by default; can be moved with `cap_captcha_gf_field_page`; TTL for solved challenges configurable via `cap_captcha_gf_verified_ttl`).
- Fully local/bundled widget assets for the proof-of-work challenge (WASM module and widget scripts served from the plugin by default; widget makes network requests only to the configured Cap endpoint for challenge/verification).
- Developer extensibility for asset URL overrides and UI behavior (filters to override widget/floating/programmatic sources, style sources, WASM/pako URLs, i18n strings, and floating-mode parameters).
CONTENT BOUNDARY
Privacy CAPTCHA for Cap capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Privacy CAPTCHA for Cap and REEID Translate FAQ.
What does Privacy CAPTCHA for Cap do according to the available plugin evidence?
Privacy CAPTCHA for Cap has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Privacy CAPTCHA for Cap?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Privacy CAPTCHA for Cap?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Privacy CAPTCHA for Cap in a multilingual WordPress workflow.
REEID documents Privacy CAPTCHA for Cap functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.