Sign on this device turns the phone into a temporary host for in-person signing. The signer uses the same signing page as an email link — fields, consent, OTP, and KYC gates still come from WordPress. The WebView only loads a one-time host ticket on this site.
Before you hand over the phone
Section titled “Before you hand over the phone”- Connect the app (Connect a site).
- In WPsigner → Mobile App, note the Host PIN.
- The first time, WordPress shows a 6-digit PIN — save it immediately.
- Later visits only say a PIN is already set. Generate a new host PIN replaces the old one.
- The PIN is stored hashed on the site. It is never written to the phone.
Host a signature
Section titled “Host a signature”- Open the document (or send from a template) in the app.
- Tap Sign on this device.
- Hand the phone to the signer. They complete the document in the kiosk WebView.
- When they finish, tap Host and enter the 6-digit PIN from WordPress to unlock the device.
The host ticket is short-lived (about 15 minutes). Start the kiosk again if it expires.
What stays on WordPress
Section titled “What stays on WordPress”- The completed PDF, signatures, and audit trail
- OTP, access codes, KYC, and payment gates you enabled for that document
- The host PIN hash and the list of connected devices
Nubesti does not keep copies of those files from the app. See Data deletion.
- Use a dedicated staff WordPress user for a tablet that stays at a front desk.
- Revoke the device from Connected devices if the tablet is lost.
- Signers who receive an email do not need the app — the public signing page already works on phones.
Related: Signer workflows · Security & compliance