Tag Docket

Legal

Privacy Policy

What we collect, why, who else processes it, and what we deliberately don’t hold.

Effective: November 10, 2026

Tag Docket is operated by MM Sanford, LLC, which is the controller of the personal data described in this policy. The agency decides what it puts into Tag Docket about its clients and campaigns.

What we do not store

  • Passwords. There are none. You sign in with a link emailed to you.
  • Who scanned a code. A short-code scan adds one to that code’s count and updates its last-scanned time. We do not store the scanner’s IP address, device, browser or location. The browser’s user-agent string is read at the moment of the redirect only to leave link-preview bots and crawlers out of the count, and is not kept.
  • Trackers. This website uses Google Tag Manager to load Google Analytics, which measures visits to its pages, Google Ads conversion measurement, which tells us whether a visit from one of our ads led to a free trial or a paid subscription, and HeyCatch analytics, which measures visits from our social posts (see “Information collected automatically”). The app at app.tagdocket.com runs no third-party analytics; the exceptions are a single report to Google Ads when you start a free trial, and another when a payment for a plan completes. Neither runs session recorders.

Information you give us

  • Account data. Your name, work email, the agency you belong to, your role and which clients you can reach. Sign-in links are created and verified through Firebase Authentication, a Google service, and emailed through Resend. When you start an agency yourself, we also record that you accepted the terms and this policy, and when.
  • Registry content. Clients, campaigns, your taxonomy of dimensions and values, pairing rules, templates, and the links, short codes and QR codes you make, including their destinations. Each change is recorded in an audit trail with the email address of the person who made it, and stays attributed to them after they leave the agency.
  • Imported files. Spreadsheets you import, as the rows you choose to write, whether uploaded in the app or sent from the Google Sheets add-on.
  • Branding. For the white label, the agency website you paste in, and the color and logo taken from it.
  • Messages you send us. Anything you write in the contact form or by email, along with the agency you tell us about.
  • Billing data. Paid plans are billed through Stripe. Card details are entered on Stripe’s systems and never reach ours. We keep a customer reference, your plan and your subscription status.

Google Analytics 4 connections

An agency can let Tag Docket read a client’s GA4 property in one of two ways.

  • A service account. Each agency has its own Google service account; none is shared between agencies. It can read a client’s property only after someone with admin rights on that property adds it in GA4, and removing it there revokes access at once.
  • Signing in with Google. An agency owner or admin can instead sign in with their own Google account and grant Tag Docket read-only access to Google Analytics (analytics.readonly), plus their email address so the agency can see whose account a client reads through.

Either way, access is read-only: Tag Docket cannot change anything in a GA4 property.

What we read from Google, and why

  • Your properties’ names and IDs, listed when you connect, so you can pick a client’s property instead of typing its ID.
  • Session counts and key-event counts by campaign tag (source, medium, campaign, content and landing page) for the last 30 days, and a 7-day session total when a connection is tested. We read these only to show the agency which of the links it created in Tag Docket brought traffic, and which tags in GA4 did not come from Tag Docket.

We do not read anything about the individual visitors in those reports; GA4 gives us totals per tag, not people.

What we keep

  • The report totals above, cached for up to six hours so that browsing the History page does not spend the property’s daily quota. Each refresh replaces the last. They are deleted with the client or the agency.
  • For a Google sign-in: the Google account’s email address and Google’s account ID, and the refresh token Google issues. The token is encrypted before it is stored (see How we protect data), is never shown to anyone or written to logs, and is used only to make the reads described above. Disconnecting the account in Settings revokes the token at Google and deletes it from our database. You can also revoke it yourself at any time at myaccount.google.com/permissions.

Limited Use

Tag Docket’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. In particular, we use Google user data only to provide the features described above to the agency that connected it. We do not sell it, use it for advertising, share it with anyone except the processors listed below as needed to run the service, or use it to train machine-learning models, and nobody at Tag Docket reads it except with your agreement, for security, or where the law requires.

