Cerbos developers rely on anonymous usage data to help prioritise new features and improve the product. The information collected is completely anonymous, never shared with external entities, and you can opt out at any time.
Cerbos build information like version, commit and build date
Operating system type and architecture
Enabled Cerbos features (storage backend type and schema enforcement level are some examples of this information)
Aggregated statistics about the policies like the total number of policies and average number of rules in a policy
Aggregated statistics about Cerbos API calls and the gRPC user agents.
We use Rudderstack to collect the data. Only a small number of Zenauth (the company leading the development of Cerbos) employees have access to the data.
There are multiple ways in which you can disable telemetry collection.
telemetry.disabled: true in the Cerbos configuration file.
telemetry: disabled: true
CERBOS_NO_TELEMETRY=true in your environment. We also honour the
DO_NOT_TRACK environment variable if it exists.
CERBOS_NO_TELEMETRY=1 ./cerbos server --config=/path/to/config.yaml
docker run -i -t -p 3592:3592 \ -e CERBOS_NO_TELEMETRY=true \ ghcr.io/cerbos/cerbos:0.19.1
Start Cerbos with
--set=telemetry.disabled=true command line flag.
./cerbos server --config=/path/to/config.yaml --set=telemetry.disabled=true
docker run -i -t -p 3592:3592 \ ghcr.io/cerbos/cerbos:0.19.1 \ server --set=telemetry.disabled=true