Here's a look, with technical jargon kept to a minimum, at the thinking behind how Qypher stays strong against outside attacks.
Just being told "it's safe" may not be enough to put your mind at ease. Here, we'll explain, as plainly as possible, the way of thinking behind how Qypher stays robust.
No "secret" worth stealing exists in the first place
As we mentioned in article one, logging into Qypher involves no password that a person memorizes. Because there's no "secret" for an attacker to target in the first place, common attack methods — stealing a password, guessing one, exploiting a reused one — simply don't apply.
Even in a worst case, nothing is stored in a usable form
Qypher's database never stores authentication-related information in a form that can be reversed back to the original. What's kept is only data that has gone through a one-way transformation — one that can't be computed back to its original value. Personal information such as names and addresses is likewise stored in encrypted form. So even if part of the data were to end up in the wrong hands, it couldn't be extracted in a form that's directly usable.
Generation left to machines — not something you can guess
The information used for login isn't generated from predictable factors like the date and time — it's produced by a cryptographically secure random number generator. Because it isn't a string a human thought up, there's no pattern to guess your way to it.
Qypher's security doesn't rest on "keeping the mechanism secret" — it's supported by a design that, as shown here, holds up even when made public. If you're interested in the technical details, please also take a look at our page for engineers, "How it's secure."