Privacy policy

Last updated 25 September 2026. Contact: jake@citamark.com.

TagStrike ("we", "us") helps you keep track of changes to your tag containers. A container is the box in Google Tag Manager that holds a site's tags. TagStrike also checks that your tags still work. This page says what we collect, why, and what choices you have. It covers the TagStrike web app, the monitor tag, the Slack app and the MCP link for AI helpers. MCP is a common way for AI tools to link to apps.

Data we collect

• Account data. Your name, email and profile photo from your Google sign-in. Also the workspace (your team's space in the app) you belong to, and the teammates you invite.
• Container data. The Tag Manager accounts and containers you pick to watch. Every version of them that goes live: tags, triggers, variables, templates, folders and settings. We also keep what changed from one version to the next. And we keep the results of our safety checks (lint rules) on each one.
• Monitoring data. Results of browser checks: page loads, the web requests each page made (network requests), and screenshots. If you turn on the monitor tag, we keep counts too. They show which tags and events ran on each page load. The monitor tag sends from 1 in 10 page views by default. You can change that in the app. It never sends web addresses of pages, with or without the part after a "?". It never sends form contents, cookies or IDs for users.
• Analytics data. If you turn on drop alerts, we read hourly event counts from the Google Analytics 4 properties you pick. A property is where one site's data is kept. We keep counts and normal ranges (baselines) only. We never keep reports about single users.
• Slack data. Your Slack workspace ID, our bot's key (bot token), and the channels you pick for each client. We post alerts to those channels. We do not read your messages.
• MCP use. Each call an AI helper makes with a TagStrike key (token): the tool name and what it sent. We keep this as a log (audit log) for your workspace.
• Activity log. What people on your team do in the app, like going back to an old version. It shows who did it and when.
• Technical data. Request logs kept by our host, Cloudflare. They hold your IP address (a number that points to your device's network), browser type (user agent) and times. They help with security and with fixing bugs. Requests from the monitor tag also reach our host. Like any web request, they carry the visitor's IP address and browser type. We use the IP address only to block abuse. We don't save either one with your counts.

How we use Google user data

We ask for Google access (OAuth scopes) one feature at a time:

• Sign-in uses only your basic profile.
• Connecting containers asks to read Tag Manager. It can't make changes.
• Two features ask to edit in Tag Manager: adding the monitor tag for you, and AI drafts.
• Two things ask to make versions and publish them in Tag Manager. They are going back to an old version (rollback), and approving an AI draft. We ask only when you turn that feature on.
• Drop alerts ask to read Analytics. They can't make changes.

We use this access only to run the features you turned on. That means we check for new versions and save copies of them. We find what changed. We run safety checks and browser checks. We add the monitor tag or your AI helper's changes to a separate draft space. When you approve a draft, we turn it into a new version and publish it. We publish the old versions you choose to go back to. And we read event counts.

TagStrike'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.

How we store and protect data

We store data with Cloudflare, our web host (on its D1, R2 and Workers services). We encrypt the keys to your Google and Slack accounts (refresh tokens and bot tokens) before we save them. We use AES-256-GCM. That means we scramble them with strong code. The key that unscrambles them is kept apart from the database, in a locked store (Workers secrets). All traffic uses HTTPS, the safe kind of web link. Only the TagStrike team can reach the live system.

How long we keep data

• Versions, changes and safety check results: as long as you watch the container. We delete them within 30 days after you remove it.
• Browser check results and screenshots: 90 days.
• Monitor tag counts and hourly Google Analytics counts: about 5 weeks (35 days).
• Normal ranges: while drop alerts are on, we work them out again each day. If you turn drop alerts off, we delete them after about 5 weeks. We also delete them when you stop watching the container.
• Alerts and AI helper (MCP) logs: 12 months.
• AI helper drafts: as long as you watch the container.
• Your account and your team's activity log: as long as your workspace exists.
• Request logs at Cloudflare: as long as Cloudflare keeps them, most often 7 days.

Deleting data and removing access

You can stop watching a container in the app at any time. To remove our Google access, use your Google account permissions page. That stops us from reading your containers right away.

To delete your workspace or your account and all your data, email jake@citamark.com at any time. We will confirm within 30 days.

Sharing

We share data only with the services we need to run TagStrike. That is Cloudflare, which hosts it, and Slack, when you add our Slack app. We share it with no one else, unless the law says we must. We do not sell personal data.

Your rights

Where you live may give you rights over your personal data. You may be able to see it, fix it, get a copy of it, or have it deleted. You may also be able to object to how we use it. Email us and we will help.

Changes

We will post any updates on this page. For big changes, we will email workspace owners before the changes start.