Why services ask for your email
Hosted e-signature tools use email as the identity and delivery channel: they invite signers by email, send reminders, and deliver the finished document as an attachment or link. That is useful for routing, but it means your address is stored and the signed document sits in mailboxes and on the provider's servers.
How it works here
You open the page, choose the PDF, sign, and click Finalize. The browser saves the signed file like any download. No address, no confirmation link, no "your document is ready" message. The name on the completion certificate is whatever you type into the signer field, which can be your full legal name as the document requires.
Sending it back
You still need to return the document to whoever asked for it. You can attach it to your own email, send it in a chat app, or upload it to the portal that requested it. Because you choose the channel, the signed file travels through one route you already trust instead of two.
What the recipient sees
The last page of the signed file is a completion certificate listing the document name, the signer name and role you entered, the signing time, and SHA-256 hashes. It doesn't list an email address, because none was collected. A QR code on that page opens the verifier, so the recipient can confirm the file hasn't been changed since you signed it.
The one time we ask for an email
Only when you buy Pro: the email address is used to issue and recover your licence and is handled as described in our Privacy Policy. Free signing never needs it.