Security policy
Last updated October 6, 2026
This policy describes how Mint Labs protects the data Mint 404 Redirects handles for merchants. It applies to everyone at Mint Labs with access to our systems.
Data loss prevention
- We keep as little data as possible. The app stores no personal data about shoppers: the 404 log holds storefront addresses without query strings, visit counts and referring website names. A visitor's network address is only used, as a keyed one-way hash, by a rate limiter while a report is processed, and is never stored or logged.
- Merchant data (redirect history, settings, catalog handles and titles) is limited to what the features need and deleted on the schedule in our privacy policy; everything is deleted after uninstall.
- The redirects themselves live in the merchant's Shopify store, so they are never lost if our service is unavailable.
- Our database is Cloudflare D1: encrypted at rest, with point-in-time recovery so it can be restored to any minute in the retention window.
- All traffic uses HTTPS (TLS). Production and development use separate databases; development never uses real merchant data.
- Webhooks and storefront reports are verified with Shopify HMAC signatures; unsigned or expired requests are rejected. The report endpoint accepts JSON only, limits size, filters bots, and limits reports per connection, per store and per day.
Access control
- Only authorised Mint Labs personnel who need it to run and support the app can access production systems.
- The app has no internal screen that lets us browse customers' personal data.
- Access is removed immediately when it is no longer needed.
Passwords and authentication
- Every account with access to production (hosting and Shopify Partner) uses a strong, unique password stored in a password manager.
- Two-factor authentication is required on all of those accounts.
- API secrets are stored as encrypted environment secrets, never in source code, and are rotated after any suspected exposure.
Logging
- Every request to the app is logged with a timestamp by our hosting provider's request logs. The app's own logs never contain network addresses or other personal data.
- Logs are reviewed when investigating errors or suspected incidents.
Security incident response
- Report. Anyone can report a suspected issue to support@stickermint.com. We acknowledge reports within one business day.
- Contain. We stop the exposure first: disable the affected feature (for example the 404 report endpoint), revoke and rotate keys and access tokens, and block abusive traffic.
- Investigate. We use request logs and database history to find what happened, which shops and data were affected, and when.
- Notify. If personal data was affected, we notify affected merchants without undue delay and within 72 hours of confirming the incident, and tell Shopify where required, with what happened and what we are doing about it.
- Recover. We fix the root cause and, if needed, restore data from point-in-time recovery.
- Review. We record each incident and the lessons learned, and update this policy.
Contact
Mint Labs — support@stickermint.com