Google Sheets add-on

The Tag Docket add-on for Google Sheets works only in the spreadsheet you open it in, and reads it only when you use one of its commands. It cannot open any other file in your Google Drive.

What it reads and sends us

  • The cells you select, and the cells it needs to make sense of them: the header row, the column you mapped to each naming field, the Tag Docket ID beside a minted link, and the cells it is about to write into, so it never writes over something already there.
  • Sent to Tag Docket: the URLs and mapped values from those cells, to check them, mint links or import them. Nothing from the spreadsheet is sent anywhere else.
  • Written back: results go into the same spreadsheet as cell values, colors and notes, plus dropdown lists on a hidden tab named _tagdocket and, when you ask for it, a tab copying the client’s registry.

What is kept, and where

  • Checking without an account (in the add-on, or with the free link checker at tagdocket.com/check): the URLs are checked and the result sent back. Nothing about them is stored. To limit how often anyone can check, we count requests per email address (or per IP address, if there is none) in memory for an hour; the count is never written to a database.
  • Checking a GA4 export at tagdocket.com/check: the file or pasted table is read in your browser and never sent to us.
  • With an account: links you mint or import are stored in your agency’s registry like any other, as described above, with who made them and when.
  • Kept in Google, not by us: which client a spreadsheet is linked to, how its columns are mapped, the colors and notes a check replaced (so they can be put back), the agency you last chose, and a fingerprint of an import you previewed. The add-on saves these in Google’s own storage for the spreadsheet or for your account.

Sign-in

With each request the add-on sends a short-lived token, signed by Google, that confirms your Google email address. We check it to find your agency and then discard it. It gives Tag Docket no access to your Google account, your Drive or any other spreadsheet, and we store no Google token for the add-on. The Limited Use commitment above covers spreadsheet data in the same way.

The add-on’s permissions are to read and change only the spreadsheet it is opened in, show its sidebar, connect to Tag Docket, and see your email address. You can remove it in Sheets under Extensions, Add-ons, Manage add-ons, or at myaccount.google.com/permissions.

Chrome extension

The Tag Docket extension for Chrome builds links from your agency’s naming rules and checks the tagged links on pages you choose. It has no analytics and no tracking of its own.

Checking links

When you check a page, a link or the address of the tab you’re on, the check runs inside your browser. The page, its links and its address are never sent to Tag Docket or anyone else, and you don’t need an account. The extension reads a page only when you ask it to: after you click its toolbar button or right-click menu on that page, or on any site if you choose to allow that in its settings.

Building links

When you build a link, the destination, the values you pick and the campaign are sent to Tag Docket to be checked and recorded in your agency’s registry, exactly as they are in the web app, with who made the link and when. A value you ask to be added is sent to your agency’s admins for approval. Inserting a link into a field on a page types it into that field and sends nothing.

Sign-in and what is kept in your browser

You sign in with Google. The extension receives a short-lived token, signed by Google, that confirms your email address; it sends it with each request, and we check it to find your agency and then discard it. It gives Tag Docket no access to your Google account. The token is held in your browser’s memory for the session only. The extension also keeps, in your browser: your email address (to renew the sign-in), the agency and client you last chose, which client you last built links for on each website, and the link you were working on, for up to an hour. None of this leaves your browser except as part of a request you make. Signing out, “Forget” in its settings, or removing the extension deletes it.

How we protect data

The most sensitive data we hold is the Google refresh token from a GA4 sign-in, because it lets Tag Docket read that account’s analytics. It gets the most protection, on top of the measures that cover everything else.

