Security policy

Last updated October 6, 2026

This policy describes how Mint Labs protects the data Mint Custom Reports handles, including any personal data of merchants' customers processed on behalf of 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 reads orders, refunds, products and stock to calculate reports and never writes to the store. About the merchant's customers it keeps only Shopify's numeric customer ID with Shopify's order count, amount spent and account creation date: no names, emails, phone numbers or addresses are requested, stored, logged or emailed.
• Reports are calculated from fixed, reviewed SQL building blocks chosen by ID; every value a merchant types (filters, dates, numbers) is passed as a bound parameter, so report settings can't change a query or reach another store's data. Every query is scoped to the authenticated store.
• Downloads and email attachments are built so spreadsheet programs never run their contents as formulas. Scheduled emails go only to addresses the merchant entered, and every email has a signed link that stops that schedule.
• 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 requests with Shopify session tokens; unsigned requests are rejected. Internal background endpoints accept only calls signed with a key derived from the app secret.

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.
• 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. Our own log lines never contain customer data, email addresses or report contents.
• 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