Privacy policy

Last updated November 16, 2026 · Applies to the dataMonitorio Shopify app and datamonitorio.com

Two parts, one policy

Part A covers the dataMonitorio Shopify app, including data about merchants and their shoppers. Part B covers this website, the waitlist and the partner program.

Part A: The dataMonitorio Shopify app

This policy explains what information dataMonitorio ("the app", "we", "us") collects when a Shopify merchant installs and uses it, how we use that information, and the choices merchants and their customers have. dataMonitorio is provided by dataMonitorio, Chattogram, Bangladesh ("we").

dataMonitorio is a Shopify app that builds a tracking dataLayer on a merchant's online store and checkout, generates Google Tag Manager containers, and, on the Pro plan, shows reports about tracking delivery, sales channels and customer lifetime value.

1. Who this policy is for

  • Merchants: Shopify store owners and their staff who install and use dataMonitorio.
  • Shoppers: people who visit or buy from a store that uses dataMonitorio. For shoppers, the merchant is the controller of their personal data and dataMonitorio acts on the merchant's behalf. Shoppers should also read the store's own privacy policy.

2. Information we collect and store

2.1 About the merchant's store

When a merchant installs the app, Shopify gives us:

  • the store's Shopify domain and store identifiers;
  • an access token, so the app can work with the store on the merchant's behalf;
  • details of the staff member who opens the app (such as name and email address), which Shopify provides with each admin session.

2.2 Settings the merchant enters

  • Google Tag Manager container ID, server container URL, GA4 measurement ID and custom GTM loader address;
  • which ad platforms and consent options are switched on, and other tracking options;
  • email addresses for alerts (Pro);
  • the merchant's plan, as reported by Shopify.

2.3 Anonymous reports (Pro)

  • Delivery counts: the GTM containers we generate for Pro stores report whether each platform's tag succeeded or failed for each event. We store only counts per day and hour, by event name, platform and result. These reports contain no shopper details, IDs, cookies or web addresses.
  • Customer totals: once a day we calculate totals such as the number of customers, revenue and repeat-purchase rate per marketing channel. Only these totals are stored, never individual customers or customer IDs.

2.4 Customers report access log (Pro)

Each time a staff member opens the Customers report, we record the store, the Shopify staff user ID, the staff member's email address if Shopify provides it, and the date and time. We record at most one entry per staff member every 5 minutes. The log contains no customer information: not which customers were shown, nor any filters or searches. We keep it to protect the customer data shown on that page and to show who accessed it.

2.5 Google account access (Pro, if the merchant signs in with Google)

On the Pro plan, a merchant can sign in with Google so we add their ready-made tags to their own Google Tag Manager and publish them for them. If they do:

  • What we access, with the merchant's permission: the merchant's Google Tag Manager accounts, containers, workspaces and versions (to list them, prepare the tags in a separate workspace and publish when the merchant asks), their Google Analytics properties and web data streams (read only, to list them), and the email address of the Google account (to show which account is connected).
  • What we store: a Google access token (a "refresh token") that lets us act on the merchant's Tag Manager without them signing in each time, stored encrypted (AES-256-GCM, with a key kept separately from the database); the Google account's email address; the permissions granted; and progress counts and error codes of the current tag preparation. We do not store anything from the merchant's containers or Analytics properties, beyond the version numbers of what we published.
  • What we do with it: only what the merchant starts in the app: list containers and data streams, create containers if asked, prepare tags, publish them, publish updates and replace expired access tokens. We do not use it for anything else, do not sell it, and do not use it for advertising or to train AI models.
  • Platform access tokens (Meta, TikTok and the others) still never reach us: the merchant's browser writes them into their Tag Manager directly.
  • Google API Services User Data Policy: dataMonitorio's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
  • Removing it: the merchant can disconnect at any time in the app (Settings → Google Tag Manager → Disconnect Google), which deletes the stored access and revokes it at Google, or in their Google Account (Security → Third-party connections). Uninstalling the app also deletes and revokes it.

2.6 Order events and Order check (Pro)

  • Order events. For the order events described in section 3, we store the order ID, an event key and the delivery status (sent or failed), so the same event isn't sent twice. No customer details are stored.
  • Order check. For Pro stores' Order check, we store each order ID with the result for each platform (succeeded or failed). No customer details are stored.