Google sign-in tokens

  • Encrypted before storage. The refresh token is encrypted with AES-256-GCM by the application before it is written to the database. Each encrypted token is bound to the agency and Google account it belongs to, so it cannot be decrypted for any other agency.
  • The key is kept apart from the data. The encryption key is held in Google Cloud Secret Manager, not in the database or the code. Only the service’s own runtime account can read it, so a copy of the database alone does not reveal any token.
  • Short-lived access. We store only the refresh token. The access tokens made from it last about an hour, are held in memory only and are never stored.
  • Never exposed. Tokens are never sent to a browser, shown in the app, included in exports or written to logs.
  • Restricted to admins. Only an agency’s owners and admins can connect or disconnect a Google account. The sign-in uses PKCE and a one-time state value, so an intercepted authorization code cannot be used by anyone else.
  • Read-only and revocable. We request read-only access to Google Analytics and nothing more. Disconnecting revokes the token at Google and deletes it from our database.

All data

  • Encrypted in transit. The app and this website are served over HTTPS only, and the connection between the app and its database is encrypted.
  • Encrypted at rest. The database and its backups are encrypted at rest by our database provider, Neon.
  • Least privilege. The service runs under its own Google Cloud account, which can read only the secrets it needs. Deploying uses a separate account, and neither is the project’s default account, which can change almost anything in the project.
  • Separated by agency. Every request is checked against the signed-in person’s agency and role, and each agency’s data is scoped to that agency (see Keeping agencies separate).
  • No passwords to steal. Sign-in is by emailed link through Firebase Authentication, so we hold no passwords.

Pages we fetch for you

The landing-page check fetches the destination you enter, to see whether it loads, redirects, carries an analytics tag or already has UTM parameters. The white-label check fetches the agency website you paste in. Both fetch only public web pages at the address you supply, identify themselves in the request, and refuse private and internal network addresses.

Information collected automatically

  • Short-code scans. A count and a last-scanned time per code, as described above. Nothing about the person scanning.
  • Hosting logs. Our hosting provider’s standard request logs record details such as IP address, browser and time for operating and securing the service, and are kept for 14 months. Contact-form submissions store a one-way hash of the sender’s IP rather than the address, which is enough to limit abuse.
  • HeyCatch. This website also uses HeyCatch analytics. It stores a random identifier in a first-party cookie and your browser’s local storage, and sends HeyCatch the pages you view, the links and buttons you click, the page that referred you, your browser and device type, and an approximate location derived from your IP address. We use it to see which of our social posts and videos bring visitors, and what they read. Short links of a single letter or digit on tagdocket.com (such as tagdocket.com/a) are how those posts link here, and they add which post it was to the address. HeyCatch is not used in the app. You can block it with any common content blocker.
  • Website analytics. On this website, Google Tag Manager loads Google Analytics, which sets first-party cookies and sends Google details of your visit: the pages you view, whether you click through to start a free trial, how many links you run through the free link checker and how many pass (never the links themselves), how many rows of a GA4 export you check there and how many split values it finds (never the export itself), the page that referred you, your browser and device type, and an approximate location derived from your IP address. We use it to see which pages are read, where visitors come from, how many go on to the signup page, and how much the checker is used. You can block it with any common content blocker, or with Google’s Analytics opt-out add-on.
  • Advertising measurement. When you arrive at this website from one of our Google ads, Google Tag Manager stores Google’s identifier for that ad click in a first-party cookie on tagdocket.com, kept for up to 90 days. If you then start a free trial, the app loads Google Tag Manager once, on the signup page, right after your agency has been created, and reports the signup to Google Ads with that click identifier and your agency’s short name as the reference. If you later pay for a plan, the app loads Google Tag Manager once, on the page you return to after paying, and reports the purchase to Google Ads with that click identifier, an order reference, the amount before tax, the currency, the plan and whether it is your agency’s first subscription. It is sent only after we have confirmed the payment with Stripe. Like any request your browser makes, it also carries that page’s address, which contains your agency’s short name from the app’s web addresses. Neither report includes your name or email address. We use them to learn which ads lead to trials and customers, and Google uses them to measure and optimize those ads. You can block them with any common content blocker, or manage how Google uses ad data at myadcenter.google.com.
  • Browser storage in the app. Only what signing in requires, plus conveniences such as remembering the email address you last used, and a note that a payment has already been reported so it is not reported twice. The app sets no analytics cookies; the signup page, and the page you return to after paying, can read the ad-click cookie described above.

