Mint LabsMint Recently Viewedby Mint Labs

Security policy

Last updated October 6, 2026

This policy describes how Mint Labs protects the data Mint Recently Viewed handles, including 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. Shoppers' recently viewed lists stay in their own browsers and never reach us. The app stores the merchant's settings and, on Pro, anonymous counts between product IDs and daily row view/click totals — no customer or order records, no shopper names, emails, IP addresses or browsing histories.
  • Storefront reports are sent only from shoppers who allowed analytics (Shopify's Customer Privacy API), carry only product IDs and page types, and are accepted only through Shopify's signed app proxy. Each endpoint is POST-only, limits the body to 1 KB, validates every field, and is rate-limited per visitor (salted, daily-changing one-way hash of the IP address, never the address itself) and per store.
  • Storefront rows print shop data with Liquid escaping and build product cards with text nodes, so product data can never become HTML or script.
  • 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 and storefront requests are verified with Shopify HMAC signatures; unsigned or stale requests are rejected.

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, including requests that process personal data, is logged with a timestamp by our hosting provider's request logs. Our own log lines never contain anything about shoppers.
  • 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