Why does Seayora ask for a code before I change my own details?

Because being signed in proves a browser or a phone is yours, not that you are the one holding it right now. A laptop left open at a desk, a session someone else has taken, or a phone handed to a colleague all look identical to us. Asking for a code that reaches your inbox or your handset is what makes moving your address or your phone number something only you can do. Reading your details never asks — only changing them does.

From the guide Account Security: SSO, 2FA & Passkeys.

Seeing your own details, and changing them

Everything Seayora holds about you is visible in Settings whenever you are signed in — your name, your mailing address, every email address and phone number on the account, and the state of every login protection you have turned on. Looking at your own record never asks for a code. That is deliberate: your settings screen is the place an unauthorized change would be visible, and it is no use to you if you cannot open it.

Changing any of it is different. Before Seayora will save a change to your name, your address, your email addresses or phone numbers, your password, your authenticator app, your passkeys or your trusted devices, it asks you to confirm it is you with a 6-digit code sent to your email or texted to your phone. Once you pass it, changes stay unlocked for 10 minutes and the screen counts down, so a run of edits only asks once.

The check is enforced by our servers, not just by the screen: a change submitted without a recent, confirmed code is refused, whichever app or device it comes from. This is what stops a browser left signed in on a shared computer — or a session taken by someone else — from moving the address your lease is served to or the phone number your sign-in codes are sent to.

Read the whole guide: Account Security: SSO, 2FA & Passkeys

More questions about Account Security: SSO, 2FA & Passkeys