SECURITY
Effective: September 18, 2026
Security matters on a store that handles accounts and purchases. This page explains how to report a suspected security issue and gives high-level information about our defensive approach without publishing sensitive configuration details.
Security measures
The Bacon Bin uses HTTPS, WordPress/WooCommerce authentication, access controls, server-side input validation, rate limiting, anti-spam controls, protected private-data directories and browser security headers on the custom storefront. Payment-card data entered into payment-provider fields is handled by the payment provider rather than intentionally stored in the custom storefront files.
Report a vulnerability
If you believe you found a security vulnerability, use our secure contact form and choose Website issue. Include the affected URL, a concise description, the steps needed to reproduce the issue, and any screenshots or logs that do not contain payment-card data, passwords or other people's sensitive information.
Good-faith reports
We appreciate good-faith reports that avoid privacy violations, service disruption and unnecessary access to data. We will review credible reports and prioritize them based on practical risk. This page is not a bug-bounty promise and does not authorize testing that would otherwise be unlawful or violate our Terms.
Account safety
Use a unique password, protect your email account, and contact us promptly if you believe your Bacon Bin account has been compromised. Never send us a password, full payment-card number, card security code or payment-provider secret key.