Would you sign a contract in a tool that never uploads the file?

by

We launch on Tuesday, and I would rather find out I am wrong before then than after.

The premise: signing your own PDF happens entirely in your browser. The file is never uploaded — you can open the network panel and watch nothing leave. Every mainstream tool uploads first, because that is simpler to build and because it enables features we deliberately do not have.

Two honest limits, so this is not a pitch:

1. The moment someone ELSE has to sign, we do upload it. There is no way around that, and any product claiming otherwise is lying. Encrypted in transit and at rest, deleted 30 days after completion.

2. Our sealing certificate is self-issued right now, so Acrobat renders the signature as "validity unknown". The seal detects tampering; it just cannot prove who issued it until we install a publicly-trusted cert.

What I actually want to know from people who send contracts:

- Does browser-only signing solve a problem you have, or is it a nice-to-have you would not pay for?

- Has "your file never leaves your device" ever been a reason you chose one tool over another?

- If you left an e-signature tool, was it the software or the billing?

I am one person building this, so blunt answers are more useful than encouraging ones.

1 view

Add a comment

Replies

Be the first to comment