GTM Spyby Trackable

Data processing agreement

Draft, under review. Last updated 15 November 2026.

This agreement is between you, the business using GTM Spy (usually an agency, for its clients), and GTM Spy, run by [legal entity, address, company number]. It forms part of our terms of use: you accept it with the terms, and it applies from the moment your team adds a client or connects a client's account. It is meant to meet Article 28 of the UK GDPR. Where it and the terms differ about personal data, this agreement wins.

Who is who

  • You are the controller of the personal data you or your clients give GTM Spy to process. If you act for a client as its processor, your client is the controller, we are your sub-processor, and you confirm you may appoint us.
  • GTM Spy is the processor of the data in your clients' connected accounts and the client data you add to your team, described below.
  • GTM Spy is the controller of the data about your own account (your sign-in, your team's members, billing and security logs), as the privacy notice describes. This agreement doesn't cover that data.

Your duties as controller

  • You have a lawful basis for the personal data you bring to GTM Spy, and for asking us to process it.
  • You are allowed to connect each client account you connect, and to give us the access you give, and you have told the people concerned what they need to know.
  • Your instructions to us comply with data protection law.

What we process, and why

  • Subject matter: auditing and monitoring the tracking of your clients' websites, and the advertising, analytics and shop accounts you connect to them.
  • Duration: while your team uses GTM Spy, and until the data is deleted as set out under At the end.
  • Nature: collecting, storing, reading, organising, comparing and deleting; and, only where you turn on “Allow changes in Tag Manager” for a client, changing that client's Tag Manager when you ask us to.
  • Purpose: providing the service to you: audits, monitoring, your team's issues and shares, emails and alerts, the API, and the Tag Manager changes you ask for. We don't use the data for anything else, including our own marketing or training AI models.

Types of personal data

  • The name or email address of the person who connected a client's Google or Meta account (or, once it is switched on, Shopify shop).
  • The access they gave us (stored encrypted), and what we read with it: account, property and container names and IDs, settings, tags and counts. Shopify orders (once switched on) are read as times, sources, channels and totals; we don't ask for customer details.
  • What your team adds about a client: its name and website, notes, issues and comments, and the people you share results with.
  • Anything personal that is in what we read, such as a name in a Tag Manager tag or a comment.

We don't ask for special category data, and an audit never collects the data of the visitors to the websites we audit.

Categories of data subjects

  • Your clients' staff and contractors who connect accounts, or who are named in them.
  • Your own staff, where they appear in client data (for example in a comment).
  • The people you share results with.
  • Anyone else named in notes, comments or the accounts we read.

Our duties as processor

We will:

  • Act only on your documented instructions, including on transfers abroad. This agreement, the terms and what you do in GTM Spy (or through your API key) are your instructions. If the law requires us to do something else, we will tell you first, unless the law forbids it.
  • Tell you immediately if we think an instruction breaks data protection law, and we need not follow it until you confirm or change it.
  • Keep it confidential: only people who need it for the service can access it, and they are bound to confidentiality.
  • Keep it secure with appropriate technical and organisational measures (Article 32): the schedule below, with the detail on the security page.
  • Use sub-processors only as set out below.
  • Help you answer requests from people exercising their rights (access, correction, deletion, objection and the rest), as far as the service allows, and pass on any request we receive directly.
  • Help you meet your own duties on security, personal data breaches, data protection impact assessments and consulting the Information Commissioner (Articles 32 to 36), taking into account what we know.
  • Tell you about requests from authorities: if a court, regulator or government body asks us for your data, we will tell you, unless the law forbids it, and give only what we are legally required to.
  • Delete or return the data at the end, as set out below.
  • Give you the information you need to show that these duties are met, and allow and contribute to audits, as set out below.

Sub-processors

You give us general authorisation to use sub-processors. They are listed on the sub-processors page. We will tell your team's owners by email at least 30 days before we add or replace one, and update that page. You may object within those 30 days on reasonable data protection grounds. If we can't meet your concern, you may stop using the affected part of the service or close your account.

Each sub-processor is bound by a written contract with data protection terms at least as protective as these. We remain responsible to you for what they do with your data.

Transfers outside the UK

We transfer data outside the UK only with a safeguard the UK GDPR accepts. The sub-processors page says where each one works. As we understand them today (to be confirmed):

  • Hostinger (the scanner's server): in the UK, so no transfer.
  • Resend: sends from the EU, covered by the UK's adequacy regulations for the EU and EEA [safeguard for its US parent to be confirmed].
  • Cloudflare, Google, Meta and Stripe: the UK-US data bridge, or else the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses.
  • Shopify: the UK's adequacy regulations for Canada.
  • Anthropic: the IDTA or the UK Addendum [to be confirmed].

If you are in the EU or EEA, your transfers to us in the UK rely on the EU's adequacy decision for the UK. If that stops applying, the EU Standard Contractual Clauses apply between us, and this agreement is read as including them.

Personal data breaches

If we become aware of a personal data breach affecting your data, we will tell you without undue delay, and no later than 48 hours after we become aware of it. We will tell you what we know of what the UK GDPR asks you to report (Article 33(3)): what happened, the kinds and rough numbers of people and records affected, the likely consequences, what we have done and will do about it, and who to contact. Where we don't know everything yet, we will tell you in stages, as we learn more, so you can meet your own duty to tell the Information Commissioner and the people affected.

At the end

  • Disconnecting a client's account removes the connection at once. Where no other client uses the same Google login, Meta user or shop, we also withdraw the access with the platform and delete our copy of the token; otherwise the token stays, sealed, for those connections only. Removing a client disconnects its accounts the same way.
  • When your team stops using GTM Spy, or at your written request, we delete the personal data we process for you within [period to be confirmed], unless the law requires us to keep it.
  • Before that, you can ask us to return it. We will send it in a common, machine-readable format (such as CSV or JSON).
  • Deleted data leaves our backups within 30 days, as they expire.
  • On request, we will confirm the deletion to you in writing.

To ask for deletion or a copy, email hello@gtmspy.io from your account's address.

Information and audits

We will answer reasonable written questions about how we process your data, and give you what you need to show that this agreement is kept. If that is not enough, you (or an auditor you appoint, bound to confidentiality) may audit our compliance, with at least 30 days' notice, at most once a year unless a regulator requires it or after a breach, in a way that doesn't expose other customers' data.

Costs

What the service does by itself (disconnecting, removing clients, the answers on this site) costs nothing extra. For other help we give under this agreement, and for audits, we may charge our reasonable costs, which we will tell you first. We won't charge for an audit that finds we broke this agreement, or for help with a breach that was our fault.

How long it lasts

This agreement lasts while we process personal data for you, and ends when that data is deleted or returned. What it says about confidentiality, deletion, breaches and audits goes on applying to any of your data we still hold after your account closes.

Changes to this agreement

We may update this agreement to meet a change in the law or in the service. We will tell your team's owners by email at least 30 days before a change that matters to you takes effect, and we won't reduce the protection it gives your data without your agreement.

Schedule: security measures

A summary; the security page has the detail.

  • Least access: read-only permissions on connected accounts, except Google Ads, which has no read-only permission (we only read).
  • Changes only when allowed: Tag Manager changes are off per client until an owner or admin turns them on; each change is a dry run first, made only with that dry run's token, and deleting or publishing needs a confirmation.
  • Encryption: platform tokens are encrypted (AES-256-GCM) before they are stored; the website is served over HTTPS only.
  • Separation: each team sees only its own clients, connections and results.
  • Sign-in: work email addresses only; passwords stored as a hash; breached passwords refused; sign-in codes stored as a hash and short-lived; sign-in attempts rate-limited.
  • Records: each use of a connection is logged (who, what, when).
  • Secrets: keys are kept as secrets of our hosting, never in the code or the database.
  • Backups: the accounts database can be restored to any point in the last 30 days; the scanner's database is copied every night and each copy is deleted after 30 days.
  • Monitoring: the website, the scanner and the backups are checked every 5 minutes, with alerts to us.

Law

This agreement is governed by the law of England and Wales.