I propose a password rotation feature for those of us using 24+ and 64+ chars
ASK: Partition long password and allow a specific segment to be updated

Basic draft to contribute to CONOPS

Preconditions: User has active authenticated session; MFA available.
Users existing password must be 24 chars or more

Step 1: User navigates to Proton login; TLS handshake negotiates hybrid PQ + classical key exchange.

Step 2: User selects Password Change Special; system prompts for current password and second factor.

Step 3: On successful re-auth, create a temporary sandbox session with no access to emails or other PII. Log entry.

Step 4: Display password partition UI with clear labels and entropy indicator. Allow user to change one or more blocks of their password, but not the whole password.

Step 5: Client sends proposed new blocks over PQ-TLS; server reconstructs candidate password, validates strength, and atomically replaces stored hash using Argon2id (Or read OWASP, NIST guidance).

Step 6: Invalidate other sessions immediately and require re‑login; send notification to user; log change.

Failure modes: On login failure, show generic warning, rate limit, and exit. On partial update failure, rollback and notify user.

Postcondition: Password updated, audit logged, user notified, and sandbox terminated.

OPTIONAL.
Lock down all access to email for 12 hours starting now

Notes: I am aware these exist:- RSA Tokens, MFA, Keywords, SSO, Federated authentication. I've not included threat modelling, precise server semantics for partitioned passwords. Over to you Proton Techs for consideration. "Is the juice worth the squeeze :-)" I'd love to learn that phrase in Swiss French too

Kind regards