2.7 Information we do not store

  • Shoppers' tracking data. The dataLayer runs in the shopper's browser. Events go from the store directly to the merchant's own Google Tag Manager containers, which the merchant controls. They do not pass through or get stored on dataMonitorio's servers. The exception is order events (Pro, see section 3): the app reads the order from Shopify and passes the event to the merchant's server-side container without storing the customer details. We keep only the record described in section 2.6.
  • Platform IDs and access tokens entered in GTM setup. The containers are built in the merchant's browser, and with Google sign-in (section 2.5) the browser writes these values into the merchant's Tag Manager directly, so they are never sent to us. Platform IDs, but not access tokens or test codes, are remembered in that browser's local storage (key dmio.gtmSetup.v1.<store>) so the merchant doesn't have to type them again. The merchant can clear them at any time with "Forget saved IDs".
  • Customer lists. The Customers page reads customer names, email addresses and order totals live from Shopify each time the merchant opens it. To keep the page fast, ranked lists are held in memory for up to one hour and are not saved to a database.

2.8 Setup emails and support messages

  • Setup emails. In the first two weeks after install, we send a few short emails to the store's contact email (Shopify Settings → General) about finishing setup: a welcome and reminders on day 1 and day 3 while setup isn't finished, and one check-in on day 7 once it is. On paid plans with a free trial, we also send one email two days before the trial ends, with the plan's price and how to change or cancel it; we read the trial dates from Shopify. We read the email address from Shopify each time and don't save it. We store only which of these emails were sent and when. Every setup email has a one-click unsubscribe link, which stops all of them. Alerts (Pro) are separate: the merchant turns them on and off in the app's Settings.
  • Support messages. When a merchant uses the contact form on the app's Help page, we email the topic and message, the store's domain and plan, and the store's contact email (read from Shopify, so we can reply) to our support inbox, hosted by Hostinger (see section 9). The message isn't saved in the app's database. To prevent abuse, we count each store's messages for one hour.

3. What happens on the merchant's storefront and checkout

