How it works For people who sign in

One minute to set up. One tap after that.

OT Auth links your phone number to a key that only your phone holds. From then on, signing in anywhere that supports it is a scan and a yes.

01 · Once

Set up

  1. Verify your number. Enter your mobile number and the six-digit code we text you.
  2. Your phone makes its key. Behind the scenes, the Secure Enclave or Android Keystore creates a private key that can never be copied off the phone.
  3. Create your profile. Your name, email and address, kept on your OT Auth account. Apps only see what you choose to share.
  4. Turn on App Lock. OT Auth opens only after your phone's own unlock: Face ID, fingerprint or passcode. It locks again when you leave it or after 5 minutes untouched. If you like, also set an approval PIN, asked once for each sign-in code.

Enter the code

Six digits, straight from the message.

Verify

02 · Every time

Sign in

  1. Scan. On the site's sign-in page, open OT Auth and point it at the QR code. On your phone already? Tap the site's OT Auth link and the app opens.
  2. Check. The app shows which app is asking, by its registered name, and the IP address and location of the screen. Make sure they match the device in front of you.
  3. Approve. One tap, plus your approval PIN or phone unlock if you turned on an approval check. The site signs you in on its own; you don't type anything.
  4. Windows PCs, too. On a PC that uses OT Cred, scan the code on its sign-in screen and approve. OT Auth can save that sign-in on your phone, so the next time you don't type your Windows password.
Expires in 01:24

Sign in to Acme?

Check these match the device in front of you.

Location
Mumbai, India
IP
203.0.113.9
Application Name
Acme
Approve sign-inNot me — report this

03 · First visit

Meet a new app

The first time you approve a sign-in for an app, it may ask for some of your profile, such as your name for your account or your email for receipts. The app explains why, and you tick exactly what to share. Your choices go on your activity log, so you can always see who has what.

Signed in

Bookly session is ready on your device.

04 When things are off

Built for the awkward moments too.

You didn't start it

Tap Not me — report this. The site is told to cancel the request at once, nobody is signed in, and the attempt is logged.

The code ran out

Codes last about 90 seconds. An expired code does nothing; refresh the sign-in page and scan the new one.

No internet

Scanning needs a connection. Without one, Show code gives you a code that changes every 30 seconds, for apps that accept codes.

A code from somewhere else

OT Auth only opens codes from apps registered with it. Anything else is refused, and nothing is sent.

05 Behind the scenes

Who says what to whom.

Your phone only ever talks to OT Auth, and every request it sends is signed by its key. The site only ever hears from OT Auth. Neither side handles a password.

Browser
Your server
OT Auth server
OT Auth app
  1. 01 WebSocket · qrLoginRequest
  2. 02 SessionRequested · QR link + expiry
  3. 03 Person scans the code
  4. 04 Scanned code, signed by the phone
  5. 05 POST /qrvalidate
  6. 06 IP, location, expiry
  7. 07 Registered app name + your details
  8. Person taps Approve
  9. 09 Approval, signed by the phone
  10. 10 POST /otlogin · UserID, PhoneNo
  11. 11 loginSuccess, same socket
  12. 12 loginSuccess
  13. 13 Signed in
The site creates the request and decides the session; the phone proves it's you; OT Auth checks the proof and carries the answer.