Security claims are easy to make and hard to check. These are the specific measures in place, described plainly enough that you can hold us to them.
In transit and at rest
The site is served over HTTPS, so traffic between your browser and us is encrypted. Sensitive stored credentials are encrypted at rest with AES-256-GCM, meaning that a copy of the database alone does not yield readable secrets.
Passwords
Your password is hashed with bcrypt and never stored in a readable form. Nobody here can look it up or tell it to you — which is why a reset is the only route back into an account, including for our own staff.
Two-factor authentication
You can require a one-time code sent to your email at sign-in. It means a stolen password alone is not enough to reach your account, and it is the single most effective thing you can switch on.
Your documents
Identity documents are stored outside the publicly reachable part of the site and served only to you and to reviewing staff. Uploads are validated by actual file content rather than by the name they arrive with, so a file pretending to be an image cannot be stored as something executable.
Access and record-keeping
Administrative actions on an account are recorded, and sign-ins are logged with time and address so unfamiliar activity can be identified.
Common questions
Can staff see my password?
No. Passwords are hashed, so there is nothing readable to see. A reset is the only way back in.
How do I switch on two-factor authentication?
Ask us to enable it for your account, or check your profile settings where available.
