Last updated 14 November 2026.
Privacy notice
This notice covers Norse Subscriptions, a Shopify app, and this website.
Who we are
Norse Subscriptions is provided by Norse Suite. Privacy contact: support@norsesuite.com.
A Shopify merchant installs the app and decides how its subscriptions work. For subscriber data we act on the merchant's instructions. For our own merchant accounts, support and security we decide the purposes ourselves.
What we process and why
| Information | Why |
|---|---|
| Store domain, store name, store email, Shopify shop ID, settings, installation and plan status | Install and run the app and check the merchant's plan. |
| Plans, products, frequencies and widget design the merchant creates | Publish selling plans to Shopify and show them to shoppers. |
| Shopify customer ID, contract ID, status, delivery schedule (dates, skips, moves, pauses), a short summary of the items, amounts and currency | Show subscribers their own subscriptions, let the merchant manage them, and charge deliveries the merchant has enabled. |
| Records of charges: date, status, attempt number, error code and what was on the delivery | Avoid charging twice, follow up failed payments and show history. |
| Records of actions (pause, skip, move, cancel, edit, discount request, cancellation reason), the source of the action and, for merchant actions, a pseudonymous staff identifier | Show history, prevent a repeated action and investigate problems. |
| Sign-in links and action tokens, stored only as keyed hashes with their expiry (at most 60 minutes for sign-in links) | Let a subscriber sign in without a password and make each action single-use. |
| Email address the subscriber types in the portal | Find the matching Shopify customer. It is not stored. A sign-in email goes to that address. |
| The customer's email address and language from Shopify | Send the emails about the subscription. The address and the message are held encrypted in a queue until the message is sent, expire after 23 hours, or the customer is erased. |
| Customer name and email from Shopify | Show the merchant who a subscription belongs to, and let the merchant search and export. Read when shown and not stored. |
| Delivery address, name and phone from the subscription | Show them to the subscriber and update them if the subscriber chooses to. Read from Shopify when needed and not stored. |
| Card brand, last four digits and expiry, if the merchant has given this access | Show them to the subscriber and warn before a card expires. Read from Shopify. They are in the text of the expiry email while it is queued. We never read a full card number or a security code. |
| Order ID and order name from Shopify | Link a subscription or a delivery to its order for the merchant. Read when shown and not stored. |
| A file the merchant uploads when moving from another app: subscription details, name, email and address | Create new subscriptions in this app. Held encrypted, and removed when the merchant completes the move, at most 30 days after upload. |
| Customer ID and email from a Shopify data request | Recorded, encrypted, so the merchant can answer the request. Overwritten when the customer is erased. |
| Daily recurring-revenue totals | Show analytics to the merchant. They contain no customer identity. |
| Merchant contact details and support messages | Provide support. |
| Server and error logs | Keep the service running. They are designed not to contain customer contacts or request bodies. |
We do not sell personal data, use it for advertising or profile subscribers. Payments are handled by Shopify.
Who receives data
Always: Shopify, and our providers for hosting (Vercel), database (Neon) and email (Resend). The email provider receives the recipient address and the full text of each email. The hosting provider keeps request logs, which can hold the address of a request: a customer's email address when the merchant's Gorgias looks them up, and the keys in a customer's personal links.
Only if the merchant turns it on, to the merchant's own destination:
| What the merchant connects | What is sent |
|---|---|
| Klaviyo | The customer's email address, and facts about the subscription: subscription ID, event, dates, attempt number, interval, item title, reason code. |
| Omnisend | The same as Klaviyo: the customer's email address and the same subscription facts. |
| Klaviyo campaign links | Personal links to the customer's subscription page, written to the customer's Klaviyo profile by email address, for the merchant's own campaigns. Each link lets the holder open the page and, after confirming, skip the next delivery or add one product to it, for up to 7 days. Klaviyo creates a profile if it has none for that address. When the customer has no active subscription left, the links are removed from the profile. |
| Gorgias | When the merchant's support opens a ticket, Gorgias sends the app the customer's email address, and the app answers with that customer's subscriptions: number, status, products, rhythm, next delivery, usual amount, a payment problem in words, and a link to the subscription in Shopify admin. Support agents can skip, pause or cancel from there. No name, address or card details. |
| Webhooks to the merchant's own system | The Shopify customer ID, and the same facts. No name or email. |
| Partner API, called from the merchant's own server | The customer's subscriptions, and on request their name, delivery address, phone, card brand, last four digits and expiry. No email. |
| A hidden copy of customer emails | A copy of each email to an address the merchant chooses. |
| Shopify Flow | Customer ID, subscription ID and, depending on the event, delivery dates, rhythm and reason code, inside Shopify. Workflows the merchant builds can also change a subscription through the app's Flow actions. |
The merchant decides what happens to that data once it has received it. If a customer is erased here, no further events about them are sent, but we cannot recall what was already delivered.
How long we keep it
The merchant's data is kept while the app is installed. When a merchant uninstalls, queued emails are cleared at once, Shopify sends a shop erasure request after 48 hours, and we then delete the store's data. When a merchant asks Shopify to erase a customer, we delete that customer's tokens, queued messages and import data, and remove the customer's identity from subscription and action records. We keep totals that do not identify the customer.
Expired sign-in links are deleted 30 days after they expire. Finished email records, which hold no address or text, are deleted after 180 days. Import data is removed at most 30 days after upload. Queued emails expire after 23 hours. Action records and ended subscriptions stay until the app is removed or the customer is erased.
Security
Store access tokens, webhook secrets, connected service keys, queued messages, import files and data-request identities are encrypted with AES-256-GCM in the application. Sign-in links and API keys are stored only as keyed hashes. Webhooks and storefront requests are verified with Shopify's signature. Every query is limited to the store. We do not claim that all data is encrypted in the application or that any compliance certification is held.
This website
norsesuite.com sets no cookies and loads no analytics or tracking scripts. If you write to us, we use your message and email address to answer you.
Your rights
A subscriber should contact the store first. We help the merchant with access, correction, deletion and other requests. Requests about our own processing go to support@norsesuite.com. You may complain to your supervisory authority, in Norway the Norwegian Data Protection Authority (Datatilsynet).
Changes
We will date material changes at the top of this page.