When the merchant turns on the app's theme embed and checkout pixel:

  • The app adds ecommerce events (for example product views, add to cart and purchases) to the store's dataLayer for the merchant's tags to use.
  • For logged-in customers and at checkout, the dataLayer can include customer details (such as email address, phone number, name and address) so the merchant's advertising platforms can match conversions. Email, phone and name are also provided in hashed (SHA-256) form.
  • If the merchant connects a cookie banner (consent platform), the app follows the shopper's choice:
    • without marketing consent, personal details and advertising identifiers are removed from events;
    • the merchant's tags wait for consent when Google Consent Mode is on.
  • Browser storage: with the shopper's consent, the checkout pixel saves the customer details entered at checkout in the shopper's own browser (localStorage key _dmud2), so later storefront pages can include them. The app also keeps:
    • Visitor ID: a first-party cookie (_dm_vid) holding a random ID, kept for up to 390 days and created only when the shopper allows analytics or advertising. It lets the merchant's tags recognise the same visitor on the storefront and at checkout. It contains no personal details.
    • Cart snapshot: a short list of the cart's products and quantities, kept in the shopper's browser (localStorage key _dmcart) so the app can tell when items are added or removed. It contains no personal details.
    • Sign-in flag: a 0/1 value (localStorage key _dm_signed_in) noting whether the shopper was signed in on their last page, so the app can report a sign-in. It is kept only with analytics or advertising consent and removed otherwise. It does not identify the shopper.
    • Sent checkout events: the checkout pixel keeps a short list of the checkout events it has already sent (session storage key _dmse_ followed by the checkout token; event names only, no personal details) so that reloading a checkout or thank-you page doesn't send them twice.
    • Ad click IDs: with advertising consent, the advertising click IDs from the page the shopper landed on (for example Google's gclid, Meta's fbclid, Microsoft's msclkid) are kept for up to 90 days in a first-party cookie (_dm_clk), so purchases at checkout can be credited to the ad that was clicked.
    • Visitor IDs on the order (Pro stores using post-purchase or renewal tracking): the app adds a hidden cart attribute (_dm) holding the shopper's visitor and advertising IDs, only those their consent allows. Shopify copies it to the order, so the app can match later order changes to the same visitor.

    None of these is sent to dataMonitorio: the cookies and browser storage stay in the shopper's browser, and the _dm attribute is stored in the merchant's Shopify order. When order events are turned on, the app reads the _dm attribute with the order to send the event, and does not store it.

Order events (Pro, only when the merchant turns them on): when an order is edited to add items, refunded or cancelled, or a subscription renews, Shopify notifies the app. The app reads that order from Shopify and sends the event to the merchant's own server-side Google Tag Manager container, in the same form as the checkout events: purchase value, items, and the customer's contact details, with email, phone and name hashed (SHA-256), and only what the shopper's consent allows. The merchant's GTM setup decides which platforms receive it.

The merchant decides which platforms receive this data through their own Google Tag Manager setup. Each platform's use of the data is covered by that platform's own terms and privacy policy.

4. How we use information

We use the information above only to:

  • provide the app's features: publishing settings to the store, generating containers, showing reports and sending alerts;
  • check the merchant's plan with Shopify and unlock the right features;
  • send service emails: setup emails after install and before a trial ends (section 2.8, each with an unsubscribe link), alerts the merchant turned on, and replies to support messages;
  • keep the app secure, prevent abuse, and fix problems.

We do not sell personal information, use it for advertising, or combine stores' data with each other.

5. Sharing

We share information only with:

  • Shopify, to run the app inside the Shopify admin and handle billing;
  • service providers that host and run the app for us, listed in section 9;
  • authorities, where the law requires it.

Partners: if a merchant links their store to a partner with a partner code, the partner does not see the store's name, settings, tracking status, orders or customers. The partner sees only how many stores are linked to them and the commission they earn, calculated from the store's app charges. The link is permanent once confirmed and doesn't give the partner any access to the store.

6. How long we keep information

Information Kept for
Delivery counts (daily) 90 days
Delivery counts (hourly) 72 hours
Order event keys and delivery status 30 days
Order check (order ID and per-platform result) 90 days
Customer totals Replaced every day
Customer lists in memory Up to 1 hour
Settings, plan and store records While the app is installed
Which setup emails were sent, and when (no email address) While the app is installed
Support messages In our support inbox, 24 months after the conversation ends
Google account access (encrypted refresh token, Google email, permissions) and tag-preparation progress (Pro, if used) Until the merchant disconnects Google or uninstalls the app; deleted and revoked at Google then
Customers report access log (staff user ID, email if provided, date and time) 12 months, then deleted automatically. If the app is uninstalled, it is deleted with the rest of the store's data when Shopify asks us to (48 hours after uninstall)
Everything about the store Deleted when Shopify asks us to, 48 hours after the app is uninstalled, except the partner records below
Partner link record (store domain, partner, link date, first install date) and the store's app charges, only if a partner code was entered Kept after uninstall: they decide the partner's commission and stop the 14-day code window from reopening on reinstall. They contain no shopper data
Record of privacy requests (store domain, request type, date, action taken; no customer details) 3 years, to show that requests were handled

7. Privacy requests

  • Shoppers: contact the store you bought from. The merchant can ask us for help at support@datamonitorio.com.
  • Requests through Shopify: we answer the privacy requests Shopify sends on behalf of shoppers and merchants (data access, customer deletion and store deletion) within the time Shopify requires. Because we do not store personal data about shoppers, there is usually nothing to provide or delete; store data is deleted completely on a store deletion request. A store deletion request also deletes the store's Customers report access log; customer data requests don't involve it, because it holds no customer data.
  • Merchants: you can see and change your settings in the app at any time. Uninstalling the app starts deletion of your store's data.

Depending on where you live, you may have rights to access, correct, delete or restrict the use of your personal information, and to complain to a data protection authority. Contact us to use these rights.

US state privacy laws: the dataMonitorio app does not sell personal information, or share it for cross-context behavioural advertising, as those terms are used in laws such as the California Consumer Privacy Act. On our website, advertising cookies from Google and Meta (see Part B) are used only with your consent; you can withdraw it at any time with the Cookie settings link at the bottom of every page, and we treat a Global Privacy Control signal from your browser as an opt-out. We do not use sensitive personal information to infer characteristics about anyone. We will not treat anyone differently for using their privacy rights.

8. Security

  • Data is encrypted in transit (HTTPS).
  • Access to production systems is limited to the people who run the service.
  • Requests from Shopify are verified with Shopify's signatures.
  • Google access tokens (Pro, if the merchant signs in with Google) are encrypted (AES-256-GCM); the key is kept separately from the database, they are never logged, and they are used only by our server to act on the merchant's own Tag Manager when the merchant asks.

See our Security Incident Policy for how we handle incidents.

9. Service providers (subprocessors)

Provider Purpose Location
Shopify App platform, billing Canada, the United States and other countries where Shopify operates
Render App hosting Oregon, United States
Render (managed PostgreSQL) Database Oregon, United States
Resend Setup, alert and support emails United States
Hostinger Email hosting for our support inbox (support messages and our replies) France and Germany (EU)
Sentry Error tracking for the app. When something fails on our servers, the error report can include technical request details and the store's domain. United States

10. International transfers

Our providers may process data outside your country. Where required, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses.

11. Children

dataMonitorio is a business tool for merchants and is not directed at children.

12. Changes

We will post updates here and change the "Last updated" date. For significant changes, we will tell merchants in the app or by email.

13. Contact

dataMonitorio
Chattogram, Bangladesh
Email: privacy@datamonitorio.com

Part B: This website and the partner program

Part A explains how the dataMonitorio Shopify app handles data. This part covers datamonitorio.com: what we collect when you visit, join the waitlist, contact us or apply to the partner program. For this data, we (dataMonitorio) are the controller.

B1. Information you give us

  • Waitlist: your email address and store URL, and optionally your name and the ad platforms you use.
  • Contact form and email: your name, email address, optional store URL and your message.
  • Partner applications: your name, work email, agency or business name, website, country, approximate number of Shopify clients, your LinkedIn profile (optional), anything else you choose to tell us, and a record that you accepted the Partner Agreement (which version and when).
  • Approved partners: your partner profile and notification choices, records of sign-ins, payout details (Wise account email, or bank details) and commission and payout records. Bank account numbers are stored encrypted, and only authorised members of our team can see them in full, with every view logged. We send payout details to Wise to pay you.

B2. Information collected automatically

  • Server logs: our hosting provider records technical details of each request, such as IP address, browser type, the page requested and the time. These are used to run and secure the website.
  • Form details: when you send us a form, we store it with the date and time and your browser and device type. We don't store your IP address with it.
  • Cookies: the website uses a few cookies it needs to work, and analytics and advertising cookies only if you agree to them in our cookie banner. See our Cookie policy.
  • Analytics and advertising: with your consent, we use Google Tag Manager (with a server container hosted by Stape), Google Analytics 4, Google Ads and Meta (the Meta Pixel and Conversions API) to understand how visitors use the website and to measure and improve our own ads. These tools collect information such as the pages you view, the website or ad that brought you here, your device and browser, an approximate location based on your IP address, and identifiers stored in cookies. If you send us a form after consenting, a hashed (SHA-256) copy of your email address may be shared with Google and Meta to measure whether our ads led to that sign-up. Until you consent, these tags don't set analytics or advertising cookies (Google Consent Mode).
Purpose Legal basis (GDPR / UK GDPR)
Emailing you when dataMonitorio launches (waitlist) Your consent, which you can withdraw at any time
Replying to your messages Our legitimate interest in answering questions about our service
Reviewing partner applications and running the partner program, including commission payouts Taking steps at your request before entering a contract, and performing that contract
Measuring how visitors use the website and the results of our advertising (analytics and advertising cookies) Your consent, which you can withdraw at any time with Cookie settings
Keeping the website secure and preventing abuse Our legitimate interest in protecting our service
Keeping records the law requires, such as payout and tax records Legal obligation

We do not sell your information. We use it for advertising only as described above: to measure and improve our own ads, and only with your consent.

B4. Who we share it with

  • Hostinger: hosts the website, stores the forms you send us in the website's database, and hosts our email inboxes.
  • Resend: sends the waitlist launch email and partner emails, when we use one.
  • Wise: sends commission payouts to approved partners.
  • Google (Tag Manager, Analytics, Ads) and Meta Platforms (Pixel and Conversions API): analytics and advertising measurement, only with your consent. They use the data under their own privacy policies.
  • Stape: hosts our server-side Google Tag Manager container, which passes consented analytics and advertising data to Google and Meta.
  • CookieYes: shows the cookie banner and keeps a record of your cookie choices.
  • Authorities, where the law requires it.

B5. How long we keep it

Information Kept for
Waitlist sign-ups Until you unsubscribe, or 12 months after we launch, whichever is sooner
Contact messages 24 months after the conversation ends
Declined partner applications 12 months
Approved partner records and payouts While you are a partner, then as long as tax law requires (6 years)
Google Analytics data 14 months, then deleted automatically by Google
Analytics and advertising cookies in your browser Up to 2 years; see the Cookie policy for each cookie
Record of your cookie choices 1 year
Server logs As set by our hosting provider, usually 30 days

B6. Your choices

  • Every waitlist email has an unsubscribe link, or you can email us to be removed.
  • You can accept or reject analytics and advertising cookies, and change your choice at any time with the Cookie settings link at the bottom of every page.
  • You can ask us to access, correct or delete the information you gave us, or to stop using it. See "Privacy requests" in Part A, which applies to this part too.