[BWA-230] Missing Password Check For Data Breach in Send

[shamim-emon]

Steps To Reproduce

1. Open Bitwarden Android Application
2. Click on Send Tab
3. Click on "New Send" button
4. Select either Text/File type.
5. On New text Send / New file Send screen Tap on "Ädditional options".
6. On expanded view scroll to new password.
7. Observe unlike "New login" there is no option for ""Check password for data breaches".

Expected Result

Like new login, user should be able to check for password data breach for send items.

Actual Result

User has no option to check for password data breach for send items.

Screenshots or Videos

No response

Additional Context

No response

Build Version

2026.2.0 (1)

What server are you connecting to?

US

Self-host Server Version

No response

Environment Details

No response

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for your report! We've added this to our internal board for review.
ID: BWA-230

[pamperer562580892423]

Just for the record, you obviously meant the "password manager" app and not the "authenticator app".

And I guess this can be considered a "follow up" to your own fix. (thank you, BTW! 🙂)

[shamim-emon]

Just for the record, you obviously meant the "password manager" app and not the "authenticator app".

And I guess this can be considered a "follow up" to your own fix. (thank you, BTW! 🙂)

@pamperer562580892423 yes I meant "password manager". Thank you and welcome 🙂

[cbbit]

Hi there,

We use GitHub issues as a place to track bugs and other development related issues. The Bitwarden Community Forums has a Feature Requests section for submitting, voting for, and discussing requests: https://community.bitwarden.com/c/feature-requests/

Please sign up on our forums and search to see if this request already exists (https://community.bitwarden.com/signup). If so, you can vote for it and contribute to any discussions about it. If not, you can re-create the request there so that it can be properly tracked.

This issue will now be closed. Note that the “Closed as not planned” status is for internal tracking purposes only, please do not hesitate to send us your suggestions to the forum.

Thanks!