This site loads its typefaces from Google Fonts, so your browser fetches those files from Google and Google sees the request.

How we use it

To run the service, send sign-in links, check short-code destinations against Google’s list of unsafe sites, answer you when you get in touch, bill you, and keep the system secure and working. We do not sell personal data, we do not share it for advertising, and we do not use registry content to train machine-learning models.

Who else processes it

  • Google Cloud (Cloud Run, region us-east5, Ohio) hosts the app.
  • Firebase Authentication (Google) creates and verifies sign-in links.
  • Resend delivers sign-in, invitation and account emails.
  • Google Web Risk receives the destination address of each short code when it is created or changed, to check it against Google’s list of unsafe sites.
  • Neon hosts the Postgres database, on AWS in us-east-2 (Ohio).
  • Stripe processes payments for paid plans.
  • Google Ads receives the purchase report, and the free-trial report, described under “Advertising measurement”, to measure our ads.
  • Google Analytics Data and Admin APIs are used for the GA4 connections your agency sets up.
  • Google Tag Manager and Google Analytics measure visits to this website (not the app).
  • HeyCatch measures visits to this website (not the app), as described under “Information collected automatically”.
  • Firebase (Google) hosts this website and stores contact-form submissions, and Resend delivers those submissions to our inbox.

Each processes data only to provide its service to us. We will update this list before adding another, and note the change in the effective date above.

Keeping agencies separate

Each agency’s data is scoped to that agency. A member list never shows which other agencies a person belongs to, and a member limited to certain clients cannot see that other clients exist.

Export and moving to another agency

Records about a client belong to that client. An agency can export a client’s records at any time, free, in a readable format with values written out in full. If a client moves to another agency on Tag Docket, the receiving agency requests the transfer and the agency holding the client approves it. If that agency declines or does not answer within 14 days, we may approve it at the client’s request, and we record a note of why with both agencies. Once approved, the client’s records move to the receiving agency, and the outgoing agency keeps a read-only archive of the work it did.

How long we keep it

Registry content is kept while the agency’s account exists. Canceling a plan deletes nothing, and retiring a client archives it rather than deleting it, because printed codes must keep resolving. An account that has never paid moves to the free plan when its trial ends, and is kept while it is in use. It is deleted with its content only after a year with no activity: nobody signing in or using the service, no links made, and none of its short codes scanned. Its owners are emailed 30 days beforehand, and any activity in that time keeps it. An account that has ever paid is never deleted this way.

An account owner can ask us in writing to close the account and delete its data. We will talk through an export first if you want one, and then delete the account within 30 days of the request. Database backups roll over every 7 days, so deleted data is gone from them 7 days after it is deleted from the live service.

Contact-form messages are kept for 14 months, and hosting logs for 14 months.

Your rights

You can see and export your agency’s data from inside the app at any time, and ask us to correct or delete personal data about you. If you are a client of an agency that uses Tag Docket, ask that agency first; we will help them answer. Depending on where you are, laws such as the GDPR or the CCPA may give you further rights, including the right to object or to complain to a supervisory authority. Ask us and we will help you exercise them.

Where data is held

Tag Docket runs in the United States, and so does every processor listed above. If you are outside the United States, using the service means your data is processed there. For personal data from the European Economic Area, the United Kingdom or Switzerland, we rely on the European Commission’s Standard Contractual Clauses (with the UK Addendum), and on our processors’ certifications under the EU-U.S. Data Privacy Framework and its UK and Swiss extensions where they hold them.

Children

Tag Docket is a business tool and is not directed to anyone under 18.

Changes to this policy

We post changes here and update the effective date. We email account owners about material ones before they take effect.

Contact

Privacy questions, or a request about your own data: hello@tagdocket.com. MM Sanford, LLC, Green Bay, WI.