Boomrrang Privacy Policy
Effective date: 2 September 2026
Last updated: 14 November 2026
Applies to: the Boomrrang subscriptions application for Shopify and the websites at
boomrrang.com, auth.boomrrang.com, hooks.boomrrang.com and {shop}.boomrrang.com.
1. Who we are, and the role we play
Boomrrang is a subscriptions application for Shopify, operated by Leds Get It LLC, a United States limited liability company formed under the laws of Wyoming, with registration details available on request from legal@boomrrang.com ("Boomrrang", "we", "us").
Understanding who decides what happens to personal data is the most important thing in this policy, because it determines whom you should contact and whose rules apply.
When a Shopify merchant installs Boomrrang, the merchant is the data controller and Boomrrang is the data processor. The merchant decides which subscribers exist, what they are billed, and what happens to their data. We process that data only on the merchant's documented instructions — which, in practice, means the actions the merchant's staff take inside the app, the configuration they choose, and the terms of our agreement with them. We do not decide the purposes of that processing, we do not use subscriber data for our own purposes, and we do not sell it.
There is one narrow exception. For the merchant's own staff accounts, and for our marketing site, we act as a controller — we decide, for example, how long to keep an app session, how to authenticate a staff member, and how to secure our own service. Those decisions are ours, and this policy is our disclosure of them.
| Data | Controller | Boomrrang's role |
|---|---|---|
| Subscriber (end-customer) data inside a merchant's shop | The merchant | Processor |
| Merchant shop configuration and access tokens | The merchant | Processor |
| Merchant staff identity and app sessions | Boomrrang | Controller |
| Security, audit and diagnostic records about our own service | Boomrrang | Controller |
If you are a shopper with a subscription: your relationship is with the store you bought from, not with us. The fastest way to exercise your rights is to contact that store directly — it can act immediately, and Shopify's own privacy tooling will reach us automatically. You can also write to us at privacy@boomrrang.com and we will route your request to the merchant and support them in answering it, but we cannot act on subscriber data without the merchant's instruction except where the law requires us to.
2. What this policy covers
This policy covers personal data processed by the Boomrrang application and its supporting infrastructure. It does not cover:
- Shopify itself. Shopify is an independent controller of the data in a merchant's store. See Shopify's own privacy policy.
- The merchant's storefront, checkout, or customer accounts. Those are the merchant's and Shopify's, not ours.
- Payment processing. We never touch it (see §4).
3. What we collect, and why
We hold three distinct populations of data. They are listed separately because they have different sources, different legal bases and different retention.
3.1 Merchant shop data (we are a processor)
Collected when a merchant installs the app, and kept current from Shopify webhooks and API reads.
| Data | Source | Why we hold it |
|---|---|---|
Shopify shop domain (e.g. example.myshopify.com) and the tenant subdomain we derive from it |
Shopify OAuth | To identify the tenant and isolate it from every other tenant |
| Shop name, contact email, country, currency, Shopify plan name | Shopify Admin API | To display the shop correctly, format money, and support the merchant. The contact email is the store owner's address on the store's Shopify account: the store's alerts go to it, and it is the reply-to address and the contact named in the footer of the emails we send to the store's subscribers, so those subscribers see it |
| Shopify shop identifier (GID) | Shopify | Stable key that survives a domain rename |
| Offline access token, encrypted | Shopify OAuth | Lets background billing and webhook work continue when no one is logged in. Stored as AES-256-GCM ciphertext, never logged, never returned to a browser |
| Granted OAuth scopes | Shopify OAuth | So the app can tell what it is permitted to do and re-prompt if scopes change |
| Install and uninstall timestamps | Our system | Drives the deletion clock described in §9 |
| The merchant's flows (§6, §14): each one's name, what starts it, its conditions and its actions, and every version of them it saved — with the text and codes the merchant types into them, such as a discount code, a customer tag, a custom attribute's value or the message of an email to its own team | The merchant, in the app | To run each flow as the merchant set it, and to show which version of it ran. These settings are the merchant's own words: they name a subscriber only if the merchant types one in — a subscriber's own discount code, say — and a draft made from the previous app's automations asks for a discount code seen on fewer than five subscriptions only if it is a code for the whole store (§3.3a). Each saved version is kept for the life of its flow, which deleting the flow does not end, until the shop's data is deleted (§9). It is linked to no subscriber, so a subscriber's erasure request (§11.3) does not reach it |
3.2 Merchant staff data (we are the controller)
Collected when a member of the merchant's Shopify staff opens the app. We never collect or store a password — see §10.2.
| Data | Source | Why we hold it |
|---|---|---|
| Shopify staff user id | Shopify OAuth (associated_user) |
The authoritative identity we bind an account to |
| Email address (lowercased) | Shopify OAuth | Initial match key for an invitation, and how we contact a staff member |
| First and last name, locale | Shopify OAuth | To show who did what in the app, and to render the UI in the right language |
| Whether the person is the account owner or a Shopify collaborator | Shopify OAuth | Affects what they may do, and protects the last remaining administrator |
| Membership: which shop, which role, status, who invited them, when they were last seen | Our system | Access control and the ability to answer "who had access, and when?" |
| App session: an expiry, a hash of the session cookie value, a hash of the IP address, and the browser user-agent string | Our system | To keep a staff member logged in, to expire sessions, and to investigate suspicious access. We store a hash of the session token and a hash of the IP address, not the values themselves |
| Short-lived, single-use handoff and OAuth state codes, stored as hashes | Our system | To carry a login securely across host boundaries and to prevent CSRF on the OAuth round trip |
3.3 Subscriber data (we are a processor for the merchant)
This is the data of the merchant's customers who hold a subscription. We hold deliberately little of it. See §4 for what we refuse to hold and why.
| Data | Source | Why we hold it |
|---|---|---|
| Shopify customer identifier (GID) | Shopify | The key that links a subscription to a person, without storing the person |
| Subscription contract: Shopify contract id, status, currency, delivery interval, billing interval, next billing date, and the delivery country (two letters, no other part of the address) | Shopify Subscription APIs | To show and manage the subscription, and to schedule billing. The delivery country is shown with the subscription (in the merchant's subscription list, on its page, in the customer portal and in the merchant's export), counted in the payment-recovery figures by country, checked by a flow with a delivery-country condition, and, for a subscription billed in another currency than the store's, sent to Shopify to read the store's price of a product for a buyer in that country when a flow sets a price (§7.1) |
| Contract lines: product and variant identifiers, product title, quantity, current price | Shopify | To show the merchant what is on the subscription |
| Customer email address | Shopify | So the merchant's subscription list can show which subscriber a contract belongs to, and so the subscriber can sign in to the customer portal by entering that address, without the app running a customer search against the merchant's store on either occasion. It is read from Shopify once when a contract is first recorded (or moved to another customer) by the app's own background process, and every such read is logged. Transactional email of ours — the subscription confirmation, a restarted subscription's confirmation, the customer portal's sign-in link, whether the subscriber asks for it or the merchant's staff send it — is addressed using the customer's current address fetched from Shopify at the time of sending, not from this stored copy. Payment-failure notices are not sent by us: where the merchant's store has approved it, the app asks Shopify to email the subscriber a secure link to update or add the payment method on their subscription, and Shopify sends that email to the address it holds without our reading it (§7.1) |
| Billing cycles and billing attempts: due date, state, attempt outcome, Shopify order id, error code and error message | Our system and Shopify | To bill on schedule exactly once, to retry correctly after a failure, and to let the merchant see why a charge failed |
| Subscription tags: which of the merchant's subscription tags we last put on each subscriber's customer record in Shopify, and which we added to each subscription order, by the Shopify customer and order identifiers | Our system | So that each tag is added and taken off once, as the merchant has set them, and the merchant can see what is waiting (§7.1). The tags are the merchant's own words for where a subscription stands, such as "Active Subscriber"; to keep them, we never read a customer's or an order's other tags (a flow the merchant sets up may check a customer's tags, as the next row says) |
| The record of the merchant's automations ("flows") on each subscription: which of the merchant's flows looked at what happened to the subscription and whether its conditions held — results, not the values checked — and, for each flow that ran, when, what it changed (products, quantities, prices and discounts by their identifiers, the next order, tags the merchant chose, a pause or a cancellation) and how it ended, with the Shopify identifier of the order involved; for each event a flow acted on, a marker naming the event, with the identifier of the run and its time; and, for a flow set to run once on each subscription or on one of its orders, a marker that it has run there | Our system | So that each flow runs once for each event, as the merchant set it, its changes are made exactly once, and the merchant can see what each flow did and why (§6, §14). To check a flow's conditions, the app may read from Shopify, when the flow runs or the merchant's staff test it on that subscription, a subscriber's customer tags, the subscription's custom attributes and the products of the order that started it; each is compared with the merchant's condition and dropped, and only whether the condition held is kept |
| Compliance request records: the shop's domain, the Shopify customer id and any order ids named in a Shopify privacy webhook, a hash of the payload, and the request's status and times | Shopify privacy webhooks | To prove we received and completed an access or erasure request — including a shop/redact request, whose record outlives the shop it erased (§9) |
Read on demand, not stored. To display a subscriber's name and shipping address, the app fetches them from Shopify at the moment they are needed and discards them when the page is rendered. They are not written to our database — except as part of data a merchant moves from a previous subscriptions app (§3.3a). In the same way, for a member of the merchant's staff who may see subscriber details, a subscription's page fetches from Shopify any custom properties on the subscription's products — text entered at checkout, such as a gift message or an engraving, which can name a person — when the page opens, shows them, and never stores them. Every such read writes an entry to our PII access log (§10.6) recording who read what, when, and why.
The merchant's staff in the customer portal. Where the merchant turns it on, a member of the merchant's staff who may see subscriber details and manage subscriptions can open a subscriber's customer portal from the app, for one subscription and for at most 15 minutes, to view it and act on it on the subscriber's behalf. Each opening is logged, and what they change there is recorded under the staff member's name, not the subscriber's.
3.3a Data a merchant moves from a previous subscriptions app (we are a processor)
A merchant moving to Boomrrang from another subscriptions app can instruct us to bring across what that app holds about the merchant's subscriptions and subscribers. The merchant gives the instruction in the app's migration console and grants the access itself, with a read-only key it generates in the previous app; we read only what that app makes available to the merchant through it.
We keep that data whole, as the previous app returned it. Moving a store must not lose its history, so we do not cut it down to what our app uses today. Depending on what the previous app holds and the access the merchant grants, it can include: subscribers' names, email addresses and phone numbers; shipping and billing addresses; subscriptions, active and ended, with their products, quantities, prices, discounts, frequencies, dates, pauses, skips and reschedules; order history and upcoming scheduled orders; payment attempts and their outcomes, including the payment provider's decline message; notes, tags and custom attributes (on an order, these can name the person a gift is for and carry the giver's message); cancellation reasons and the comments subscribers left; payment-method display details (card brand, last four digits and expiry — never a card number, a security code or bank details, which such apps do not release and we do not request); loyalty balances; gift subscriptions, including the name and delivery address of the person a gift is sent to; and the previous app's own identifiers, timestamps, settings and activity records — which can name the member of the merchant's staff who made a change, by the email address that app recorded. We also record when each item was read and how it maps to the records our app made from it. One setting is cut down before it is kept: the web address the previous app sent its notifications to keeps only its scheme, host and path, since the rest of it can carry a password or key.
Customer records are kept for customers who had a subscription. Of the store's customers that app lists, we keep only those who ever held a subscription with it: we read the details of the customers of the subscriptions the merchant moves, and of the buyers of its gift subscriptions, and nothing of any other customer — not that app's list of the store's customers, nor the record of a customer who never subscribed. Such a customer has no subscription history there, and Shopify already holds their name and contact details. We keep every customer that app lists only when the merchant runs its loyalty programme — whose points, credit, coupons and rewards the merchant must honour for each customer who has them, which the details we read show — or the merchant asks us to. We do not read that app's copy of the store's products, which Shopify holds, nor its second copy of each subscription in each customer's own list of them.
The subscriptions are read first. The rest of what that app holds — the store's history — is read afterwards in the background, when the merchant asks for it, and read once more for what changed after the merchant stops the previous app. Each item is linked, where the previous app's data allows, to the subscriber it concerns, so the rights below reach it; a gift's delivery details are part of the gift subscription of the subscriber who bought it.
| Purpose | What it involves |
|---|---|
| Recreating the merchant's subscriptions | Each live subscription becomes a Shopify subscription contract with the same products, prices, frequency, dates and delivery address |
| Keeping the merchant's history | Ended subscriptions and past orders are kept for the merchant, so they can be shown to it and an ended subscription restarted on its previous terms at the subscriber's or the merchant's request |
| Reconciliation and support | Proving what the previous app held, what was brought across and how each record maps to ours, and answering the merchant's questions about the move |
| The merchant's later use of its own history | Reports and features in the app that use the full history the merchant moved |
| Recreating the merchant's automations | The automations the previous app ran on the merchant's subscriptions are worked out from its activity records, inside our database and shared with no one, as part of the move the merchant started: for each, its name and how often and how well it ran, and, only where it ran on at least five subscriptions, when it ran and what it appeared to do — a discount code kept only where it was seen on at least five subscriptions — so the merchant can review each as a draft of its own flow, which does nothing until the merchant turns it on (§6). Nothing about any one subscriber is kept of them: a discount code they removed on fewer than five subscriptions may be one subscriber's own, so it is not kept, and the draft asks the merchant to type it only if it is a code for the whole store — what the merchant types is kept with the flow's settings (§3.1) |
It is held only for the merchant that moved it, is available only to that merchant (its staff, according to their permissions), and is covered by subscribers' rights exactly as the rest of §3.3 (§11.3): an erasure request removes the subscriber's personal data from it, and an access request includes it.
3.4 Operational and security data (we are the controller)
- Event ledger. Every state-changing operation appends an immutable record: which shop, who acted, what kind of thing changed, which record, and a request id. This ledger is required by design to be free of personal data — it stores identifiers, never names, emails or addresses.
- PII access log. Every read of subscriber personal data: shop, acting user, what was read, which fields, and the stated reason.
- Webhook receipts. For each webhook Shopify sends us: its id, topic, shop domain, API version, a hash of the payload, and processing state. The hash lets us prove we handled a specific message and detect duplicates without retaining its contents.
- Application logs and error reports. Structured logs and crash reports, passed through a redaction layer before they leave the process (§10.5).
- Operations telemetry. Our servers report to an internal operations dashboard — our own
tool for running the apps we operate, hosted for us by Vercel with its database on Supabase
(§7.2). It is not an analytics product, no browser ever talks to it, and it is not shared
with anyone. It receives: error and warning reports as codes — which part of the service
failed, the kind of error, an error code or HTTP status, and counts — never the error's
text, never a payload and never the shop concerned; heartbeats with counts that show the
background jobs and billing are running; the version deployed; and, once per installation,
the Shopify shop domain (e.g.
example.myshopify.com) of a store when its staff take it live, ending its dry run. It holds no subscriber data and no merchant staff data. - Service health records. An internal health checker compares what our service should have done with what it did — subscriptions present at Shopify and here, renewals billed, webhooks processed, background jobs completing — and keeps its findings in our own database: identifiers of the affected subscriptions and billing records, codes and counts, kept while a problem is open and deleted 30 days after it is resolved, and with the store when it is erased. Our operations dashboard (§7.2) receives a summary per store under a pseudonymous code that only our checker can compute — the store's status, counts of affected subscriptions and charges, failure codes and times; never a subscriber's data, never the error's text — kept there 30 days after the store was last reported (resolved incidents 90 days).
- A used free trial. Boomrrang's paid plans come with a free trial once per store. When a
store that had a paid Boomrrang plan (a test plan included) is erased after an uninstall (§9),
we keep a one-way keyed hash of its Shopify store identifier and of its shop domain, and the
month it was erased, so the same store installed again does not get the free trial a second
time. The hash cannot be turned back into the store's identifier or domain without a secret
key only we hold, and we match it only against a store that installs the app. It is
pseudonymous, not anonymous: when the erasure follows Shopify's
shop/redactrequest, it is written together with our record that the request was completed, which names the store's domain (§3.3, §9), so someone with access to our database could connect the two. A store that never had a paid plan leaves nothing.
3.5 Website visitors
boomrrang.com is a static marketing site served separately from this application. Any analytics
or cookie use there is disclosed on that site. The application hosts (auth., hooks. and the
per-shop tenant hosts) set no advertising or analytics cookies at all. They set only the
strictly necessary cookies that sign a staff member in and keep them signed in (the session
cookie described in §3.2), plus one preference cookie on a tenant host if, and only after, a
staff member collapses the admin sidebar: cad_sidebar, holding the single word collapsed, so
the sidebar stays collapsed on their next visit. It identifies no one, is never sent anywhere
else, and is deleted when they expand the sidebar again.
4. What we deliberately do not collect
Data minimisation is a design constraint here, not an aspiration. Specifically:
- We never receive, process or store payment card numbers, CVVs, bank account numbers, or any other payment credential. Payment instruments are vaulted by Shopify and its payment providers. Where a charge must be made, we reference Shopify's own stored payment method by its Shopify identifier through the Admin API; the card itself never enters our system, our logs, or our backups. We are consequently not a card-data environment.
- We do not store subscriber names, shipping addresses, billing addresses or phone numbers that we read from Shopify: we fetch them on demand and discard them (§3.3). The one exception is data a merchant instructs us to move from a previous subscriptions app, which we keep as that app held it (§3.3a).
- We do not build customer profiles, and we do not track browsing behaviour. Order history, and the previous app's own records of its customers, are held only where a merchant moved them from a previous subscriptions app (§3.3a) — and those records only for the customers who had a subscription with it, unless the merchant runs that app's loyalty programme or asks us to keep every customer. The others' records are not read at all. The subscription tags we keep on a subscriber's customer record in Shopify (§7.1) say only where their subscriptions with the merchant stand, in the merchant's own words, and are worked out from those subscriptions alone. A flow the merchant sets up looks at one subscription at a time, against the merchant's own conditions, and keeps no picture of the subscriber: what it reads of them is compared and dropped (§3.3), and the tags it adds are the ones the merchant named.
- We do not store Shopify staff passwords or any password — the app has no password field, no password reset flow, and no credential store, because authentication is entirely mediated by Shopify (§10.2).
- We do not store raw IP addresses against staff sessions — only a hash.
- We do not build advertising profiles, run behavioural advertising, or sell or share personal information as those terms are defined under CCPA/CPRA (§12).
5. Legal bases for processing
Where we act as processor, the merchant is responsible for establishing the legal basis for the processing it instructs. Our agreement with the merchant requires it to have one.
Where we act as controller (merchant staff data, security and operational data), our bases under Article 6 GDPR are:
| Processing | Legal basis |
|---|---|
| Authenticating a staff member and maintaining their session | Article 6(1)(b) — necessary to perform our contract with the merchant, and 6(1)(f) legitimate interests in securing the service |
| Role and membership records; enforcing least privilege | Article 6(1)(b) and 6(1)(f) — legitimate interest in preventing unauthorised access |
| Event ledger, PII access log, webhook receipts, security logging | Article 6(1)(f) — legitimate interest in security, fraud prevention, and being able to reconstruct what happened; and Article 6(1)(c) where a law or Shopify's protected-customer-data requirements oblige us to keep the record |
| Operations telemetry to our operations dashboard (§3.4) | Article 6(1)(f) — legitimate interest in running the service reliably: noticing failures, stalled background jobs and missed billing, and knowing which stores have gone live |
| The record that a store used its free trial, kept past its erasure (§3.4) | Article 6(1)(f) — legitimate interest in offering the free trial once per store, as our Terms of Service say, rather than each time the same store installs again |
| Transactional email to merchant staff about the service | Article 6(1)(b) |
| Retaining records to defend or bring legal claims | Article 6(1)(f) |
| Complying with a legal obligation, court order or valid regulatory request | Article 6(1)(c) |
Where we process data revealing anything more sensitive than the above, we do not — the system is not designed to hold special-category data, and merchants are contractually asked not to place it in free-text fields.
We have documented a legitimate interests assessment for each 6(1)(f) basis above; it is available to merchants on request.
6. How we use personal data
We use the data in §3 to:
- Install the app, connect it to a merchant's Shopify shop, and keep that connection working.
- Authenticate the merchant's staff and decide what each of them is allowed to do.
- Display, create, edit, pause, resume and cancel subscription contracts at the merchant's direction, through Shopify's APIs.
- Move a merchant's subscriptions and their history from a previous subscriptions app at the merchant's instruction, keep that history for the merchant, and restart an ended subscription when asked (§3.3a).
- Schedule and execute recurring billing at the merchant's direction, exactly once per cycle.
- Send transactional subscription email on the merchant's behalf — confirmations and the customer portal's sign-in link — and, where the merchant's store has approved it, ask Shopify to email a subscriber a secure link to update or add the payment method on their subscription: after a failed payment, or when the subscriber or the merchant's staff ask for it (§7.1).
- Keep the merchant's subscription tags on its subscribers' customer records and on its subscription orders in Shopify, as the merchant has set them (§7.1).
- Run the automations a merchant sets up that change its subscribers' subscriptions — their items, discounts, dates and tags, and pausing or cancelling them — only on that merchant's own rules, and keep the record of what each one did (§3.3, §14).
- Respond to privacy requests received through Shopify's privacy webhooks (§11.3).
- Keep the service secure, available and correct: monitoring, error diagnosis, abuse prevention, and reconstructing the sequence of events after an incident.
- Meet our legal and regulatory obligations.
We do not use subscriber data to train machine-learning models, to build products for other merchants, for advertising, or for any purpose the merchant has not instructed. Where we produce aggregate statistics about the service (for example, total contracts processed), those statistics contain no personal data and cannot be re-identified.
7. Who we share personal data with
We share personal data with three categories of recipient, and no others.
7.1 Shopify
Shopify is not our sub-processor — it is the source and the destination of most of this data, and an independent controller in its own right. We read from and write to the merchant's Shopify shop using the scopes the merchant granted at install, or later when the app asked for one it added:
read_products, write_products, read_customers, write_customers, read_orders,
write_orders, read_all_orders, read_own_subscription_contracts,
write_own_subscription_contracts, write_customer_payment_methods.
read_products and write_products let the app read the shop's products and attach the
merchant's subscription plans to them; they carry no personal data, except that a flow's store
price for a subscriber billed in another currency is read for their delivery country, sent to
Shopify as its two-letter code.
read_own_subscription_contracts and write_own_subscription_contracts let it read and manage
the subscriptions it created — renewing, pausing, skipping, changing and cancelling them — and no
other app's.
read_customers and read_orders are what allow the app to show a subscriber's name and
shipping address on demand without storing them (§3.3); read_customers is also what the
app's background process uses to read a subscriber's email address once when a contract is
first recorded (§3.3), and what the mailer uses to address a notice at the time of sending. It is
also how a flow with a condition on a customer tag reads the subscriber's tags, when the flow runs
or the merchant's staff test it, to compare them with the merchant's condition; none of them is
kept (§3.3).
read_orders is also how the app checks its own charges: for each charge, the identifier and
total of the order it produced, and for each subscription, the identifier of the order it began
with. And before an ended subscription moved from a previous subscriptions app is restarted, it is
how the app reads that subscriber's orders since the move, no further back than 60 days — each
order's number, date and subscription plans, and no name, address or amount — to check that the
previous app has not billed them again; the orders on that app's plans are shown to the merchant
reviewing the restart, and nothing of the read is kept. And for a flow with a condition on the
products of the order that started a subscription, it is how the app reads that order's products
and quantities when the flow runs or is tested — nothing of the customer, an address or an amount —
keeping none of them.
write_customer_payment_methods lets the app read a subscriber's saved payment methods — a token
reference, the brand, the last four digits and the expiry, never a card number — and put one of
them on a subscription.
write_customers is asked of every store for two uses. It lets the app ask Shopify to email a
subscriber a secure link to update the payment method on their subscription, or to add one to it —
after a failed payment, or when the subscriber asks for it in the customer portal or the
merchant's staff ask for it — and to send a subscriber who asks for it in the portal to Shopify's
own page for updating a Shop Pay payment method. Shopify sends the email to the address it holds
for the customer: we choose neither the recipient nor the content, and we never see the card or
the link, except the Shop Pay page we send the subscriber to, which we never store or log. What we
keep is that the request was made, when, by whom and through which of Shopify's three requests —
identifiers and codes, never Shopify's own wording or the address. And it lets the app keep the
merchant's subscription tags on its subscribers' customer records: tags the merchant chooses in the
app, such as "Active Subscriber" or "Paused Subscriber", saying where each subscriber's
subscriptions with the store stand, added and taken off by the customer's identifier as those
subscriptions change. We keep which of them we put on each customer, and read no other tag and
nothing else of the record to do it. A flow the merchant sets up uses the same two tag requests to
add or take off, on the customer record of the subscription it ran on, the tags the merchant named
in the flow. Apart from those tags, it is not used to create, change or
delete customer records: the app makes exactly those three requests and the two tag requests with
it. A store that installs the app is asked for it on Shopify's install screen with the other
scopes; a store that installed the app before we began requesting write_customers is asked for
it, on Shopify's "update permissions" screen, the next time the store's owner opens the app from
the store's Shopify admin, at most once a day, and the store's staff are not asked. Until the store
has approved it, the app makes none of those requests for that store, and the store keeps working
without them; its subscribers' tags are put on once it has.
write_orders is asked of every store for one use alone: adding the merchant's tags to its
subscription orders — the order that started a subscription and each order the app bills — by the
order's identifier: its subscription tags, such as "Subscription" and "Subscription Recurring
Order", and the tags a flow the merchant sets up adds to the order it ran on. It is never
used to change an order's items, prices, addresses, payment or fulfilment, or to cancel, refund,
archive or close an order. To tag the order that started a subscription, the app reads under
read_orders when the order was created. Where the merchant has asked for a tag from an order
attribute, it reads each subscription order it tags — the order that started a subscription and
each order the app bills — for when the order was created and the names of its attributes, never
their values. We keep which tags we added to which order for 35 days after adding them (§9). A store that installs the app is asked for it on
Shopify's install screen with the other scopes; a store that installed the app before we began
requesting write_orders is asked for it in the same way as for write_customers, the next time
the store's owner opens the app from the store's Shopify admin, at most once a day, and the store's
staff are not asked. Until the store has approved it, no order of that store is tagged; an order
placed meanwhile is tagged once the store has, if that is within 55 days of the order. A flow that
adds or takes off tags can be turned on only once the store has approved the scope its tags need:
write_customers for a customer's, write_orders for an order's.
read_all_orders lets the app see a shop's orders older than 60 days, which
read_orders alone does not. We request it for features that need a subscriber's whole order
history: showing that history to the merchant and to the subscriber, cancellation and retention
offers that weigh how long and how much a subscriber has ordered, and the merchant's subscription
analytics. Each will read only the orders and order details it needs. Part of the first is
available to the merchant: a subscription's page in the merchant's admin reads from Shopify, by
each order's identifier and whatever its age where the shop has granted read_all_orders, that
subscription's own orders — the order each of its charges produced and the order it began with —
for each order's number, when it was created and cancelled, its payment and fulfilment status,
its current total and any amount refunded, and whether it is a test order; nothing of the
customer, an address or the order's lines, and none of it is kept. The others are not available
yet; until they are, the app reads no other order older than 60 days. A shop that installed
the app before we began requesting read_all_orders is asked for it the next time the shop's
owner opens the app from the shop's Shopify admin, at most once a day; the shop's staff are not
asked, and a shop that does not grant it keeps working as before.
7.2 Sub-processors
Each of the following processes personal data on our behalf, under a written contract containing the obligations required by Article 28 GDPR, with confidentiality obligations and appropriate technical and organisational measures.
| Sub-processor | Purpose | Data reached | Location |
|---|---|---|---|
| Fly.io | Application compute only: the TLS edge, the web application, the background worker and an internal health checker that reads the service's own records to detect billing and processing failures. Not the database. | Application data in transit and in process on its infrastructure. No durable stored records of merchant or subscriber data | United States — deploy region iad (Ashburn, Virginia). Transfers from the EEA/UK/Switzerland are covered by the mechanisms in §8 |
| Upstash (managed Redis queue, provisioned through Fly.io) | The job queue only; the billing schedule of record lives in the database, never here | Transient, re-derivable queue state; raw webhook payloads in transit to the worker | United States — iad (Ashburn, Virginia) |
| Supabase (managed PostgreSQL) | Primary database of record and encrypted backups; and, in a separate project, the database of our operations dashboard (§3.4) | All stored data in §3. Shopify API tokens as AES-256-GCM ciphertext only — the encryption key never leaves our own compute. What our servers send to the dashboard's project is only the operations telemetry in §3.4 | United States — us-east-1 (AWS N. Virginia) |
| Postmark (ActiveCampaign, LLC) | Transactional email delivery to merchant staff and to subscribers on the merchant's behalf | Recipient email address, and the contents of the message sent | United States |
| Sentry (Functional Software, Inc.) | Application error monitoring | Stack traces and request metadata, PII-scrubbed before transmission (§10.5) | United States (us.sentry.io data region) |
| Vercel, Inc. | Hosting of our internal operations dashboard (§3.4) — our own monitoring tool, not an analytics service | Error and warning codes, counts of background-job and billing health, the deployed version, a store's Shopify shop domain when it goes live, and per-store service-health summaries under a pseudonymous code (§3.4). No subscriber data, no merchant staff data, no error text | United States |
The job queue is a vendor service, and is listed above. The background job queue runs on Upstash's managed Redis, provisioned through Fly.io, so Upstash is a sub-processor in its own right. The queue holds only transient job state — including raw webhook payloads in transit to the worker, removed on completion — and no durable personal data; the billing schedule of record lives in the database, never in the queue.
Changes to this list. We will publish an updated list here before adding or replacing a sub-processor, and give merchants at least 30 days notice so they can object.
7.3 Others
- Professional advisers (lawyers, accountants, auditors) under confidentiality.
- Law enforcement, regulators or courts, where we are legally compelled. Where we are legally permitted to, we will notify the affected merchant before disclosing, so it can seek relief.
- A successor entity, in the event of a merger, acquisition or asset sale — subject to this policy continuing to apply, and to merchants being notified in advance.
We do not sell personal data, and we do not share it for cross-context behavioural advertising. We have never done so.
8. International transfers
All application hosting, processing and storage occur in the United States: application compute
on Fly.io in iad (Ashburn, Virginia), the primary database and encrypted backups on Supabase
in AWS us-east-1 (N. Virginia), the job queue on Upstash in iad, transactional email via
Postmark, error monitoring in Sentry's US data region, and our operations dashboard (§3.4) on
Vercel in the United States, with its database on Supabase in us-east-1. Personal data originating in the
EEA, the United Kingdom or Switzerland is therefore transferred to the United States for all of
the processing described in this policy, with Leds Get It LLC itself acting as the data
importer.
The United States has no general adequacy decision, and we have not certified under the EU–US Data Privacy Framework, so these transfers rely on:
- the European Commission's Standard Contractual Clauses (2021/914), Module Two (controller → processor) between the merchant-controller as data exporter and us as data importer, and Module Three (processor → processor) where the merchant itself acts as a processor for another controller. Our own sub-processors are US vendors, so passing data to them is not a further restricted transfer — their obligations flow down contractually through each vendor's data processing agreement;
- the UK International Data Transfer Addendum to those SCCs for UK transfers;
- the Swiss addendum recognised by the Swiss FDPIC for Swiss transfers;
together with a transfer impact assessment covering the destination country's laws, and the supplementary technical measures described in §10 — in particular encryption of tokens at rest, TLS in transit, and the deliberate absence of card data and customer profiles from our systems, which materially limits what any compelled disclosure could reach.
A copy of the SCCs as executed is available to merchants on request.
9. How long we keep data
Retention periods are set by our internal retention policy, and our automatic deletion follows it. The periods are:
| Data | Retention |
|---|---|
| Subscription contracts, lines, billing cycles and attempts | For the life of the subscription and while the app remains installed |
| Subscriber personal data (customer email on a contract) | Purged on receipt of a Shopify customers/redact webhook |
| Subscription tags we applied (§3.3): which tags are on each subscriber's customer record, and which were added to each order | A subscriber's record while the app remains installed, removed on receipt of a Shopify customers/redact webhook; an order's record 35 days after its tags were added, or 90 days after we stopped trying for one that could not be tagged |
| The record of the merchant's automations on each subscription (§3.3) | Each flow's runs on a subscription, with what each changed, 90 days; the events they looked at, and the markers that a flow acted on one, 35 days; that a flow set to run once on each subscription, or on one of its orders, has run on one, for as long as the subscription's record is kept, even after the flow is deleted. The runs, the events and the event markers are removed on receipt of a Shopify customers/redact webhook; the markers that such a flow has run — the flow's, the subscription's and the run's identifiers and the time it ran, and nothing more — are kept, so the flow never runs on that subscription, or that order, again |
| Data moved from a previous subscriptions app (§3.3a) | While the app remains installed. The subscriber's personal data in it is removed on receipt of a Shopify customers/redact webhook; all of it is deleted with the shop |
| All data belonging to a shop | Purged immediately on receipt of a Shopify shop/redact webhook — which Shopify sends around 48 hours after uninstall — and within 30 days of uninstall in any event (our operations dashboard's record of when the store went live, the record that the store used its free trial, and the records of the privacy requests we received for the store, its erasure request included, are kept as set out in the next three rows) |
| Operations telemetry in our operations dashboard (§3.4; contains no subscriber or staff data) | Error and warning reports 30 days; heartbeats 90 days; the record that a store went live, with its shop domain, 400 days — kept by the dashboard, outside the application's database, so an uninstall or shop/redact does not remove it sooner |
| The record that a store used its free trial (§3.4; a keyed one-way hash of the store's identifier and of its shop domain, and the month it was erased; only for a store that had a paid plan) | 24 months from the start of the month the store was erased — shop/redact and the 30-day purge write it rather than remove it, so a reinstall does not get the free trial again |
Records of the privacy requests we received (§3.3), including a shop/redact request's record, which keeps the shop's domain |
24 months from receipt, as evidence that each request was honoured — the shop/redact record outlives the shop it erased |
| Service health records (§3.4) | Open problems while open; resolved findings 30 days; incident summaries (codes, counts, times) 400 days; erased with the store |
| Service health summaries in our operations dashboard (§3.4; per store under a pseudonymous code, no subscriber data) | Health reports on the service as a whole 7 days (their daily summaries 400 days); a store's summary until it has not been reported for 30 days, or at once when our checker erases the store; resolved incidents 90 days; scans of each store's subscriptions at Shopify 30 days |
| Event ledger (contains no personal data) | 24 months |
| Webhook receipts (id, topic, payload hash — not payload contents) | 30 days |
| PII access logs | 12 months |
| Encrypted database backups | At most 35 days, then destroyed |
Three consequences worth stating plainly:
Uninstall deletion is fast, not leisurely. Because Shopify sends
shop/redactabout 48 hours after an uninstall, a merchant's data is normally gone two days later, not thirty. The 30-day figure is an outer bound for the case where no webhook arrives. Three records are kept longer: outside the application's database, our operations dashboard keeps the record that the store went live, with its shop domain, for 400 days; if the store had a paid Boomrrang plan, we keep a keyed one-way hash of its identifier and of its domain, with the month it was erased, for 24 months, so a reinstall does not get the free trial again; and the records of the privacy requests we received for the store — its erasure request included, with the shop's domain, and for an access request the customer and order ids it named — are kept 24 months as evidence that they were honoured (the table above).shop/redactdoes not shorten any of them. Merchants should export what they need before uninstalling (Terms of Service §12.5).Backups lag deletion. When we erase data from the live database, copies persist in encrypted backups until those backups age out, within 35 days. We do not restore deleted data from a backup to circumvent an erasure request; if a backup is ever restored, the erasure is re-applied.
The event ledger survives a subscriber's erasure by design — but only because it contains identifiers and no personal data. It is what lets us prove that deletion actually happened. A shop's own erasure deletes its event ledger with the rest of its data; the proof of that erasure is the record of the request (above).
Where a legal hold, an unresolved dispute, or a statutory obligation requires it, we may retain specific records beyond these periods, and only for as long as that reason lasts.
10. How we protect personal data
A fuller technical description is published at boomrrang.com/security. In summary:
10.1 Tenancy isolation
Each merchant is served on its own origin ({shop}.boomrrang.com), separate from the
authentication host and the webhook host. Every route asserts which host role it is allowed to be
reached on and returns 404 otherwise. Sessions are bound to a single shop; a session issued for
one tenant cannot be replayed against another.
10.2 Authentication — no passwords
Boomrrang has no password of its own. Identity comes entirely from Shopify OAuth: a staff member proves who they are to Shopify, and we receive the result. We therefore have no password database to breach, no credential-stuffing surface, and no password reset flow to abuse. Shopify's own multi-factor authentication protects the account.
Session cookies use the __Host- prefix and are Secure, HttpOnly, SameSite=Lax, and carry
no Domain attribute — which is what keeps a cookie from leaking sideways between tenant
subdomains. Only a hash of the session token is stored; the token itself exists only in the
browser.
10.3 Authorization — least privilege
Shopify authenticates; we authorize. Permission is expressed as fine-grained grants bundled into roles, and every state-changing action checks its specific grant. Actions that move money (charging now, changing dunning policy, refunding), actions that export data, and actions that reveal subscriber personal data each require their own separate grant — none of them is implied by ordinary read access. The default read-only role cannot see subscriber personal data at all.
10.4 Encryption
Shopify access tokens are encrypted at rest with AES-256-GCM — an authenticated cipher, so tampering with the ciphertext is detected rather than silently decrypted. All data in transit uses TLS 1.2 or higher. Database storage and backups are encrypted at rest by the managed provider.
10.5 Logging with personal data scrubbed
All application logging passes through a redaction layer before anything is emitted; tokens, request bodies and customer fields are never logged. Error reports sent to Sentry are scrubbed of personal data before transmission. Error reports sent to our operations dashboard (§3.4) carry a code, the kind of error and counts only — never the error's text and never the shop concerned.
10.6 Audit logging
Two immutable records back everything above: an append-only event ledger written in the same database transaction as the change it describes — so a change cannot exist without its audit record — and a PII access log that records every read of subscriber personal data, including which fields were read and why. These are the records we use to answer "who saw this customer's data?"
10.7 Our own staff access
Access to production data is restricted to named personnel who need it, is granted for a specific reason, and is logged. See boomrrang.com/security.
No system is perfectly secure, and we do not claim otherwise. We commit to the measures above and to notifying merchants of a breach as described in §13.
11. Your rights
11.1 If you are a subscriber (a shopper)
Under GDPR, UK GDPR and comparable laws, you have the right to:
- access the personal data held about you, and receive a copy;
- rectify data that is inaccurate or incomplete;
- erase your data ("right to be forgotten");
- portability — receive your data in a structured, commonly used, machine-readable format, and have it transmitted to another controller where technically feasible;
- restrict processing while a dispute about accuracy or legitimacy is resolved;
- object to processing based on legitimate interests, and to direct marketing at any time;
- withdraw consent where consent was the basis, without affecting prior processing;
- not be subject to a decision based solely on automated processing with legal or similarly significant effects — we do not make such decisions (§14);
- complain to a supervisory authority — in the EEA, the authority of the member state where you live or work, or where the issue arose (we have no EU establishment, so no single lead authority applies — the authority of each affected member state is competent); in the UK, the Information Commissioner's Office.
How to exercise them: contact the store you subscribed with. The merchant is the controller and is the one who can act. If you contact us at privacy@boomrrang.com instead, we will acknowledge you, tell you which merchant holds the relationship where we can identify it, and forward the request — we cannot act on a merchant's data without its instruction.
11.2 If you are merchant staff
The same rights apply to your own staff account data, for which we are the controller. Write to privacy@boomrrang.com. Note that some records — the event ledger, the PII access log — exist to prove what happened in a shop and are retained for the periods in §9 for security and legal reasons even after your access is removed; they contain identifiers, not personal profiles.
11.3 How Shopify's privacy webhooks actually implement this
Shopify sends every app three mandatory privacy webhooks. This is the mechanism by which a subscriber's rights reach us in practice, and here is exactly what each one does in our system:
| Webhook | What we do |
|---|---|
customers/data_request |
We record the request, assemble every record we hold of that subscriber — their contracts, both those of their Shopify customer identifier and any with no identifier that carries exactly the email address the request names, whatever its letter case (the same contracts the erasure below takes as theirs), with contract lines, billing cycles, billing attempts, the customer email held for the subscription list and portal sign-in, everything moved from a previous subscriptions app about that customer, as that app returned it (§3.3a), the flows that ran on their subscriptions (each flow's name, the event, when it ran, what each of its conditions found, how it ended and why, and each of its steps and how it ended), the events of their subscriptions the flows looked at, with which flows looked and whether their conditions held, and the markers that a flow acted on them, and the record of who looked at their data, against them or against any of those contracts (§10.6) — and return it to the merchant in machine-readable form so the merchant can fulfil the access and portability request. We respond within 30 days of receipt. |
customers/redact |
We erase the subscriber's personal data — the customer email held against their contracts (those of their Shopify customer identifier, and any with no identifier that carries exactly the email address the request names, whatever its letter case: we erase each of these as theirs, in everything this row says), and from the data moved from a previous subscriptions app their name, contact details, addresses, free text and every field not known to be non-personal — and sever the link to identifying data, leaving only non-identifying subscription records where we are required to retain them. The records of the flows on their subscriptions are deleted — the runs, the events and the markers that a flow acted on one — all but the markers that a flow set to run once, or on one of its orders, has run on a subscription, which hold no personal data and stop it running there again. Ended subscriptions moved from a previous app that were never restarted are deleted. The erasure is recorded in the event ledger so it can be proven. |
shop/redact |
Sent by Shopify 48 hours after a merchant uninstalls. We delete all data belonging to that shop, including the encrypted access token, memberships and contracts. Kept for their periods in §9, as evidence and not removed by this webhook: the records of the privacy requests we received for the shop (this one included) and the receipts of the webhooks Shopify sent us (an id, a topic, the shop's domain and a hash of the payload, never its contents). The one record outside our application's database — our operations dashboard's record that the store went live, with its shop domain (§3.4) — is kept for the period in §9 and is not removed by this webhook either. If the store had a paid Boomrrang plan, this webhook also writes the record that it used its free trial — a keyed one-way hash of its identifier and of its domain, and the month of the erasure (§3.4) — which is kept for the period in §9. |
Every one of these requests is recorded with its status and completion time, and every action taken is written to the event ledger in the same transaction that performs it. We commit to completing any request under this section within 30 days.
11.4 Verification
We verify requests before acting on them. For requests arriving through Shopify's webhooks, verification is cryptographic — we check the HMAC signature on every webhook and reject anything unsigned or altered. For requests arriving by email we may need to confirm identity through the merchant, precisely so that we do not disclose one person's data to another.
We do not charge for exercising these rights, unless a request is manifestly unfounded or excessive, in which case the law permits a reasonable fee or a refusal — and we will explain why.
12. California privacy notice (CCPA/CPRA)
This section applies to California residents. Under the CCPA as amended by the CPRA, we are a service provider to merchants for subscriber data, and a business in respect of merchant staff data.
12.1 Categories of personal information collected
In the preceding 12 months we have collected the following categories, all from the merchant's Shopify shop or from the staff member themselves:
| CCPA category | Do we collect it? | Examples |
|---|---|---|
| Identifiers | Yes | Shopify customer id, Shopify staff id, email address, shop domain |
| Personal information under Cal. Civ. Code §1798.80 | Yes, limited | Email. Name, address and telephone number only as part of data a merchant moves from a previous subscriptions app (§3.3a); otherwise read on demand and not stored |
| Commercial information | Yes | Subscription contracts, products subscribed to, billing history; order history moved from a previous subscriptions app (§3.3a) |
| Internet or network activity | Yes, limited | User-agent string and a hash of the IP address for staff sessions; application logs |
| Financial information | No | We never receive card numbers or bank details |
| Geolocation data | No | Shop country code, and a subscriber's delivery country (two letters) |
| Biometric information | No | — |
| Audio, electronic, visual or similar information | No | — |
| Professional or employment information | Yes, limited | A staff member's role within the shop |
| Education information | No | — |
| Sensitive personal information (CPRA) | No | We do not collect any category of sensitive personal information |
| Inferences / profiles | No | We build no profiles |
Purposes, sources, and retention for each category are as set out in §3, §6 and §9.
12.2 No sale, no sharing
We do not sell personal information, and we have not sold personal information in the preceding 12 months. We do not share personal information for cross-context behavioural advertising. We do not knowingly sell or share the personal information of consumers under 16 — we do not knowingly collect it at all (§13).
As a service provider, we are contractually prohibited from retaining, using or disclosing subscriber personal information for any purpose other than performing the services for the merchant, and from combining it with information from other sources except as CCPA permits.
12.3 Your California rights
You have the right to know what personal information is collected, used, disclosed and to whom; to delete personal information; to correct inaccurate personal information; to opt out of sale or sharing (there is nothing to opt out of — see §12.2); to limit the use of sensitive personal information (we collect none); and to non-discrimination for exercising any of these rights. We do not offer financial incentives.
To exercise these rights as a shopper, contact the store you subscribed with — as service provider, we act on the business's instruction. You may also write to privacy@boomrrang.com and we will route the request. An authorised agent may submit a request on your behalf with written proof of authorisation. We will respond within 45 days, extendable by a further 45 days with notice, as CCPA permits.
13. Children's data
Boomrrang is a business tool sold to merchants. It is not directed at children, and we do not knowingly collect personal data from anyone under 16 (or under 13 in the United States). We have no way to identify the age of a subscriber, because we do not collect date of birth or any age signal. If a merchant informs us that data belonging to a child has been placed in our system, we will delete it promptly on the merchant's instruction. If you believe a child's data has reached us, contact privacy@boomrrang.com.
14. Automated decision-making
We do not make decisions about individuals based solely on automated processing that produce legal or similarly significant effects. Recurring billing runs on the schedule the merchant configured and the subscriber agreed to; a failed payment triggers the retry sequence the merchant configured.
Besides billing and payment retries, a merchant can set up automations of its own ("flows") that change its subscribers' subscriptions when something happens to them — a subscription starts, an order is placed, a payment fails, a subscription is paused, cancelled or resumed: a product added, swapped or removed, a price or a discount changed, the delivery frequency or a custom attribute changed, the next order skipped, moved or given an extra item, a tag added or taken off, an email to the merchant's team, or the subscription paused or cancelled. They run without a person each time. These are the merchant's decisions, made in advance as rules: a flow acts only on the rules the merchant set up and turned on for its own store, and only on what happens after it was turned on; a template or a draft the app offers does nothing until the merchant turns it on, and we do not write or choose a merchant's rules. We stop a flow by ourselves only when its runs keep failing, and tell the merchant. A flow checks the facts the merchant named — such as which order of the subscription it is, its products and discounts, or a customer tag — and does what the merchant set. The merchant can see each run and why it ran or did not, test a flow on a subscription without changing anything, and turn any flow, or all of them, off.
Neither billing nor a flow involves profiling or an evaluation of the person beyond the facts the merchant named.
15. Security incidents and breach notification
If we become aware of a personal data breach affecting a merchant's data, we will notify that merchant without undue delay and in any event within 48 hours of becoming aware, with the information the merchant needs to meet its own Article 33 obligation to a supervisory authority within 72 hours. Because the merchant is the controller, it is the merchant who notifies regulators and affected individuals; we support that with facts, scope and remediation status. Our full incident response process is summarised in boomrrang.com/security.
16. Changes to this policy
We will update this policy when the service or the law changes. The "Last updated" date at the top always reflects the current version. For changes that materially affect how we handle personal data — a new category of data, a new purpose, a new sub-processor — we will notify merchants in advance, by email to the shop contact and in the app, giving at least 30 days before the change takes effect. Prior versions are retained and available on request.
17. Contact
| Privacy contact | privacy@boomrrang.com |
| Postal address | Leds Get It LLC — postal address available on request from privacy@boomrrang.com |
| Data Protection Officer | Not designated — an Article 37 assessment is in progress; privacy@boomrrang.com handles all privacy matters |
| EU representative (Art. 27 GDPR) | Appointment in progress — until then, contact privacy@boomrrang.com |
| UK representative (Art. 27 UK GDPR) | Appointment in progress — until then, contact privacy@boomrrang.com |
| Security contact / responsible disclosure | security@boomrrang.com — see boomrrang.com/security |
You always have the right to complain to a supervisory authority. In the EEA that is the authority of the member state where you live or work, or where the issue arose; in the UK it is the Information Commissioner's Office (ico.org.uk). We would appreciate the chance to resolve it with you first.