PIPL
Self-hosted design that supports PIPL requirements.
Scope
Self-hosting provides control over data residency and processing scope. Optional external lookups should be evaluated for cross-border transfer rules.
This page maps SCaptcha 2.3.0 behavior to the named framework. It is not a certification or legal advice.
Localization and transfer control
SCaptcha can be deployed entirely within your China-based infrastructure to meet localization expectations.
There are no default data transfers to external CAPTCHA providers.
Minimization and consent
The widget avoids tracking cookies and does not require personal data to verify users.
If you enable Under-Attack Mode or Sentinel logging, describe the purpose in your notices.
Third-party considerations
Proxy intelligence is optional and sends IP data only if enabled.
Review any external vendors against PIPL requirements and update documentation accordingly.
Implementation checklist
Keep logging minimal, store data locally, and review retention periods.
Disable external lookups unless they are necessary and documented.
SCaptcha 2.3.0 behavior
Each challenge uses its own cryptographically random 32-byte salt. Your WoltLab installation validates the salt, hash, algorithm, answer, and HMAC against the issuing session. The challenge expires after 60 seconds and does not require an external CAPTCHA provider.
This option is off by default. If you enable it, SCaptcha sends the visitor's public IP address to proxycheck.io for proxy, VPN, or Tor evidence. SCaptcha 2.3.0 sends tag=0 by default; administrators can opt in to provider logging. The IP address is transmitted for every lookup either way.
A pre-submit marker and the optional text/audio proof are valid for 5 minutes. Under-Attack mode uses a signed, user-agent-bound access cookie for 5 to 30 minutes; the default is 10. Sentinel can store a server-side rejection in a separate signed cookie for 10 minutes. Sentinel itself is off by default.
Request analytics are on by default. Logs can contain linkable operational data, including IP address, user agent, request, network and location fields, reasons, and submitted browser telemetry. Retention defaults to 90 days and can be set from 1 to 3,650 days. Turning analytics off stops new collection but does not erase existing rows or exports.
What operators need to review
Document enabled features, limit access to security logs, and assess optional external services separately. SCaptcha does not replace legal review or accessibility testing of the complete website.
Enable only the options you need. Update privacy and cookie notices, restrict access to analytics and logs, and test the actual form integration before launch.