Public betaYou're using an early version of eGuard - features may change.Try signing
Try Signing
Send a document to your own eGuard user account, approve it in the eGuard User app on mobile or desktop, and download the signed file. No setup, no sales call — the same API a website would use.
Step 1
Send a PDF
Choose a document and enter the email of your eGuard user account — the one you sign in with on the eGuard User app. Up to 5 MB.
Step 2
Approve it in the User app
It arrives in the eGuard User app, on mobile or desktop, as an ordinary signature request. Read the document, enter your PIN.
Step 3
Get the signed file
Your token makes the signature. The signed PDF appears here, ready to download and verify in Adobe.
Don't have the eGuard User app yet?
Install it and sign in with the email you use below - the request arrives there.
Watch a signature happen
Choose a PDF, place the signature on the page, and send it to your own eGuard user account. It opens in the eGuard User app, on mobile or desktop, like any other request.
The email you sign in with on the eGuard User app, mobile or desktop.
To send, add your email, a PDF.
Your document is not stored. It is held only while the request is alive, sealed to your device, and dropped the moment it is answered.
Why nobody can use this on you
A page that sends signature requests to an address anybody can type is a page that could be used to pester people. It is built on the assumption that it will be.
Only your own account can be signed
A signature is made on the owner’s own token, with their own PIN, after they have read the document. Nothing on this page can sign anything by itself.
Ten a day, one at a time
Per account, with a separate limit per network. That is the ceiling on how often anybody’s User app can be asked — and every one of them is a single tap to decline.
Declining costs you nothing
Cancel a request and you can send another a minute later; it is your own account and testing it should not lock you out. An account that declines everything and never signs is a different story, and the page stops sending there.
Nothing is stored
The document is held in memory for the few minutes the request is alive and then dropped. What is kept is the record that it was signed, in your own activity.
Want this on your own website?
The button your customers click can hand a document straight to the signer’s eGuard User app and get the signed file back — one API call, no document ever stored with us. Talk to us about an authorised API key.
Talk to us