Legal

Effective November 4, 2026

Security practices and cookie information for Max QR Code on getmaxqr.com.

In short

  • Traffic to the site, API, and redirects uses HTTPS.
  • Essential cookies power theme, sessions, and anti-abuse checks.
  • Report security issues to hello@getmaxqr.com.

Security

  • HTTPS everywhere. Website, API (api.getmaxqr.com), and redirect host (go.getmaxqr.com) use TLS.
  • Secrets. Supabase secret keys and API keys stay server-side. Rotate keys if they leak.
  • Least access. Staff do not browse customer QR projects by default. Exceptions: support you request, or investigation of abuse / illegal use.
  • Redirect integrity. Dynamic destinations are stored in our systems; keep account access tight so destinations cannot be changed without authorization.
  • Custom domains. Ownership is verified before a brand host serves redirects.

Report suspected vulnerabilities to hello@getmaxqr.com (subject: “Security”). Please give enough detail for us to reproduce the issue without exploiting third parties.

Cookies

We use cookies and similar storage for:

  • Essential. Theme preference, session / auth cookies when you sign in, and anti-abuse checks for guest generation.

We do not currently run a third-party analytics script on Max QR. If we add one later, this page and our Privacy Policy will be updated first. You can control cookies in your browser; blocking essential storage may break signed-in features. Privacy requests: Contact.

Questions about this page?

We usually reply within 2 business days.