-
Notifications
You must be signed in to change notification settings - Fork 905
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove telemetry token from the code #1329
Comments
@EBazarov Wow, thanks for catching this! Considerable privacy leak, I'll prioritise this! |
Looking at the related code, it seems no private data is logged. 😅 chainlit/backend/chainlit/telemetry.py Line 87 in 74636a9
The telemetry is gathering just performance traces and takes care to obfuscate client's host names (single iteration of SHA256, perhaps we should use something like PBKDF2, scrypt, Argon2 or Bcrypt). It is currently enabled by default in the config, but can easily be disabled: https://github.com/Chainlit/chainlit/blob/main/backend/chainlit/config.py#L56 As the underlying framework is OpenTelemetry (uptrace is just a wrapper/implementation of it), perhaps it makes sense to switch to the default OLTP exporter, setting default environment variables. This would enable implementers to do their own telemetry, default to setting anonymous stats to LiteralAI while making it similarly easy to disable it. Perhaps another feature would be to add an interactive prompt to |
chainlit/backend/chainlit/telemetry.py
Line 65 in 74636a9
The text was updated successfully, but these errors were encountered: