Tracking Watch privacy policy.
Tracking Watch checks that an agency's analytics and advertising tracking (Google Analytics 4 and Meta) keeps working, and tells the agency when it stops. This policy explains what Tracking Watch collects, why, and what you can do about it.
Tracking Watch is built and run by Nathanael Tyre Conway, operating as Tyred Labs (nathanaeltyre.ai). Questions go to contact@nathanaeltyre.ai.
What Tracking Watch collects
- Your Google sign-in details. When you choose "Continue with Google", we receive your name, email address and Google account ID. We use them to create your account and sign you in.
- Read-only Google Analytics access. With your permission (
analytics.readonly), we read the list of Analytics accounts and properties your Google login can see, and the tracking data needed to check that events are still arriving. We cannot change anything in your Analytics account. - Read-only Meta access. If you connect Meta, and with your permission (
ads_read), we read your Meta user ID, name, the permissions you granted, and the ad account and pixel data needed to check that your pixel is still firing. We cannot change your ads or pixels. - Connection details. Which accounts are connected, the permissions granted, when access expires, and whether the connection is healthy.
- Check results. When each check ran and whether it passed, with a status code when it failed.
- A sign-in cookie. One random cookie keeps you signed in. We store only a one-way hash of it. Tracking Watch uses no advertising or third-party tracking cookies.
How it's used
Only to run the service: sign you in, run your checks, show you their status and alert you when tracking breaks. Tracking Watch does not sell your data, does not use it for advertising, and does not use Google user data to train AI or machine-learning models.
Google API Services. Tracking Watch'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 access is protected
The access Google and Meta give us is stored encrypted (AES-256-GCM, a separate key for each connection) in a part of the database only one internal service can read. Short-lived Google access is held in memory for at most five minutes and never saved. Access tokens are removed from logs and error reports. Each agency's data is kept separate from every other agency's at the database level.
Who else handles it
Only the services that run Tracking Watch, under their own security terms:
- Vercel hosts the app.
- Neon hosts the database.
- Inngest schedules the checks. It receives check IDs and timing, not your Google or Meta access.
- Healthchecks.io receives an "I'm alive" signal from our scheduler. It receives no data about you.
We disclose information to others only if the law requires it.
Where it's stored
In the United States.
How long we keep it, and how to delete it
- Disconnecting a Google or Meta connection in Tracking Watch revokes our access with Google or Meta and deletes our stored copy of it right away.
- You can also remove our access yourself at any time, from your Google account permissions or from Meta's Settings, then Business Integrations.
- Everything else is kept while your account is open. To delete your account and its data, email contact@nathanaeltyre.ai. It is deleted within 30 days.
Children
Tracking Watch is a business service and is not meant for anyone under 16.
Changes
If this policy changes, the "Last updated" date changes with it. If a change affects how your data is used, we'll email account holders before it takes effect.