Mint LabsMint Sales Popupby Mint Labs

Security policy

Last updated October 7, 2026

This policy describes how Mint Labs protects the data Mint Sales Popup 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. From orders the app keeps only the order ID, time, test flag, up to 3 product IDs and (only if the merchant turns it on) the shipping country code, for 30 days at most. Order webhooks are limited to the order ID, and the app requests no customer, name, email, phone or address fields from Shopify. No shopper names, emails or IP addresses are stored or logged.
  • The storefront endpoints are GET only, accept only a product handle (letters, digits, "-" and "_") or a numeric product ID, never return order IDs, and are rate-limited per visitor (salted, daily-changing one-way hash of the IP address, never the address itself) and per store.
  • Product titles are shown in the storefront with text-only DOM methods; no product or merchant text is ever inserted as HTML.
  • 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 is logged with a timestamp by our hosting provider's request logs. Our own log lines never contain anything shoppers or 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