For the Glitter apps for Shopify, the website glitter.sh and our support. Effective date: 6 November 2026.
apps.glitter.sh, run on Cloudflare. It serves the app
pages, these legal pages, and receives Shopify’s mandatory privacy webhooks. It stores nothing.The Glitter apps are developed and operated by Glitter Shine Software Inc., 1025 King Street East, Unit 107 #4029, Cambridge, ON N3H 3P5, Canada, registration number 1835610-6 (Corporations Canada), Ontario Corporation Number 1001804149 (“we”, “us”). Contact for privacy questions: privacy@glitter.sh. The person responsible for the protection of personal information (Canada’s PIPEDA, Quebec’s private-sector privacy act) is Glitter Shine Software Inc., at that address. Representative in the EU (Art. 27 GDPR): not appointed. We rely on Art. 27(2) GDPR: the EU personal data we keep is limited to support messages and the store records Shopify shows us, and our processing is occasional, involves no special categories and is unlikely to result in a risk. Representative in the UK: not appointed. We rely on Art. 27(2) UK GDPR: the UK personal data we keep is limited to support messages and the store records Shopify shows us, and our processing is occasional, involves no special categories and is unlikely to result in a risk.
This policy covers the 3 apps listed in section 16, the pages on glitter.sh and apps.glitter.sh, and our support by e-mail.
Merchants. When an app processes personal data of your customers or staff inside your store (for example, customer tags read at checkout to apply your wholesale prices), you decide why and how: you are the controller. To the extent that we process such data at all, we do so on your behalf, as your processor, under our data processing terms. In practice this processing runs in your browser and on Shopify’s infrastructure, and the data does not reach systems we operate.
Us. For the data we receive directly (section 4) we are the controller.
Your customers (buyers). Your store’s privacy notice tells your customers how you use their data, including through apps. Section 7 lists what our storefront features do in a shopper’s browser, so that you can describe it.
| Data | Source | Purpose | Legal basis (GDPR) | Kept for |
|---|---|---|---|---|
| Store details for each install, as Shopify’s documentation describes them: the store, its Shopify plan and its plan for our app, the install date, whether the install came from an ad campaign, install and uninstall events, charges and earnings. Shopify decides what it shows us, and that may include other details, such as a contact e-mail address or feedback given when uninstalling. | Shopify, in our Partner Dashboard, Dev Dashboard and Partner API (source). | Billing, support, preventing abuse, accounting. | Contract; legal obligation (accounting). | 6 years after the end of the tax year they relate to, then deleted. Shopify’s own copies in those dashboards stay for as long as Shopify decides; we do not control that. |
| Support messages: your name, e-mail address, store domain, the content of your message and attachments. | You, when you write to support@glitter.sh. | Answering you; improving the apps. | Legitimate interest; contract. | 24 months after the last message, or earlier on request |
| Technical request data when an app page loads in your Shopify admin: IP address, browser user agent, and the page address. Shopify adds to that address your store’s myshopify domain, your admin language, a signature and a short-lived Shopify session token that identifies the store and the Shopify staff account ID (session token fields). When you print from an app’s print action, the Shopify admin fetches the print page from our host with the same kind of token in a request header; our code ignores it. | Your browser, via Cloudflare. | Delivering the page. Our code reads only the store domain (to send the security header that lets only your admin frame the page) and the app’s client ID inside the token (to route a deep link to the right app). It stores nothing. | Legitimate interest (operating the service). | Not stored by our code. Cloudflare’s Workers Logs are switched off for our host, so no request log is kept for us (section 10). |
Shopify’s privacy webhooks (section 8). For customers/data_request and
customers/redact Shopify’s message contains the store ID and domain, the customer’s ID, e-mail and
phone, and order IDs; for shop/redact the store ID and domain
(payloads). |
Shopify. | Verifying the signature and acknowledging the request. | Legal obligation; legitimate interest. | The message body is read into memory to check its signature and then discarded. Our code writes only the app, the topic and Shopify’s webhook ID to the log, and that log is not kept (section 10). |
| Print documents: when you print from an app that uses our print route, the data the printout shows (for example product titles, SKUs, barcodes and prices for labels) travels to our host in the print link’s address, because Shopify shows print pages with scripts switched off and the page must arrive finished. | The Shopify admin, from your browser, via Cloudflare. | Rendering the printable page. | Contract (providing the feature). | Rendered in memory and not stored; our code logs no print data (only a template error, without the data), and the page is sent with a “no-store” cache header. Cloudflare’s Workers Logs, which would contain the address, are switched off for our host (section 10). The apps that use this route are named in section 16; today they print product data (labels, line sheets), not buyer data. |
| Shopify’s developer logs of our apps, as Shopify’s documentation describes them: for each GraphQL Admin API request an app makes, the request and Shopify’s response, large ones cut off; webhook deliveries; for each run of an app’s checkout Function, its input and output, shown when the app’s permissions cover the fields it reads. Shopify decides which entries and fields appear, and its documentation does not say whether the requests an admin page sends directly from your browser are included, so we assume they can be. These entries can contain your store’s data and the protected customer data listed per app in section 6. | Shopify, in the Dev Dashboard of our Shopify developer account (logs, Function runs). | Investigating a problem you report and checking an app after a change. We do not copy, export or use this data for anything else. | Legitimate interest (operating and fixing the apps); for your customers’ data, your instructions under our data processing terms. | Kept by Shopify for 30 days (“Logs are retained for 30 days”); we keep no copy. Visible in our developer account to the owner and one administrator, both with two-step sign-in. |
| Visits to our pages on apps.glitter.sh (these legal pages, the support pages) and to our website glitter.sh: IP address and user agent. | Your browser, via Cloudflare. | Delivering the page. | Legitimate interest. | Not stored by us; see section 10 for Cloudflare. |
We use no analytics, advertising or tracking on our pages and set no cookies there. The legal and support pages contain no scripts; the website’s scripts only operate the page (menu, search box, filters) and send nothing. We do not sell personal data, do not use it for advertising or for “competitive benchmarking”, and do not use your data or your customers’ data to train or improve any AI or machine-learning model. We make no automated decisions about a person that have legal or similarly significant effects.
We use your store’s data only to provide the app’s features to you. We do not copy or keep it on our systems.
Shopify calls customer and order data protected customer data. Level 1 is customer data without name, address, phone and e-mail; Level 2 includes any of them (source). An app can read it on a live store only after Shopify approves the app. These apps use it:
Required for the app’s main job:
Only for an optional feature you turn on:
For each of them: the data is processed only for the stated purpose, inside Shopify (Functions at checkout, the customer’s own account, or your admin page in your browser); it is not sent to us, not stored by us, and not used for automated decisions about a person beyond applying your own rules (for example a price or a checkout limit you set). Shopify’s developer logs show it to us for 30 days (the app’s API responses and its Functions’ inputs, section 4); we open them only to fix a problem and never copy them.
Cookies. None of our storefront scripts sets a cookie (checked in each app’s theme code). Features that add to the cart or send a form use Shopify’s own cart and forms, which may use Shopify’s cookies.
Browser storage. Some features remember a shopper’s choice in the shopper’s own browser
(localStorage keeps it until cleared; sessionStorage until the tab or browser session
closes). Nothing stored this way is sent to us.
| App | Storage | What is stored |
|---|---|---|
| Glitter Announcement Bar | localStoragesessionStorage | Bars the visitor closed (od-ab:<bar id>:<version>, until the bar changes, local) and the first UTM parameters and external referrer of the visit, for bar targeting (session). |
| Glitter Chat Buttons | sessionStorage | Whether the visitor closed the greeting bubble (session). |
Detected in each app’s storefront code; 2 of 3 apps.
Consent. These apps’ storefront code reads the visitor’s choice from Shopify’s Customer Privacy API (the choice made in your cookie banner):
The other browser-storage uses do not check consent. They are listed, with what each one stores, so that you can decide how to present them in your cookie notice and whether to turn the feature on.
Your responsibility. You choose which features to turn on in your store, and you are the one who shows your visitors a cookie or privacy notice and collects any consent the law of the countries you sell to requires for them, including for the browser storage above and for the third-party services below. We do not decide that for you. Under the EU and UK ePrivacy rules, storing information in a visitor’s browser, or reading it back, normally needs the visitor’s consent unless it is strictly necessary for a service the visitor asked for; the European Data Protection Board reads this as covering any browser storage, whether or not it is personal data, and as covering information a page reads from the visitor’s device such as link parameters (Guidelines 2/2023). Shopify asks apps that set cookies on a storefront to follow the choice made in the store’s cookie banner through its Customer Privacy API. Where an app above does not check consent, treat its storage as something your notice must cover or do not turn that feature on.
Forms. Sign-up, restock, quote, contact, quiz and wholesale-application forms send what the shopper types to Shopify’s own customer or contact forms. Shopify stores it in your store or e-mails it to you; our apps do not receive it.
Third-party services. A few features load content from, or link to, other services that you choose. The shopper’s (or your) browser then contacts that service directly:
| Service | When | Apps |
|---|---|---|
api.mapbox.com | Mapbox — geocoding or map tiles with the merchant’s own key | Glitter Store Locator |
api.maptiler.com | MapTiler — geocoding or map tiles with the merchant’s own key | Glitter Store Locator |
ig.me | Instagram — opens the visitor’s messaging app when clicked | Glitter Chat Buttons |
line.me | LINE — opens the visitor’s messaging app when clicked | Glitter Chat Buttons |
m.me | Messenger — opens the visitor’s messaging app when clicked | Glitter Chat Buttons |
maps.apple.com | Apple Maps — directions link, only when a shopper clicks it | Glitter Store Locator |
maps.googleapis.com | Google Maps Platform — geocoding with the merchant’s own key, from the merchant’s browser | Glitter Store Locator |
nominatim.openstreetmap.org | OpenStreetMap Nominatim — geocoding of store addresses from the merchant’s browser, when the merchant chooses it | Glitter Store Locator |
pinterest.com | Pinterest — share / follow link, only when clicked | Glitter Chat Buttons |
signal.me | Signal — opens the visitor’s messaging app when clicked | Glitter Chat Buttons |
t.me | Telegram — opens the visitor’s messaging app when clicked | Glitter Chat Buttons |
tile.openstreetmap.org | OpenStreetMap tiles — loaded by shoppers’ browsers for the interactive map, if the merchant picks this provider | Glitter Store Locator |
tile.thunderforest.com | Thunderforest tiles — loaded by shoppers’ browsers, if the merchant picks this provider | Glitter Store Locator |
tiles.stadiamaps.com | Stadia Maps tiles — loaded by shoppers’ browsers, if the merchant picks this provider | Glitter Store Locator |
wa.me | WhatsApp — opens the visitor’s messaging app when clicked | Glitter Chat Buttons |
www.facebook.com | Facebook — share / follow link, only when clicked | Glitter Chat Buttons |
www.google.com | Google Maps — directions links opened by shoppers, or the Google Maps embed (merchant’s key) in Glitter Store Locator | Glitter Store Locator |
www.linkedin.com | LinkedIn — share / follow link, only when clicked | Glitter Chat Buttons |
www.openstreetmap.org | OpenStreetMap — embedded map of the selected store (shoppers’ browsers) and attribution links | Glitter Store Locator |
x.com | X — share / follow link, only when clicked | Glitter Chat Buttons |
Every app subscribes to Shopify’s three mandatory privacy webhooks. Our host checks Shopify’s signature on each message (a message with a wrong or missing signature is refused with 401) and answers 200.
| Webhook | When Shopify sends it | What we do |
|---|---|---|
customers/data_request | A customer asks you for their data. | Our systems keep no copy of your customers’ data (the webhook itself is read, verified and discarded, and our host stores nothing), so the host only acknowledges the message. The data our apps keep about that customer is in your store (for example cart attributes and line-item properties on their orders, customer tags); you can see and export it in your Shopify admin, and section 16 lists per app what is kept and where. Two places outside your store can show us that customer’s data for a while: a support message in which you included it (section 4, kept as described there) and Shopify’s 30-day developer logs (section 4, kept by Shopify, never copied by us). If you need either described for a request, write to privacy@glitter.sh and we answer within 10 days. |
customers/redact | You or Shopify erase a customer; sent 10 days after the request (or withheld for 6 months after a recent order). | Nothing to erase in our systems. Data in your store is erased by you or by Shopify: Shopify’s erasure removes personal data such as the customer’s name and address and keeps the customer profile and order history (source). Its documentation does not say whether that also clears customer metafields an app wrote, and we do not control what it reaches. Apps can keep data there, so after such a request check that customer’s metafields in your admin and remove what is left. If a support thread with you contains that customer’s data, we delete it on request. |
shop/redact | 48 hours after you uninstall the app. | Nothing to erase in our systems: we keep no store data. Your support messages stay for the period in section 10 (or are deleted earlier on request); our install and billing records about your store stay for 6 years after the end of the tax year they relate to, then deleted. What happens to data in your store is described in section 11. |
Timings from Shopify’s privacy-law compliance page. You can also write to privacy@glitter.sh; we answer within 30 days.
| Provider | What they do for us | Data | Terms |
|---|---|---|---|
| Cloudflare, Inc. (USA; global network) | Hosts the app pages, this website and the privacy-webhook endpoint, and forwards mail sent to our addresses to our support mailbox (Cloudflare Email Routing). Cloudflare shows us a routing log of forwarded messages (sender, recipient, time and result; not the message content). | Request data (section 4); privacy-webhook messages and support messages in transit; the routing log. | Cloudflare’s data processing addendum is part of its self-serve subscription agreement and includes the EU Standard Contractual Clauses (DPA, version 6.3 of 20 June 2025 read; its sub-processors). |
| Google (Gmail; USA, global data centres) | Our support mailbox: a standard Gmail account, which stores support messages. | Support messages. | Google’s Terms of Service and Privacy Policy. This account has no data processing agreement. |
| Brevo (France; hosting in the EU) | Sends our replies to support messages. | Your e-mail address and our reply. | Brevo’s terms, which include its data processing agreement (Appendix 3). |
Shopify is the platform your store runs on, under your own agreement with Shopify. The apps store data in your store and Functions run on Shopify’s infrastructure; Shopify is not our sub-processor. Services you choose to connect through an app (section 7) work under their own terms with you.
Shopify deletes the app’s own metafield and metaobject definitions at uninstall and keeps the values “temporarily”, for a period Shopify does not guarantee, so that a reinstall can restore them (source). Data an app wrote outside its own space stays in your store until you delete it: tags, cart attributes and line-item properties on orders, products and files it created for you, and these metafields in your own namespaces:
Several apps offer “Remove all data” or “Export” in their settings; use them before uninstalling if you want a clean store or a backup.
Depending on where you live, you may ask for access to, correction or deletion of your personal data, restrict or object to its use, receive a copy in a machine-readable format, and withdraw a consent you gave (this does not undo processing that happened before). Write to privacy@glitter.sh; we answer within 30 days and may ask you to confirm who you are. You may also complain to a data protection authority: in Canada the Office of the Privacy Commissioner of Canada (and in Quebec the Commission d’accès à l’information), in the EU the authority of your country, in the UK the Information Commissioner’s Office. Giving us your details when you write to support is voluntary; without them we cannot answer. If you are a shopper of a store that uses our apps, please contact that store first: it controls your data, and we will help it answer. Our apps are for businesses and are not directed at children.
We are in Canada. Support messages, our replies and the store records Shopify shows us are processed in Canada. The EU and the UK recognise Canada’s federal privacy law (PIPEDA), which applies to us, as providing adequate protection for commercial organisations. Cloudflare processes requests in its global network; transfers from the EU / UK to Cloudflare rely on the Standard Contractual Clauses in Cloudflare’s DPA. Support messages are stored by Google (USA) and replies are sent through Brevo (EU). Where a provider in the USA is certified under the EU-US Data Privacy Framework (and its UK extension), that certification covers the transfer; otherwise the Standard Contractual Clauses do.
We will post changes here with a new effective date. For material changes we will tell merchants who have an app installed at least 30 days in advance, through the app or by e-mail.
For each app: the permissions it asks for and why, whether it uses protected customer data, what its checkout Functions read, where it stores data in your store, and what it does in your shoppers’ browsers. The rows come from the app’s code and configuration; the description below them explains the app in words.
| App | Protected customer data | Checkout buyer fields | Shopper browser storage |
|---|---|---|---|
| Glitter Announcement Bar | none | — | local, session |
| Glitter Chat Buttons | none | — | session |
| Glitter Store Locator | none | — | — |
announcement-barwrite_validations — create and change the app’s checkout rules (validations)read_products — read products, variants and collectionsread_online_store_pages — read Online Store pageslocalStorage, sessionStorage — Bars the visitor closed (od-ab:<bar id>:<version>, until the bar changes, local) and the first UTM parameters and external referrer of the visit, for bar targeting (session).Description: stores your bars (texts, links, codes, targeting, schedules), your vacation closures and messages in app settings read by your theme (plus your store timezone), and the closures on its own checkout validation. At checkout the Function reads only the store's local date/time, the checkout language and one cart attribute (_od_open, your private bypass code), transiently — never cart lines or buyer data. Customer targeting happens in your theme at page render; the storefront script keeps UTM parameters/referrer for the visit in session storage and remembers closed bars in the shopper's browser. No customer data is read or stored.
chat-buttonsread_files — read files in Content › FilessessionStorage — Whether the visitor closed the greeting bubble (session).www.facebook.com — Facebook — share / follow link, only when clickedx.com — X — share / follow link, only when clickedpinterest.com — Pinterest — share / follow link, only when clickedwa.me — WhatsApp — opens the visitor’s messaging app when clickedt.me — Telegram — opens the visitor’s messaging app when clickedwww.linkedin.com — LinkedIn — share / follow link, only when clickedm.me — Messenger — opens the visitor’s messaging app when clickedig.me — Instagram — opens the visitor’s messaging app when clickedline.me — LINE — opens the visitor’s messaging app when clickedsignal.me — Signal — opens the visitor’s messaging app when clickedDescription: stores your contact channels (WhatsApp / phone numbers, usernames, email addresses, agent names and avatars, message templates, business hours) and social links in one app setting that your theme renders, plus your store’s timezone. If you choose “Pick from Files”, it lists the images in Content → Files. The app never sees who clicks: links open the visitor’s own messaging app, and optional click events go only to the analytics tools already on your store (Shopify customer events, GA4, Meta) and only when the visitor’s consent allows. No customer, order or visitor data is read or stored.
store-locatorread_products — read products, variants and collectionsread_locations — read your locationsread_online_store_pages — read Online Store pageswww.google.com — Google Maps — directions links opened by shoppers, or the Google Maps embed (merchant’s key) in Glitter Store Locatorwww.openstreetmap.org — OpenStreetMap — embedded map of the selected store (shoppers’ browsers) and attribution linksmaps.apple.com — Apple Maps — directions link, only when a shopper clicks itmaps.googleapis.com — Google Maps Platform — geocoding with the merchant’s own key, from the merchant’s browserapi.mapbox.com — Mapbox — geocoding or map tiles with the merchant’s own keyapi.maptiler.com — MapTiler — geocoding or map tiles with the merchant’s own keynominatim.openstreetmap.org — OpenStreetMap Nominatim — geocoding of store addresses from the merchant’s browser, when the merchant chooses ittile.openstreetmap.org — OpenStreetMap tiles — loaded by shoppers’ browsers for the interactive map, if the merchant picks this providertiles.stadiamaps.com — Stadia Maps tiles — loaded by shoppers’ browsers, if the merchant picks this providertile.thunderforest.com — Thunderforest tiles — loaded by shoppers’ browsers, if the merchant picks this providerDescription: stores your stores, dealers and stockists (business addresses, coordinates, business phone/email/website, opening hours, tags, linked products) as app-owned metaobjects in your store, a compiled copy for your storefront and your locator settings in app settings, and an optional geocoding key in an app setting that is only read by the admin page. Coordinates are looked up from your browser directly with the geocoding provider you choose (OpenStreetMap Nominatim, or your own Google / Mapbox / MapTiler key) — nothing passes through our servers. On the storefront, “Use my location” asks the shopper’s browser for its position and uses it only in that browser to sort stores by distance; it is never sent anywhere. If you choose an embedded or interactive map, the shopper’s browser loads map images from the provider you configured. No customer data is read or stored.
Glitter Shine Software Inc., 1025 King Street East, Unit 107 #4029, Cambridge, ON N3H 3P5, Canada — privacy@glitter.sh.