Privacy policy
What we collect, why, and who receives it. Written to be read.
Last updated 19 November 2026
Who we are
Tagbreeze is a conversion tracking service operated by Webotic, a company based in Morocco (webotic.ma). For any question about this policy or your data, write to privacy@tagbreeze.com.
Webotic SARL AU, 332 Bd Brahim Roudani, Maarif, Casablanca, Morocco. Trade register (RC) 581231, ICE 003279900000014.
Two kinds of data, two roles
Tagbreeze handles data about two groups of people, in two different roles.
- Account holders: people who sign up to Tagbreeze to track their own website. For this data Webotic decides why and how it is used: we are the controller.
- Visitors of tracked websites: people who browse a website where an account holder installed the Tagbreeze tag. The website owner decides what is tracked and where it is sent: the owner is the controller and Webotic is its processor, acting on its instructions under the data-processing terms in our Terms of service.
Data about account holders
- Your e-mail address, whether it has been confirmed, and a one-way hash of your password if you chose one. We never store the password itself.
- If you sign in with Google or Facebook: we receive your e-mail address from that provider and nothing else. We do not receive your password, your contacts or your profile content, and we do not post anything.
- The websites you add, the result of the analysis of their public pages, and your tracking settings.
- The identifiers of the ad and analytics accounts you connect (for example a Meta dataset ID, a Google Analytics measurement ID, a Google Ads conversion ID and labels, a Tag Manager container ID, a TikTok pixel ID).
- Access tokens you paste, or that a platform issues when you connect an account in one click. They are stored encrypted, are never shown again in the console, and are used only for what is described in the next section.
- Your plan and subscription status. Payments are handled by PayPal: we never see or store your card or bank details.
- One session cookie,
mt_s, that keeps you signed in for up to 30 days. It is the only cookie the Tagbreeze console sets. The console uses no analytics and no advertising trackers. - Technical records needed to run and protect the service, such as the IP address used to limit repeated sign-in attempts. These are short-lived.
Access to your Google, Meta and TikTok accounts
When you connect an account in one click, the platform shows you exactly what Tagbreeze asks for. Here is what each access is, and what we do with it.
- Sign in with Google: your e-mail address only, to create your account and sign you in.
- Google Analytics (read-only): the list of your Analytics accounts, properties and web data streams, so you can pick the measurement ID of your site. We read nothing else and change nothing.
- Creating a Google Analytics property (edit access, asked only if you choose it): if you have no property for your site and press "Create a new property for this site", Google asks you for one more permission, to edit Google Analytics. Tagbreeze never asks for it otherwise. After you pick the Analytics account and confirm, Tagbreeze creates one property named after your site and one web data stream in it, and reads back its measurement ID. It changes or deletes nothing else. Tagbreeze asks for no long-lived access here: the access lasts at most one hour and we delete it as soon as the property exists. Your Google account page keeps listing the permission until you remove Tagbreeze's access there.
- Google Tag Manager (read and write): the list of your accounts and containers, so you can pick one. In the container you pick, and only after you confirm, Tagbreeze creates one workspace, adds one Custom HTML tag (the Tagbreeze tag), creates a version and publishes it. If you have no container for your site and ask for one, Tagbreeze creates one web container named after your site in the Tag Manager account you choose, after you confirm, and publishes its tag in it. We do not read, change or delete your other tags or containers.
- Google Ads: the list of the Google Ads accounts you can reach, and the website conversion actions of the account you pick. Tagbreeze reads those conversion actions and creates the ones that are missing for your tracking plan. We do not change your campaigns, ads, budgets, audiences or billing.
- Google Ads spend reports (only if you choose a Google Ads account in the "Ads" tab of a site): for that account, Tagbreeze reads the name of each campaign and, per day, its cost, impressions, clicks, conversions and conversion value, to show your return on ad spend beside the sales the tag recorded. This is read-only. The figures are stored with your site and deleted with it, or when you remove the account from that tab.
Tagbreeze's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. In practice: Google user data is used only to provide the set-up features described above, which you see and trigger yourself in the console; it is not sold, not used for advertising, not used to train artificial-intelligence models, and not read by people at Webotic unless you ask us for support, it is needed for security, or the law requires it.
Meta
- Sign in with Facebook: your e-mail address only.
- Connecting Meta ads (permissions
ads_managementandbusiness_management): the list of your ad accounts, your business portfolios and their datasets (pixels), so you can pick one, and the right to send conversion events to the dataset you pick through the Conversions API. If you have no dataset for your site and press "Create a new dataset for this site", Tagbreeze creates one dataset named after your site in the ad account or business portfolio you choose, after you confirm; this uses the same permissions, and nothing is created unless you ask. We do not create or edit ads, and we do not read your audiences, messages or page content. - Meta spend reports (permission
ads_read, only if you choose an ad account in the "Ads" tab of a site): for that ad account, Tagbreeze reads the name of each campaign and ad and, per day, its spend, impressions, clicks, and the purchases and leads Meta reports, to show your return on ad spend beside the sales the tag recorded. This is read-only. The figures are stored with your site and deleted with it, or when you remove the account from that tab.
TikTok
- The list of your advertiser accounts and their pixels, so you can pick one, and the right to send events to the pixel you pick through the Events API.
You can withdraw any of these accesses at any time: see Delete your data.
Data about visitors of tracked websites
When the Tagbreeze tag runs on a website, it can collect:
- the address of the page and of the referring page, with sensitive parameters removed;
- the actions the website owner chose to measure (a purchase, a form sent, a click on a phone number…), with their value, currency, order number and product details when the page provides them;
- a first-party visitor identifier and the click identifiers that ad platforms add to links (see the table below);
- where the visit came from: the campaign parameters of the link (
utm_source,utm_medium,utm_campaign,utm_content), whether the visitor clicked an ad of Meta, Google, TikTok or Bing, and the name of the referring website. With consent, this is kept for the first and the latest visit and stored with each purchase or lead, so the owner can see which campaign brought it; - a customer reference: a one-way hash, different on every website, of the visitor identifier or of the hashed e-mail address. It lets the owner see that two purchases come from the same customer. It cannot be turned back into an identifier or an address, and is only made with consent;
- an e-mail address or phone number typed in a form or at checkout. It is turned into a SHA-256 hash on the visitor's device, by the tag and inside the Shopify checkout pixel, before anything is sent. Tagbreeze never receives the readable value;
- the IP address and browser user agent of the request. They are used to protect the service and, with consent, passed to the ad platforms the owner connected so they can attribute the conversion. They are not stored with the events.
Consent
By default the tag waits for the visitor's choice in the European Economic Area, the United Kingdom and Switzerland. It reads that choice from Google Consent Mode, from the IAB TCF signal or from the common consent tools when the website has one, or shows its own simple banner when the owner switched it on.
Before consent, or when it is refused: the tag sets no identifier, loads no advertising pixel, and sends Tagbreeze only cookieless counts (the name of the event, the page address without sensitive parameters, and the time). Nothing is forwarded to ad platforms.
With consent: the identifiers below are set, the pixels the owner connected are loaded, and events are sent to those platforms from the browser and, for Meta and TikTok, from our servers.
The website owner can switch this waiting off. The owner is then responsible for collecting consent another way where the law requires it.
Cookies and storage used by the tag
The tag stores the following on the visitor's device, under the tracked website's own domain.
| Name | Where | Purpose | Kept for | Needs consent |
|---|---|---|---|---|
_mt_id | Cookie | First-party visitor identifier, used to recognise the same browser and to match browser and server events. | 390 days | Yes |
_mt_c | Cookie | Remembers the visitor's consent choice so the banner is not shown again. | 180 days | No (it records the choice) |
_mt_gclid | Cookie | Google Ads click identifier taken from the link the visitor followed. | 90 days | Yes |
_mt_ttclid | Cookie | TikTok click identifier taken from the link the visitor followed. | 90 days | Yes |
_fbc | Cookie | Meta click identifier taken from the link the visitor followed. | 90 days | Yes |
_fbp | Cookie | Meta browser identifier. The tag creates it when Meta's own pixel has not. | 90 days | Yes |
_mt_u | Local storage | Hashed e-mail address and phone number (SHA-256), kept so a later purchase can be matched. | 90 days | Yes |
_mt_at | Local storage | Where the first and the latest visit came from: campaign parameters, kind of ad click, referring website. | 90 days for the first visit | Yes |
_mt_tx | Local storage | Numbers of the orders already sent, so a reloaded confirmation page is not counted twice. | Until cleared by the browser | No (holds no personal identifier) |
_mt_d | Session storage | Events already sent during the visit, to avoid duplicates. | Until the tab is closed | No (holds no personal identifier) |
The pixels of Meta, Google and TikTok, when the owner connected them and the visitor consented, set their own cookies under their own policies.
Why we are allowed to use the data
- Account data: to perform the contract with you (create the account, run the service, bill it); our legitimate interest in keeping the service secure and in telling you when your tracking stops working; legal obligations for accounting records.
- Visitor data: the website owner chooses the legal basis as controller. Advertising identifiers and forwarding to ad platforms rest on the visitor's consent where the law requires it. Cookieless counts rest on the owner's legitimate interest in measuring its own website.
Who receives the data
We use the following providers (sub-processors) to run Tagbreeze:
- Cloudflare: hosting, network and database. Data is processed on Cloudflare's global network.
- PayPal: subscriptions and payments.
- Webotic's own notification gateway (notifications.webotic.agency) and the mail servers of o2switch (France): account e-mails such as address confirmation, password reset, alerts and trial reminders.
The website owner also chooses destinations: Meta, Google and TikTok receive the events of that website, each under its own terms. They are chosen by the owner and are not our sub-processors.
We do not sell personal data and we do not use it to build advertising profiles of our own.
Transfers outside your country
Webotic is established in Morocco, and its providers operate in several countries, including the European Union and the United States. Data can therefore be processed outside the country where you or your visitors live. Where the law requires a safeguard for such a transfer, we rely on the standard contractual clauses offered by our providers or on an adequacy decision. The destinations a website owner connects (Meta, Google, TikTok) carry out their own transfers under their own terms.
How long we keep it
- Account data: as long as the account exists. It is deleted when you delete the account.
- Recent events of a website, shown in the console to check that tracking works: the latest 200 per website, and never older than 30 days.
- Hourly event counts: 90 days.
- Purchases and leads with where they came from, and the daily figures read from ad accounts: 400 days, or until the website is deleted.
- API keys: until you delete them. Only a hash of each key is kept.
- Sign-in sessions: 30 days.
- Password-reset links: 1 hour.
- Billing records: as long as the law requires.
Security
All traffic is encrypted in transit. Passwords are stored as salted one-way hashes, access tokens are stored encrypted, and e-mail addresses and phone numbers of visitors are hashed on their own device before they reach us. Access to production systems is limited to the people who operate the service.
Your rights
You can ask to see, correct, export or delete your data, to restrict or object to its use, and you can withdraw a consent or an access you gave at any time.
- Account holders: the Account page of the console lets you export your data, change your password, revoke the access given to Tagbreeze and delete your account yourself. You can also write to privacy@tagbreeze.com. See Delete your data.
- Visitors of a tracked website: contact that website first, since it decides what is tracked. You can also write to us with the address of the website and we pass the request on and help the owner answer it.
We answer within one month. If you think your data is not handled properly, you can complain to a data protection authority: in Morocco the CNDP (cndp.ma), or the authority of the country where you live.
Changes
If this policy changes in a way that matters, we tell account holders by e-mail before the change applies.