Mint LabsMint Store Creditby Mint Labs

Security policy

Last updated October 6, 2026

This policy describes how Mint Labs protects the data Mint Store Credit 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. Store credit balances live in Shopify. The app stores a ledger of the credits it made (numeric customer ID, amount, currency, reason, the merchant's note, dates, Shopify's transaction ID), cashback orders by ID, cashback rules and settings. Customer names and email addresses are read from Shopify when a merchant looks at them and are never stored or logged.
  • Emails from an uploaded CSV are kept only until they're matched to a customer; unmatched rows are kept 30 days so the merchant can see what failed.
  • Money moves only through Shopify's store credit and refund APIs, on a merchant's action or their cashback rules. Each credit has a unique key in the ledger and is sent once; if Shopify doesn't answer, the app checks Shopify's transaction list instead of sending again. Refunds use Shopify's idempotency keys.
  • The storefront block is rendered by Shopify's Liquid from Shopify's own data; it calls no app endpoint.
  • 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; unsigned requests are rejected. Internal job endpoints only accept the Worker's own signed calls.

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 names, emails or anything merchants type.
  • 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