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

[GH-ISSUE #5305] Feature request: phoneNumber masked #27532

New Issue
Open
opened 2026-04-17 18:35:34 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-17 18:35:34 -05:00
Owner
Copy Link

Originally created by @reslear on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/5305

Originally assigned to: @ping-maxwell on GitHub.

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

API currently returns full phone numbers, risking data leaks and privacy issues.

Describe the solution you'd like

Return masked numbers by default (e.g., +1 XXX XXX 12 34).
Full numbers only accessible via secure, authorized endpoints.

Describe alternatives you've considered

Frontend masking — insecure.

Encrypted full numbers — still exposed in transit.

Additional context

Improves privacy, aligns with GDPR and industry best practices.

Originally created by @reslear on GitHub (Oct 14, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/5305 Originally assigned to: @ping-maxwell on GitHub. ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. API currently returns full phone numbers, risking data leaks and privacy issues. ### Describe the solution you'd like Return masked numbers by default (e.g., +1 XXX XXX 12 34). Full numbers only accessible via secure, authorized endpoints. ### Describe alternatives you've considered Frontend masking — insecure. Encrypted full numbers — still exposed in transit. ### Additional context Improves privacy, aligns with GDPR and industry best practices.
GiteaMirror added the credentials label 2026-04-17 18:35:34 -05:00
GiteaMirror commented 2026-04-17 18:35:35 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Oct 14, 2025):

Not a bad idea.
Until there is support, for now we recommend using hooks to mask the phone number

<!-- gh-comment-id:3402660414 --> @ping-maxwell commented on GitHub (Oct 14, 2025): Not a bad idea. Until there is support, for now we recommend using hooks to mask the phone number
GiteaMirror commented 2026-04-17 18:35:36 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jan 13, 2026):

Hi, @reslear. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You suggested that the API should return masked phone numbers by default to enhance privacy and comply with GDPR.
  • The maintainer, ping-maxwell, agreed with the idea but recommended using hooks to mask phone numbers as an interim solution.
  • You responded positively to this interim approach.
  • Native support for masked phone numbers by default has not yet been implemented.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here.
  • If I don’t hear from you, this issue will be automatically closed in 7 days.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3745193121 --> @dosubot[bot] commented on GitHub (Jan 13, 2026): Hi, @reslear. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You suggested that the API should return masked phone numbers by default to enhance privacy and comply with GDPR. - The maintainer, ping-maxwell, agreed with the idea but recommended using hooks to mask phone numbers as an interim solution. - You responded positively to this interim approach. - Native support for masked phone numbers by default has not yet been implemented. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here. - If I don’t hear from you, this issue will be automatically closed in 7 days. Thanks for your understanding and contribution!
GiteaMirror commented 2026-04-17 18:35:37 -05:00
Author
Owner
Copy Link

@reslear commented on GitHub (Jan 13, 2026):

@dosubot not stale

<!-- gh-comment-id:3745282167 --> @reslear commented on GitHub (Jan 13, 2026): @dosubot not stale
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 credentials
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#27532
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?