Screen sharing is the moment two people look at the same screen. A password typed in that moment is a password the other person can read.
The page does not know a second pair of eyes is there. It keeps painting the login field and the card number exactly as it would for one person.
The Other Person Sees What You See
On October 14, a Google security note described the ordinary case: sharing a screen to help family, or to work with a coworker, and then needing to type a password or a card’s security number. Android already hides sensitive information inside its own apps. The same protection now extends to Chrome and to pages opened inside an app. During a live screen share, those surfaces blank the login field and the payment screen.
The note’s footnote says the change is rolling out this month on phones running Android 15 or newer. That is not every phone. It is not an iPhone. A laptop share is a different path, and this note does not cover it.
The blank is what the other person should see. The page can stay up. The password and the card number should not.

A Call With the Bookkeeper
Picture a video call with a bookkeeper in Midtown. You share the browser to show last month’s checkout. The card field is still filled in from the test order you placed that morning. They are not trying to read it. The screen is showing it anyway.
The letters are not hard to see. A shared payment screen is easy to read, and the other person gets the number whether they asked for it or not.
Your Site Still Paints the Field
The phone may cover the field during a share. Your page does not. If the share is from a computer, or from a phone that does not have this update, the field stays as your site drew it.
A password box that shows dots is already hiding the characters. A card field that leaves the full number on screen is not. A stored card number does not belong in view on a call.
The check is visual, not a setting buried in a phone. Open the login and the checkout the way a customer would, then imagine the second person on the call. If you can read the password or the card, so can they.
Look at the Screen Before You Share It
Use your own login and your own payment page. Start a share, or sit a colleague next to the monitor. Watch the password field and the card field, not the headline.
What stays readable is part of the product. If customers pay or sign in on that page, the screen they might share is part of the work. We design that kind of flow on our UX page.
Bring the page you would share on a call with a bookkeeper. Fifteen minutes on the calendar is enough to see whether the password stays up.