hoop Loyaltyby Hoop Interactive LLC

Security

Last updated: 17 November 2026

Encryption in transit

Every connection between browsers, Shopify and hoop Loyalty uses HTTPS (TLS). The app and its database talk over our hosting provider's private network, which is not reachable from the internet.

Encryption at rest

  • Each store's Shopify access token (and refresh token) is encrypted with Fernet (AES with an HMAC check) before it is saved.
  • API keys for email providers a merchant connects (Resend, Klaviyo, SendGrid) are encrypted the same way.
  • A referring shopper's email is encrypted; a referred friend's email is kept only as a one-way keyed hash.
  • The encryption key is kept outside the database, and keys can be rotated without downtime.

Checking every request

  • Webhooks from Shopify are accepted only with a valid Shopify HMAC signature. The store is taken from the signed content, never from a header alone.
  • Storefront requests come through Shopify's App Proxy and are accepted only with a valid Shopify signature.
  • The merchant admin is accepted only with a session token signed by Shopify for that store's admin.
  • Checkout and customer account blocks use Shopify-signed session tokens; shopper actions need a signed-in shopper.
  • Requests are rate limited per store.

Each store sees only its own data

Every record is tied to one store, and every query the app makes is limited to the store the signed request belongs to. One store can never read or change another store's members, points or settings.

Only the permissions we need

We ask Shopify only for the permissions the features use: reading orders and customers to give points, writing discounts to create reward codes, writing customer data for birthdays, store credit where the merchant turns it on, and reading products and themes for points on product pages and widget setup. Payments are handled by Shopify; we never see card details.

Who at Hoop Interactive LLC can access data

Only a small team that runs and supports the app can reach production systems, using secret keys that are never shared outside that team. Changes our team makes from our internal tools, such as plan changes, are written to an audit log.

Hosting and backups

The app and its MySQL database run on Railway in the United States. Backups are limited to what Railway provides for that database; we do not promise more than that. See Subprocessors.

How deletion works

  • Uninstall: Shopify sends a shop deletion request 48 hours after a merchant uninstalls. We delete everything we hold for that store 30 days after the uninstall, unless the merchant reinstalls first. This includes members, points history, rewards, orders, settings, and the store's messages and ideas sent to us.
  • A shopper's erasure request (customers/redact) is carried out as soon as it arrives: their balance, birthday, rewards and VIP history are deleted, and their identity is removed from the points history and orders.
  • Earlier deletion: a merchant can email hi@hoopinteractive.com from the store's contact email to ask us to delete their store's data sooner.

If something goes wrong

If we become aware of a breach affecting personal data, we will tell the affected merchants without undue delay and within 72 hours, with what we know and what we are doing about it, as set out in our Data processing addendum.

Report a security issue

Found a security problem? Email hi@hoopinteractive.com with the details. Please do not test against stores you do not own. We will reply within 1 business day.