Privacy policy

Last update: 21 nov. 2024, version 20.3.0

In short

We, or the Bonjourr team refers to Tahoe Beetschen & Victor Azevedo. We do not use collect, store, or share any data the user generates on Bonjourr. Data sent to our API is the minimum required for Bonjourr to work, is completely anonymous and cannot identify a user. The API does not save any logs or data.

External services

To enjoy every feature, Bonjourr has to communicate with external services. All data your page sends goes to our open source API before accessing the relevent services. This offers a layer of anonymity for the users, much like a VPN.

This API is deployed on Cloudflare Workers, which means we have access to Cloudflare's automatic account analytics and worker metrics. These analytics are general info about network traffic, error rates, and bandwidth usage. We can use these metrics to debug potential issues.

Nothing is stored on our end, however we cannot control how the service providers are using your data. You can refer to the privacy policy of each providers below:

Active on first start

api.bonjourr.fr

image.unsplash.com

Optional

api.bonjourr.fr

cdn.jsdelivr.net

api.github.com

Permissions

Extensions are more secured than webpages, that means Bonjourr needs to ask for permission to function properly. More about permissions on developer.chrome.com

Required

Optional

Settings storage

We do not have access to any of your settings. Settings are stored in the browser using the extension storage API. This storage system is not encrypted so users need to be responsible. Bonjourr will never ask for or store any personal or identifiable data.

By default, Bonjourr will synchronize its settings with your browser account if available. You can opt out by selecting "Disabled" on the "Synchronization" option, or by following these steps:

Background service

When using the extension, Bonjourr background service can open a tab on install, uninstall and when clicking on its toolbar icon. Nothing else runs in the background of your browser. Since the upgrade to manifest v3, the background worker even shuts down after 30s of inactivity all by itself.