Google Analytics is a web and app analytics platform, reviewed for data collection, ads personalization, sharing, retention, deletion, and controls.
70
Mixed
70
Mixed
Google Analytics is built to measure user behavior, even though admins get strong export, retention, and consent controls.
Google Analytics gives administrators mature controls around exports, retention windows, configuration, and consent-aware deployment.
Its weakest area is still tracking by design: the product exists to collect and analyze user-behavior signals across sites and apps.
70
Mixed
Linked Google products can use exported Analytics data under their own terms rather than the narrower Analytics processing terms.
Customers can still use Analytics data for personalization or advertising purposes depending on configuration.
70
Mixed
45
Weak
80
Good
85
Good
Latest Finding
Open: support.google.comAnswer 7667196
Open: support.google.comAnswer 7586885
Open: support.google.comAnswer 6366371
Open: support.google.com1. Tracking
Linked Google products can use exported Analytics data under their own terms rather than the narrower Analytics processing terms.
2. Tracking
Customers can still use Analytics data for personalization or advertising purposes depending on configuration.
3. Tracking
Google Analytics generally acts as a processor or service provider for customers under its data processing terms.
4. GA4 Does
GA4 does not log or store IP addresses, and customers are prohibited from sending PII.
5. Controls
Customers control whether to enable features such as Google signals that widen how data is used.
Founded
Unknown
Founder
Unknown
Parent Company
Google Analytics
Lifecycle
Active
Category
Analytics & Tracking
CEO
Unknown
Security Team
In house
Date Added
05-18-2026
Once you delete a chat, you cannot recover it. Deleting a chat removes it both from your visible chat history and the system after the retention window.
Google Analytics generally acts as a processor or service provider for customers under its data processing terms.
GA4 does not log or store IP addresses, and customers are prohibited from sending PII.
Customers control whether to enable features such as Google signals that widen how data is used.
70
Mixed
Product linking can send Analytics data into other Google products where different terms apply.
Site and app owners still decide what they instrument, share, and disclose to their users.
Google says it does not share Analytics data without customer authorization except where contractually permitted or legally required.
The processor/service-provider model is stronger than ordinary ad-tech controller language.
Customers choose whether to link Analytics data into other Google products or export it elsewhere.
45
Weak
Google Analytics still relies on first-party cookies, app instance IDs, browser and device data, and on-site or in-app activity measurement.
Privacy outcomes depend heavily on the site or app owner's consent flows, tagging choices, and ads settings.
GA4 does not log or store IP addresses.
Customers can disable Google signals and other ads-personalization features when they are not needed.
The platform is designed around first-party measurement rather than a public social-graph advertising feed.
80
Good
Customers can set data-retention periods instead of accepting a fixed indefinite default.
Google provides user-deletion tools for removing individual user-level data.
Analytics is explicit that retention and deletion are customer-governed administrative settings.
Aggregate reporting data can remain even after deleting some individual user-level data.
Customers must actively configure retention and deletion; weak defaults or neglected settings can leave data longer than intended.
85
Good
Customers can configure consent mode, Google signals, and ads personalization settings.
Customers can set retention windows and invoke deletion tooling for user-level data.
Google prohibits sending PII and documents ways to avoid collecting more data than needed.
Export, admin, and property-level controls let organizations narrow access and move data when needed.
End-user privacy still depends primarily on how the site or app owner configures the implementation.
The most privacy-sensitive choices are admin-controlled rather than self-serve for the tracked end user.
