About this screen · A17
- Requirements
R-NF-21R-NA-20R-EL-4R-NF-1- Mocked in this prototype
With the demo API this screen works (API DECISIONS §19, §22). An account made with a platform code has no e-mail or phone: on a phone without a session the recovery key brings the account back (a secret derived from the key, the API knows only a hash) and opens the messages at once; or the old phone gives a link code (A8); or, both lost, a new code from the platform (the old account waits 7 days). An account without a code logs in again with e-mail or phone. Then: pseudonym, session and rooms back; the recovery key is a Matrix key over a real encrypted backup; the old phone can say ‘Yes’ and then sends the backup key, encrypted, to the new device. Still mock: moving income, requests and work preferences with a file (concept). Without the demo API no key is made and nothing is sent. The 12 words come from a fixed list of 24, random each time; the check asks for 3 places. The QR code is a drawing and the number is random. ‘Phone lost’ shows three made-up devices; ‘Remove everywhere’ (two taps) only changes this list. The real per-account removal is live in A8 with the demo API.
- In the real design
A recovery key only the worker holds restores the keys of the encrypted rooms (D-033, open point 39); no recovery through a platform code (R-NA-20). Moving over uses a QR code and a comparison number between two phones. ‘Remove everywhere’ ends every session of that device; the phone repeats it per account, because only the phone knows which accounts belong together (R-NF-21, D-030).