Solutions
Your device approves. The site verifies.
Rhea Key is designed as a global passwordless sign-in method for websites and applications—not a login available only inside Rhea Data. On participating sites, your device approves and the site checks the signed proof.
A practical example
Your device approves. The site verifies.
A visitor chooses Rhea Key on an independent participating website. On desktop, they scan its QR code, confirm the two-digit match and approve on their device. The site checks the signed proof before creating a session—without asking the visitor to remember another password or old login email.
Your device approves. The website verifies.
01 / Participating website
A fresh request, for this site.
shop.example
Scan the fresh QR request with Rhea Key
42
02 / Your Rhea Key device
Scan, match and approve.
42Confirm the same two digits, check which site is asking, then approve on your device.
03 / The website backend
Verify the response. Start the session.
The device returns a signed response. The website checks its challenge, binding, expiry and signature, rejects reuse, then creates its own session.
Rhea Data is not required.
- 01
Integrate the sign-in entry
Use the Rhea Key SDK or supported integration protocol. The participating site creates a short-lived, site-bound challenge.
- 02
Approve on the device
The person sees which site is asking, confirms the number match and approves. Supported mobile flows hand off directly to Key; the private key is not sent to the website.
- 03
Verify before signing in
The site checks the signed response, expiry and replay protection on its backend.
Architecture and scope
A clear model for your environment.
A simple sign-in UI still requires proper backend verification, replay protection and a valid site integration. No Rhea Data connection is required. Rhea Key is not a password manager or crypto wallet; worldwide support is the goal, not current universal availability.