Skip to content

Google Privacy Sandbox Topics API detected

The Topics API is Google's replacement for third-party cookies in the Chrome browser, designed to enable interest-based advertising without tracking visitors across individual sites. This check simply detects whether the site is using it. On this site, the Topics API was detected, which is informational rather than a defect, since it may be an intentional adoption or just default Chrome behaviour. This finding is informational rather than a problem in itself, so there's no direct risk being flagged. What matters is confirming whether the business deliberately adopted it. If so, it should be documented like any other tracking technology, because a 2024 ruling from the Court of Justice of the European Union (CJEU) treats Topics API data as personal data still requiring consent from EU visitors. You or your privacy lawyer should first confirm whether Topics API use was a deliberate choice or just default Chrome behaviour the site inherited. If it was deliberately adopted, document it in the privacy policy alongside other tracking technologies. If it's simply the browser's default behaviour and nothing was configured to enable it, no action is needed. This is roughly 30 minutes to confirm and, if needed, document.

Why this matters

This finding is informational rather than a problem in itself, so there's no direct risk being flagged. What matters is confirming whether the business deliberately adopted it. If so, it should be documented like any other tracking technology, because a 2024 ruling from the Court of Justice of the European Union (CJEU) treats Topics API data as personal data still requiring consent from EU visitors.

How to fix it

You or your privacy lawyer should first confirm whether Topics API use was a deliberate choice or just default Chrome behaviour the site inherited. If it was deliberately adopted, document it in the privacy policy alongside other tracking technologies. If it's simply the browser's default behaviour and nothing was configured to enable it, no action is needed. This is roughly 30 minutes to confirm and, if needed, document.