Mint LabsMint Stock Forecastby Mint Labs

Security policy

Last updated September 30, 2026

This policy describes how Mint Labs protects the data Mint Stock Forecast 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. The app never requests customers' names, email addresses, phone numbers, addresses, prices or payment details from Shopify. From orders it keeps only order and line item IDs, variant IDs, order dates, quantities and fulfilling locations, and deletes them after 60 days.
  • Order exports are streamed from Shopify's signed download links straight into the database and not kept as files. Customer erasure requests delete the named orders' lines and block them from being stored again.
  • 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 uses fictional sample data only.
  • Webhooks are verified with Shopify HMAC signatures, admin requests with Shopify session tokens; unsigned or invalid requests are rejected. Background jobs can only be started by the app itself (internal requests are signed with a key derived from the app secret).
  • The link in the digest email that turns the digest off is signed per store and can do nothing else.

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 stores' orders or 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 email addresses or order 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