One-time opt-out of Google Analytics #65

New Issue

OVERLORD · 2026-02-04T16:37:12+03:00

OVERLORD commented

2026-02-04 16:37:12 +03:00

Originally created by @lablans on GitHub (Aug 9, 2018).

By default, the Bitwarden apps come with Google Analytics activated. To opt-out, you need to visit each app/plugin instance and tick the box. This can really add up: With my three machines, two user accounts on each and two browsers, I need to opt-out twelve times. Surely I've forgotten it on one or two instances. This is problematic from a data protection standpoint, especially in Europe.

Some ideas for solutions:

Allow to change the Google Analytics setting server-wide, allowing the administrator to set it to opt-in.
Acknowledge the user's decision and store it as a preference server-side.
Have the Docker container's entrypoint remove the Google Analytics code from the downloaded Vault's JavaScript code (configurable via environment variable).

Originally created by @lablans on GitHub (Aug 9, 2018). By default, the Bitwarden apps come with Google Analytics activated. To opt-out, you need to visit each app/plugin instance and tick the box. This can really add up: With my three machines, two user accounts on each and two browsers, I need to opt-out twelve times. Surely I've forgotten it on one or two instances. This is problematic from a data protection standpoint, especially in Europe. Some ideas for solutions: * Allow to change the Google Analytics setting server-wide, allowing the administrator to set it to opt-in. * Acknowledge the user's decision and store it as a preference server-side. * Have the Docker container's entrypoint remove the Google Analytics code from the downloaded Vault's JavaScript code (configurable via environment variable).

OVERLORD added the enhancement future Vault labels 2026-02-04 16:37:12 +03:00

OVERLORD closed this issue

2026-02-04 16:37:19 +03:00

OVERLORD commented

2026-02-04 16:37:34 +03:00

@dani-garcia commented on GitHub (Aug 9, 2018):

I don’t think there is a way to control other clients from the server, but we could look into modifying the web vault in the build file.

@dani-garcia commented on GitHub (Aug 9, 2018): I don’t think there is a way to control other clients from the server, but we could look into modifying the web vault in the build file.

OVERLORD commented

2026-02-04 16:37:44 +03:00

@ptman commented on GitHub (Aug 9, 2018):

Where is this opt-out located?

@ptman commented on GitHub (Aug 9, 2018): Where is this opt-out located?

OVERLORD commented

2026-02-04 16:37:56 +03:00

@fbartels commented on GitHub (Aug 9, 2018):

I have noticed the tracking options in the Android apps, but I don't see anything in the web vault (also ublock does not report anything). @martinlablans are you sure there is google analytics in the web vault?

ps: using the tagged 0.12.0 release.

edit: ah never mind, this seems only to be present in the new vault currently part of the beta docker image.

@fbartels commented on GitHub (Aug 9, 2018): I have noticed the tracking options in the Android apps, but I don't see anything in the web vault (also ublock does not report anything). @martinlablans are you sure there is google analytics in the web vault? ps: using the tagged 0.12.0 release. edit: ah never mind, this seems only to be present in the new vault currently part of the beta docker image.

OVERLORD commented

2026-02-04 16:38:08 +03:00

@mprasil commented on GitHub (Aug 14, 2018):

Submitted a PR, that should remove analytics in self-hosted scenario.

@mprasil commented on GitHub (Aug 14, 2018): Submitted a PR, that should remove analytics in self-hosted scenario.

OVERLORD commented

2026-02-04 16:38:28 +03:00

@mprasil commented on GitHub (Aug 20, 2018):

This was resolved in #136

@mprasil commented on GitHub (Aug 20, 2018): This was resolved in #136

OVERLORD referenced this issue

2026-02-05 04:48:20 +03:00