github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 23:52:05 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

Telemetry opt OUT by default. #1680

New Issue
Closed
opened 2026-03-13 08:55:28 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-03-13 08:55:28 -05:00
Owner
Copy Link

Originally created by @rebasecase on GitHub (Aug 11, 2025).

Should have tememetry opt out by default. Not opt in.

Collects environment, system, and config info (with sensitive data redacted) on startup.

Is not a good enough assurance.

https://github.com/better-auth/better-auth/pull/3822

Originally created by @rebasecase on GitHub (Aug 11, 2025). Should have tememetry opt out by default. Not opt in. > Collects environment, system, and config info (with sensitive data redacted) on startup. Is not a good enough assurance. https://github.com/better-auth/better-auth/pull/3822
GiteaMirror commented 2026-03-13 08:55:29 -05:00
Author
Owner
Copy Link

@rebasecase commented on GitHub (Aug 11, 2025):

You don't even give a heads up on package install/server startup. This is poor show guys.

For clarity, I enable telemetry for those who make it opt in, unlike npm/package managers for example, because I am in control and I choose to 'support' their development activities with these datapoints... I actively disable any that is opt in by default.

@rebasecase commented on GitHub (Aug 11, 2025): You don't even give a heads up on package install/server startup. This is poor show guys. For clarity, I enable telemetry for those who make it opt in, unlike npm/package managers for example, because I am in control and I choose to 'support' their development activities with these datapoints... I actively disable any that is opt in by default.
GiteaMirror commented 2026-03-13 08:55:29 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Aug 11, 2025):

Fair callout. We'll add heads up on package startup asap

That said. We’ve tried to make sure the data collection is completely anonymous and also easy to understand if you’re curious about what we collect. We’ve also added a section in our docs about what we're collecting with telemetry. Plus, you can inspect exactly what’s being sent by setting BETTER_AUTH_TELEMETRY_DEBUG=1 in your .env file, this will log all outgoing data to our server.

@Bekacru commented on GitHub (Aug 11, 2025): Fair callout. We'll add heads up on package startup asap That said. We’ve tried to make sure the data collection is completely anonymous and also easy to understand if you’re curious about what we collect. We’ve also added a section in our docs about what we're collecting with telemetry. Plus, you can inspect exactly what’s being sent by setting `BETTER_AUTH_TELEMETRY_DEBUG=1` in your `.env` file, this will log all outgoing data to our server.
GiteaMirror commented 2026-03-13 08:55:30 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Aug 11, 2025):

I think people generally don’t opt in to telemetry unless they’re prompted. Since this is a library, it can be harder to do prompt users to do so. That said, we’ll try to make the collection as transparent as possible. At the end of the day, this is about understanding the community better. We’ve avoided adding telemetry for almost a year to keep things as private as possible, but understanding usage patterns will obviously help us improve the library

@Bekacru commented on GitHub (Aug 11, 2025): I think people generally don’t opt in to telemetry unless they’re prompted. Since this is a library, it can be harder to do prompt users to do so. That said, we’ll try to make the collection as transparent as possible. At the end of the day, this is about understanding the community better. We’ve avoided adding telemetry for almost a year to keep things as private as possible, but understanding usage patterns will obviously help us improve the library
GiteaMirror commented 2026-03-13 08:55:30 -05:00
Author
Owner
Copy Link

@rebasecase commented on GitHub (Aug 11, 2025):

Thanks. I really do like this library, it does a LOT of boring boilerplate auth stuff I would otherwise have to do myself - and it does it well (and getting better).

Fair point, I think at least giving a notice on startup would be good (in dev mode as well, so it's not a shock when someone comes to testing it in a non test environment or whatever)

@rebasecase commented on GitHub (Aug 11, 2025): Thanks. I really do like this library, it does a LOT of boring boilerplate auth stuff I would otherwise have to do myself - and it does it well (and getting better). Fair point, I think at least giving a notice on startup would be good (in dev mode as well, so it's not a shock when someone comes to testing it in a non test environment or whatever)
GiteaMirror commented 2026-03-13 08:55:30 -05:00
Author
Owner
Copy Link

@ThallesP commented on GitHub (Aug 19, 2025):

I think people generally don’t opt in to telemetry unless they’re prompted. Since this is a library, it can be harder to do prompt users to do so. That said, we’ll try to make the collection as transparent as possible. At the end of the day, this is about understanding the community better. We’ve avoided adding telemetry for almost a year to keep things as private as possible, but understanding usage patterns will obviously help us improve the library

@Bekacru Maybe it's possible to prompt users on a postinstall script using something like prompts?

@ThallesP commented on GitHub (Aug 19, 2025): > I think people generally don’t opt in to telemetry unless they’re prompted. Since this is a library, it can be harder to do prompt users to do so. That said, we’ll try to make the collection as transparent as possible. At the end of the day, this is about understanding the community better. We’ve avoided adding telemetry for almost a year to keep things as private as possible, but understanding usage patterns will obviously help us improve the library @Bekacru Maybe it's possible to prompt users on a `postinstall` script using something like `prompts`?
GiteaMirror commented 2026-03-13 08:55:31 -05:00
Author
Owner
Copy Link

@harrisonford commented on GitHub (Oct 4, 2025):

Damn this was such a bad move, and broke my pipeline because it's non-NodeJS it's just adding salt to the wound. How much data do you really need if you need to sneakily take advantage of people opting-in without knowing that's a great way to break trust.

Maybe for next release call yourself just Auth instead of Better-Auth.

@harrisonford commented on GitHub (Oct 4, 2025): Damn this was such a bad move, and broke my pipeline because it's non-NodeJS it's just adding salt to the wound. How much data do you really need if you need to sneakily take advantage of people opting-in without knowing that's a great way to break trust. Maybe for next release call yourself just Auth instead of Better-Auth.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#1680
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?