Security policy

Last updated September 30, 2026

This policy describes how Mint Labs protects the data Mint Age Check handles, including any personal data of merchants' customers processed on behalf of merchants (by design, the app handles none). It applies to everyone at Mint Labs with access to our systems.

Data loss prevention

• We keep as little data as possible: the merchant's settings, plan and publish status. The app stores no data about the merchant's shoppers — no birth dates, ages, answers, IP addresses, visitor IDs, names or email addresses.
• The storefront script makes no requests to our servers. A date of birth typed into the check is used in the shopper's browser and never sent anywhere; the answer is kept only in a first-party cookie on the shopper's device. The optional checkout confirmation runs inside Shopify's checkout as a Shopify Function without network access, so checkout data never reaches our servers either.
• 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 or customer data.
• Webhooks are verified with Shopify HMAC signatures and admin pages with Shopify session tokens; unsigned or tampered requests are rejected. The app has no public endpoint that accepts data from shoppers.

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 merchants' data, and holds no shoppers' personal data to browse.
• 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. Shoppers' browsers never call the app, and logs never contain shoppers' data.
• Logs are reviewed when investigating errors or suspected incidents.

Security incident response

1. Report. Anyone can report a suspected issue to support@stickermint.com. We acknowledge reports within one business day.
2. Contain. We stop the exposure first: disable the affected feature, revoke and rotate keys and access tokens, and block abusive traffic.
3. Investigate. We use request logs and database history to find what happened, which shops and data were affected, and when.
4. 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.
5. Recover. We fix the root cause and, if needed, restore data from point-in-time recovery.
6. Review. We record each incident and the lessons learned, and update this policy.

Contact

Mint Labs — support@stickermint.com