Analytics

Privacy Policy for Sites & Apps Using Google Analytics

Google Analytics (GA4) collects usage and device data, often via cookies or identifiers. If you use it, your privacy policy needs to disclose analytics tracking, and in many regions you also need a cookie/consent notice.

Create My Privacy Policy

Last updated July 8, 2026

Why this affects your privacy policy

Analytics tools observe how people use your site or app — pages viewed, events, approximate location, device type — and share that data with Google. Under GDPR/ePrivacy this typically requires consent before non-essential analytics run, and under CCPA it may count as a sale/share depending on configuration. Your policy is where you explain all of this.

Data typically processed

Data type Details
Usage events Pageviews, screen views, clicks, and custom events.
Device & browser data Device type, OS, browser, and approximate location from IP.
Identifiers Cookies or app-instance IDs used to distinguish users/sessions.

What to disclose

  • That you use a third-party analytics service and what it measures.
  • That analytics may set cookies or use identifiers.
  • That data is shared with the analytics provider and may be transferred internationally.
  • How users can opt out (consent banner, browser settings, opt-out tools).
  • Whether you enable features like Google Signals or ads personalization.

Example wording

Analytics. We use a third-party analytics service to understand how visitors use our site or app so we can improve it. This service collects information such as the pages or screens you view, your device and browser type, and approximate location, and may use cookies or similar identifiers. Where required, we ask for your consent before loading non-essential analytics. You can opt out at any time through our cookie settings or your device controls.

Sample language only — adapt it to your actual data practices.

Best practices

  • → Load analytics only after consent in regions that require it (EU/UK).
  • → Turn on IP anonymization / data-retention limits and disclose your retention period.
  • → If you disable analytics entirely, you can simplify your policy — say what you actually do.
  • → Keep a cookie table if you set multiple cookies, and link it from your policy.

Generate a policy that already covers Google Analytics and host it at a permanent URL.

Host Your Policy

Frequently asked questions

Do I need a cookie banner if I use Google Analytics?
In the EU/UK and similar regions, non-essential analytics generally require consent before they run, which usually means a consent banner. Your privacy policy should describe this alongside the banner.

Is Google Analytics a "sale" under CCPA?
Depending on settings (e.g., ads features/Signals), analytics data sharing can be treated as a sale or share, which triggers opt-out rights. Configure conservatively and disclose accordingly.

Can I avoid all this by not using analytics?
Yes — if you collect no analytics, your policy can say so plainly, which is simpler and a nice trust signal. Just make sure no SDK is quietly collecting data anyway.

Related guides

Privacy Policy for Apps Using Firebase Privacy Policy for Meta, Facebook & Instagram Apps Privacy Policy for Chrome Extensions

This guide is for general informational purposes only and is not legal advice. Your privacy policy should reflect your actual data practices and applicable legal requirements, which vary by jurisdiction and platform.

Create and host your privacy policy

Fill out a short form, get a permanent HTTPS URL for your app submission.

Create My Privacy Policy