Privacy policy generator: how to check it against your tracking
A generator knows only what you tell it, not your website. Here is how to find out which tracking services really load, then compare them with the text.

What does a privacy policy generator do?
A privacy policy generator is an online tool that asks questions about your website and assembles text blocks from the answers. It knows only what you tell it. It cannot see whether your site actually loads Google Analytics 4 (GA4), Google Ads conversion tracking or the Meta Pixel. A generator is therefore a good start for the privacy policy of your website, but never a substitute for comparing it with reality. This article is not legal advice.
The privacy policy must inform visitors which data you process and for what purpose, who receives it and how long you store it (Art. 13 GDPR). For tracking, that means every service running on your site belongs in it, with provider, purpose and recipient.
What do generators ask about?
- Data controller, contact details and hosting of the website
- Contact form, newsletter, comments and user accounts
- Analytics: a selection of well-known services, usually including GA4
- Advertising and remarketing, often only as a general option
- Embedded content such as maps, videos, fonts and social media plugins
- Shop, payment methods and shipping providers
Good generators offer ready-made blocks for well-known services. The problem begins where your site does more, or something different, than the selection list allows for.
→ Cookie banner with Consent Mode v2: compliant, with no monthly licence
Why is tracking so often missing from the privacy policy?
Tracking grows after the website launches. The answers in the generator date from the day it was created, and the site changes afterwards. A service can get onto the site without reaching the text in these ways:
- Marketing or an agency adds a Meta Pixel or Google Ads remarketing in Google Tag Manager.
- A plugin brings its own scripts, for example for a shop, form, chat or map.
- The text still describes Universal Analytics, which was switched off long ago, instead of GA4.
- A service that has been removed is still in the text.
- The text promises consent, but the site loads the service before that.
The pattern behind it is always the same: the generator text is a snapshot, while the website is a running system. If services are added in marketing without anyone touching the privacy policy, the gap creates itself. A fixed rule in the team helps: no new service goes live before it is on the list and in the text.
How do you find out which services really load?
Compare the generator text with four sources. No single one is enough on its own, because each shows a different part of the picture.
| Source | How to look | What you find there |
|---|---|---|
| Browser: Network | Open Chrome DevTools (Cmd+Option+J or Ctrl+Shift+J), go to the Network tab and reload the page | Requests to the domains of analytics and advertising services |
| Browser: Cookies | Application, Storage, Cookies, choose your domain | Cookies with name, domain and lifetime |
| Google Tag Manager | Open the list of tags in the container or start Preview | All tags the container fires, including those for Google Ads and Meta |
| CMS and plugins | Go through the plugin and theme list in the back end | Extensions with their own scripts for shop, form, chat and map |
| Advertising accounts | Look at Meta Events Manager and the conversion actions in Google Ads | Services that marketing has set up, even if nobody wrote it down |
→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant
How do you compare what you find with the generator text?
Create a list with the columns service, provider, purpose and listed in the policy. If a service is missing, switch on the matching option in the generator or have a specialist add to the text. For each entry, check that provider, purpose and recipient are right. Also check that the text matches reality: if it says a service runs only with consent, it must also load only after consent. You test that in an incognito window with the Network tab, before and after the click in the cookie banner.
This is what the list can look like. The rows are an invented example, and your list contains your services. Whether provider and purpose are described correctly in an individual case is for a specialist to check.
| Service | Provider | Purpose | Listed in the policy |
|---|---|---|---|
| Google Analytics 4 | Google Ireland Limited | Audience measurement | Yes |
| Google Ads conversion tracking | Google Ireland Limited | Measuring advertising success | No, add it |
| Meta Pixel | Meta Platforms Ireland Limited | Measuring advertising success | No, add it |
| Google Maps on the contact page | Google Ireland Limited | Map display | No, add it |
Three places fail particularly often in generator texts. First, the list of services: it is incomplete or out of date. Second, the information on cookies: names and lifetimes should match what you see in the Cookies section of DevTools. Third, the timing: the text says a service starts only after consent. The site proves the opposite.
Example: a small online shop
An online shop creates its privacy policy in a generator, entering contact form, newsletter, Google Analytics and PayPal. Half a year later, the shop starts advertising on Meta and Google Ads. For that, the agency sets up the Meta Pixel and Google Ads conversion tracking in Google Tag Manager. The privacy policy names neither. In the comparison, the container shows two tags that are missing from the list. The shop adds them and then checks that neither tag fires any more after Reject all.
Where does a generator end, and when do you need a specialist?
A generator cannot check whether the legal basis holds in your case, whether contracts with the providers exist or how transfers of data outside the EU should be assessed. A data protection officer or a lawyer does that. When choosing a generator, look at whether it lets you select tracking services individually and whether the provider keeps the texts up to date when the law changes. Free or paid, what matters is that the text fits your site and is maintained.
Trackum offers a cookie scan and privacy texts as an extra for €50. Beforehand, the free check shows which tags and cookies your site uses when it loads. It does not replace a legal assessment.
Frequently asked questions
Is a generator enough to create a privacy policy for my website?
As a start, yes, but not as the end point. The generator assembles text blocks from your answers and cannot see what your site loads. You must compare the text with the services you actually use and ask a specialist if in doubt.
Which tracking services must the privacy policy name?
Every service that processes data on your website, for example Google Analytics 4, Google Ads, the Meta Pixel or embedded maps and videos. As a rule, Google Tag Manager belongs on the list too, as do services that are loaded only through it.
How often do I have to update the privacy policy?
Whenever something changes in the services or the processing, for example with a new advertising or analytics service, a relaunch or new plugins. A fixed review date is also worthwhile, because integrations can change unnoticed.
Which is better: a free or a paid generator?
That depends less on the price than on whether the provider lets you select services, keeps the texts up to date when the law changes and fits your case. Check both by comparing against your site. No generator replaces a legal assessment.
Sources
- Data Protection Conference (DSK): guidance for providers of digital services datenschutzkonferenz-online.de
- Gesetze im Internet: Section 25 TDDDG gesetze-im-internet.de
- Tag Manager Help: Preview and debug containers support.google.com
- Chrome for Developers: Network panel in DevTools developer.chrome.com
Read more
FeaturesCookie banner with Consent Mode v2: compliant, with no monthly licence
Reject on the first layer, settings per purpose, Consent Mode v2 with every consent type and a record of each choice. No monthly licence.
FeaturesSetting up Google Consent Mode v2 correctly: no warning in Tag Assistant
The most common warning in Tag Assistant says a tag read consent before a default was set. How to avoid it, and what else matters.
FeaturesMarketing dashboard with GA4 and Google Ads: every number on one page
Visitors, leads, orders, ad spend and ROAS per campaign on one page, compared with the previous period. One link, nothing to set up.
FeaturesRevenue from your CRM, shop and ERP in one dashboard: HubSpot, Shopify, Odoo and more
Google Analytics only sees what happens on the website. Orders by phone or email are missing. With a data connection, the real revenue from your system appears in the dashboard.
FeaturesWebsite leads with their source in your CRM: HubSpot, Pipedrive, Brevo, Salesforce or webhook
Where did the lead come from? The CRM handover writes source, campaign and click ID into the CRM with every enquiry, without a form plugin.
FeaturesOffline conversions: report sales from your CRM to Google Ads and Meta
Google Ads and Meta learn from what you report to them. If they only get form fills, they optimise for form fills. With offline conversions, they optimise for sales.