How we protect your data
This page describes the security measures built into QRCode Suite, each as it works today. If something you observe does not match what is written here, please tell us through the contact form.
Passwords
Passwords are hashed with bcrypt at a cost factor of 12 and are never stored in readable form. A new password must be 12 to 128 characters long, is refused if it is on a list of very common passwords, and is checked against the Have I Been Pwned breach database through its range API, which only ever receives the first five characters of the password’s SHA-1 hash. Signing in takes the same time whether or not an email address is registered, so the form cannot be used to find out who has an account.
Sign-in from a new device
When you sign in with your password from a browser we do not recognise, we email you a 6-digit code before opening the session. The code expires after 10 minutes and only a keyed hash of it is stored. Once confirmed, that browser is trusted for 90 days. Sign-up, sign-in and password reset also require a Cloudflare Turnstile check against automated attempts.
Sessions
A session lasts 30 days without activity and is renewed while you use the dashboard. Your account status is read again from the database on every dashboard page, so a disabled account loses access on its very next request.
Rate limiting
Sign-in, sign-up, password reset, email verification, the contact form, license activation and QR code redirects all limit how many requests can be made in a given window, counted per IP address or per account. The counters behind these limits are deleted automatically once their window has passed.
License keys and API keys
License keys and API keys are stored only as HMAC-SHA-256 hashes computed with a server-side secret. The dashboard shows only the start of a license key and its last four characters, never the full key.
IP addresses
The application stores IP addresses only in hashed form. Scans, link clicks, sign-in checks and the counters that rate-limit sign-in and stop abuse keep at most a keyed HMAC-SHA-256 hash derived from the address, cut to 32 hexadecimal characters, never the raw address. Bot traffic is detected and left out of your scan counts.
Stored secrets
Webhook signing secrets, integration credentials and the email addresses collected by Link Hub forms are encrypted in the database with AES-256-GCM.
Webhooks
Every webhook we send carries an HMAC-SHA-256 signature of its exact body in the X-QRCS-Signature header, so your endpoint can verify that it comes from us. Payment events from Stripe are rejected unless their signature checks out.
Payments
Card details are entered on Stripe Checkout and in the Stripe customer portal. They never reach our servers, and we store no card numbers.
Plugin downloads
WordPress plugin download links are signed and expire after 15 minutes. Each plugin release is stored together with its SHA-256 checksum.
Browser protections
- Our pages cannot be embedded in frames on other sites (X-Frame-Options: SAMEORIGIN).
- Browsers are told not to guess file types (X-Content-Type-Options: nosniff).
- Links to other sites send only our domain as the referrer (Referrer-Policy: strict-origin-when-cross-origin).
- Access to the camera, microphone and location is switched off for our pages (Permissions-Policy).
Vulnerability reporting
Report a vulnerability through the contact form. Please include steps to reproduce and the affected URL.