> For the complete documentation index, see [llms.txt](https://docs.sec1.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sec1.io/user-docs/4-sast/3-javascript/leakage-of-sensitive-data-to-google-analytics.md).

# Leakage of sensitive data to Google Analytics

## Overview

* **Rule ID**: `javascript_third_parties_google_analytics`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-201

## Description

Exposing sensitive data to third-party analytics tools such as Google Analytics is a common cause of data leaks and can result in data breaches.

## Remediation Guidelines

* **Ensure** all sensitive data is stripped out when sending information to analytics libraries like Google Analytics.
* **Use** unique database identifiers if user identification is necessary.

  ```javascript
  gtag("event", "screen_view", {
    user: {
      subscribed: true,
    },
  });

  ```

## References

* [**Google Analytics docs**](https://developers.google.com/analytics/devguides/reporting/)
* [**OWASP logging cheat sheet**](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html)
* [**CWE-201: Insertion of Sensitive Information Into Sent Data**](https://cwe.mitre.org/data/definitions/201.html)
* [**OWASP Top 10: A01:2021 - Broken Access Control**](https://owasp.org/Top10/A01_2021-Broken_Access_Control/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)