[GH-ISSUE #121] One-time opt-out of Google Analytics #64

New issue

Closed

opened 2026-03-03 01:24:26 +03:00 by kerem · 5 comments

kerem commented

2026-03-03 01:24:26 +03:00

Owner

Originally created by @lablans on GitHub (Aug 8, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/121

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 8, 2018). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/121 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).

kerem

2026-03-03 01:24:26 +03:00

closed this issue
added the
enhancement

future Vault
labels

kerem commented

2026-03-03 01:24:27 +03:00

Author

Owner

@dani-garcia commented on GitHub (Aug 8, 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 8, 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.

kerem commented

2026-03-03 01:24:27 +03:00

Author

Owner

@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?

kerem commented

2026-03-03 01:24:27 +03:00

Author

Owner

@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.

kerem commented

2026-03-03 01:24:27 +03:00

Author

Owner

@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.

kerem commented

2026-03-03 01:24:27 +03:00

Author

Owner

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