Compliance on a Google Analytics project, end to end
The clauses are the visible part. What makes them worth having is that they keep matching the code after you stop paying attention.
It finds it without being told
AutomaticGoogle Analytics resolves from its package, its endpoint or its credential name — so an integration with no SDK installed is found like any other.
Clauses, not a template
The disclosures Google Analytics forces are assembled from a library built from published regulatory text, and filled in from the catalog row rather than from a guess about what the vendor does.
Every clause explained
Beside each one, in plain English: what it means, why your product needs it, and which detected component put it there — with the file and line it was proved from.
It notices when this changes
DriftLater scans are diffed against the snapshot your documents were generated from, so removing Google Analytics or adding something beside it becomes an update you approve.
Delivered where you work
As a pull request on a connected Git host, as an approval in the dashboard, or from your editor over MCP — the same six tools your agent can call without opening a browser.
Read in memory, not retained
The files a scan reads are processed in memory and dropped when the request ends; what is kept is the list of services it found. The MCP server goes further and scans on your own machine.
How Poliogo proves Google Analytics is there
Detection is pattern matching over what is literally in your repository — dependency manifests, source files, configuration, edge functions and `.env.example` — not a model's opinion about your code. Google Analytics resolves from any of the signatures below, so an integration written as a bare `fetch` with no package installed is found exactly like one with an SDK.
- ✓Three cookies, two of them two-year: _ga, _ga_* and _gid, every one classified Analytics and every one held until a visitor actively agrees.
- ✓Detected from gtag(, gtag.js, gtag/js and react-ga as well as the vendor's name — the needles are deliberately narrow, because a bare “g-” also matches posthog-js and a false vendor in a sub-processor schedule is a false statement.
- ✓Google Consent Mode v2 signals are sent on every plan including Free, so visitors who decline are still modelled in your reporting rather than disappearing from it entirely.
What Google Analytics changes in your documents
Google Analytics watches traffic — this needs consent in the EU/UK and an opt-out for US users. It tracks how people behave on your site, and behavioural tracking must be disclosed and consented to. That is why Google Analytics moves your Privacy Policy, Cookie Policy and Cookie banner — and it is the same sentence the Updates page shows when a scan finds it for the first time, because both are read from one place.
- ✓Privacy Policy — regenerated and shown as a diff before anything is published.
- ✓Cookie Policy — regenerated and shown as a diff before anything is published.
- ✓Cookie banner — regenerated and shown as a diff before anything is published.
Google Analytics in your sub-processor schedule
A sub-processor schedule names the legal entity, not the brand — Google LLC rather than "Google Analytics" — because that is the name a customer's data protection agreement is checked against. The row below is what Poliogo generates and what your Trust Center publishes.
| Field | Value |
|---|---|
| Legal entity | Google LLC |
| What it receives | IP address, page views, referrers, device and browser data, conversion events |
| Purpose | Measuring traffic and advertising conversions |
| Processing location | United States |
| Their privacy policy | policies.google.com/privacy |
Generated from the catalog entry, and published on your Trust Center alongside every other sub-processor a scan found.
Getting this onto a Google Analytics project
Nothing is written or published until you have seen it. The scan proposes, you approve, and only then does anything reach your repository or your live pages.
Connect the repository, the host or the live address. The scan reads manifests, source, configuration and `.env.example` in memory and keeps the list of services it found, not the files it read.
A plain-English list of every service the scan proved, Google Analytics among them, each with the file and the line it was found on. Correct anything wrong before a word is generated.
Privacy Policy, Cookie Policy and Terms, with the clauses Google Analytics forces already in them, and a plain-language explanation beside each one saying which detected component put it there.
Later scans are diffed against the snapshot your documents were generated from, so a service added next month becomes an update you approve rather than a quiet inaccuracy nobody notices.
Questions people ask
Does Poliogo detect Google Analytics on its own?
Yes. Google Analytics resolves from the signatures in the detection library — the package name, the endpoint it is called at, and the credential name it uses in `.env.example`. Matching on the endpoint is the part that matters: an integration written as a bare `fetch` with nothing added to package.json is still found, and that is the case a dependency-only scanner misses entirely.
What does Google Analytics actually receive from my users?
IP address, page views, referrers, device and browser data, conversion events — for measuring traffic and advertising conversions. That list is not written for this page: it is the catalog row the generated Privacy Policy prints, so what you read here is what your document will say, down to the categories.
Do I have to list Google Analytics as a sub-processor?
If it processes personal data on your behalf, yes — and the row names Google LLC, the legal entity, rather than the brand, because that is the name a customer's data protection agreement is checked against. Poliogo generates the row and publishes it on your Trust Center alongside every other sub-processor a scan found.
Where does Google Analytics process the data?
United States. That matters for the transfer clause rather than for the vendor list: an EU product sending personal data to a US processor owes a transfer disclosure whether or not anything else in the stack is American. The generated clause names the location from this same row rather than assuming one.
Which cookies does Google Analytics set, and are they blocked before consent?
_ga, _ga_*, _gid. Whether each one waits depends on its classification, not on its vendor: the ones marked strictly necessary are disclosed in the Cookie Policy and always allowed to run, because gating them breaks the thing they exist for, and anything classified Analytics or Marketing is held until a visitor agrees.
What happens when I add another service later?
A scan has to run first — manually on any plan including Free, or on your plan's schedule from Starter. When one finds a service your documents do not mention, the change arrives as a proposal with a plain-language diff: what changed, why, and which detected component triggered it. On a connected Git host it can also arrive as a pull request on a side branch, so changes reach your default branch only through a pull request you approve.
Is any of this legal advice?
No. Poliogo reads code and assembles clauses from a library built from published regulatory text; it does not weigh your circumstances, and no generated document settles whether a business is compliant — that turns on how the business actually handles data. What the product is for is making sure the documents describe what the software genuinely does, which is the part that goes stale on its own and the part a person cannot check by hand every week.
Compliance for the rest of your stack
See what a scan finds in your Google Analytics project
Connect it and read the list before anything is generated. Free plan, no credit card, nothing published until you approve it. Poliogo automates the reading and the drafting, not the judgement — it is not a law firm and this page is not legal advice.
Start free — no credit cardPoliogo is an automated code analysis and document display tool, not a law firm. Poliogo does not provide legal advice, representation, or guarantees of statutory compliance, ADA/WCAG certification, or legal immunity. Visual banners and generated documents are advisory tools and do not substitute for professional legal review.