What your sign-in holds

In plain words Technical detail

Each kind of information, why we keep it, who can see it and for how long
What	Why	Who can see it	Kept for	Retention schedule
Your recovery codes	Getting back in when the device a passkey is on is lost. Only a scrambled copy of each code is kept.	You	Until used, replaced by a new set, or the account is erased.	Not listed yet
Browsers you have signed in from	Under the key auth.devices: scrambled names of the last few browsers the account was used from, so a sign-in from a new one can be noticed. Under the key auth.passkey_later: the day until which the suggestion to add a passkey is not shown again, set when you choose Maybe later or carry on without a passkey while joining.	You	The last eight browsers; the day is 30 days ahead and is not read after it passes. Removed when the account is erased.	Not listed yet
Your two-step sign-in	Two-step sign-in, when you turn it on: which kind, and for an authenticator app its secret, kept sealed so a copy of the database cannot read it. Counts wrong codes to pause it after five.	You	Until you turn it off or the account is erased.	Not listed yet
Your password	A password, if you choose to have one: kept as a salted hash that cannot be turned back into the password and cannot be attacked without the site's own secret. A one-time code by email and a passkey always work as well.	You	Until you remove it or the account is erased.	Not listed yet
Wrong passwords at your sign-in	How many wrong passwords were typed for your account and how long password sign-in is paused, so that guessing is slow. Counts and times only; nothing that was typed.	You	Cleared by the next right password or a new one; removed when the account is erased.	Not listed yet
Sign-up refusals and people waitingAlso about people who are not members	A scrambled copy of an address that was turned away at sign-up, or that asked to be counted as waiting at a college that is not open yet.	Staff	30 days for a refusal; up to a year for someone waiting.	Not listed yet