When you create your account, SideClick shows a recovery code once: letters and digits in groups of four, with the ones that look alike left out. You type it back before you can continue, so it is certain you have it. Keep it somewhere safe and offline — written down, or in a password manager.
Your password is turned into keys on your device and never sent, so SideClick holds no way to reset it. The recovery code opens the same personal key by a second route. Lose both, and nobody — including SideClick — can open your records. The screens say so, because it is true.
Forgot your password? is on every sign-in screen. It takes your email, the recovery code and a new password. The code proves it is you and opens your personal key, which is wrapped again under the new password; your keys themselves do not change, so nothing has to be re-sent. You get a new recovery code, shown once and typed back, and the one you used stops working.
Then every device of yours is signed out and you are emailed. A phone, tablet or browser signs in again with the new password straight away and keeps what it had not yet sent. A computer whose records open only with the forgotten password is different: they are erased there and fetched again from the sync server, and anything that computer had not yet sent is lost — the screen says so first.
The recovery code also stands in when you sign in on a new device with no other device at hand to approve it.
Related
- Your accountOne account per person, with your email and password; every device you sign in on belongs to you, not to a practice.
- Remove, Mark as lost, Sign out everywhereThe three things you can do to a device of yours on Settings → Your devices, what each erases, and when.
- A device that cannot sign inWhat each sign-in refusal means — a wrong password, approval waiting, no other device, the sync server out of reach, a device refused, an update required — and what to do.
- What the sync server can seeEvery entry reaches the sync server sealed, under a key only the people who may open it hold; the server keeps the sealed copy and cannot read it.
Still stuck? support@sideclick.io reaches the people who build the product.