Privacy policy

Scope and publisher

This policy covers checkoutfirewall.com and Checkout Firewall for WooCommerce, published independently under the Codeprint name without a separate incorporated legal entity. A merchant using the plugin remains responsible for its store’s own privacy notices, lawful basis, retention choices, and responses to shoppers.

This website

The website does not currently provide accounts, accept form submissions, run advertising pixels, or intentionally set analytics or advertising cookies. Hosting and security infrastructure may process ordinary request data such as IP address, user agent, requested URL, timestamps, and error or security events to deliver, secure, and troubleshoot the site. We retain operational data only as reasonably necessary for those purposes and provider obligations.

Plugin data stored on the merchant’s site

Checkout Firewall processes keyed IP, billing-email, session, and combined identifiers; masked hints; aggregate Activity records; temporary blocks; configuration; health state; and optional trusted exemptions. An exact IP is keyed immediately; a narrow CIDR must remain readable to match the network; an authenticated-user exemption stores the local WordPress user ID. A temporary keyed payment-feedback snapshot may be attached to an order. Checkout Firewall never reads, stores, logs, hashes, or transmits card numbers, CVCs, or gateway payment payloads.

Purposes and retention

Local data is used to detect repeated checkout abuse, explain interventions, recover legitimate shoppers, operate notifications, and troubleshoot the plugin. Activity and terminal blocks are retained for 1, 3, or 7 days; masked block hints for 7, 30, or 90 days. Premium intervention analytics may be retained for up to 90 days while entitled. Recorded payment success or failure deletes temporary order feedback immediately; otherwise Activity retention bounds it.

External services

Free protection works locally without a Codeprint account. If an administrator explicitly connects Freemius, licensing and update data may include administrator name and email, site URL, plugin and SDK versions, installation/license identifiers, and local/premium/activation state. Checkout Firewall disables Freemius site-profile, diagnostic, extension-inventory, and newsletter permissions. See Freemius Privacy and Terms.

If a merchant selects and configures Cloudflare Turnstile or Google reCAPTCHA, that provider loads only when local signals require a challenge. It may process browser and network signals. Server verification sends the response token and merchant secret, omits the optional shopper IP, and sends no payment details. See the Turnstile Privacy Addendum, Cloudflare Terms, Google Privacy Policy, and Google APIs Terms.

Choices, access, and deletion

Administrators can use the local challenge and skip the Free Freemius connection. WordPress personal-data erasure removes directly email-attributable plugin records. Uninstall preserves plugin data by default so an accidental removal does not erase incident evidence; an administrator may explicitly enable full deletion before uninstalling. The local support snapshot is not uploaded and excludes store/customer identity, orders, gateways, credentials, tokens, requests, logs, and raw errors.

Security, transfers, and changes

Checkout Firewall uses data minimization, keyed identifiers, masked hints, capability checks, bounded retention, and encrypted Premium webhook credentials. No system is perfectly secure. External providers may process data in other countries under their own policies. Material changes to this policy will be dated on this page.

Questions and rights requests

Email jacob@codeprint.io. Do not put personal data or vulnerability details in a public issue. Depending on applicable law, individuals may have rights to access, correct, delete, restrict, object to, or receive a copy of personal data.