Skip to content
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

Open
EBazarov opened this issue Sep 10, 2024 · 2 comments
Open

remove telemetry token from the code #1329

EBazarov opened this issue Sep 10, 2024 · 2 comments
Assignees
Labels
evaluate-with-priority What's needed to address this one? security

Comments

@EBazarov
Copy link

@dokterbob
Copy link
Collaborator

@EBazarov Wow, thanks for catching this! Considerable privacy leak, I'll prioritise this!

@dokterbob dokterbob self-assigned this Sep 23, 2024
@dokterbob dokterbob added the evaluate-with-priority What's needed to address this one? label Sep 23, 2024
@dokterbob
Copy link
Collaborator

dokterbob commented Sep 25, 2024

Looking at the related code, it seems no private data is logged. 😅

def trace_event(event_name):

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 init where the user is interactively asked about anonymous data collection, as is common in other FOSS packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
evaluate-with-priority What's needed to address this one? security
Projects
None yet
Development

No branches or pull requests

2 participants