Security & Privacy

We never see your document — unless you ask someone else to sign it.

This page explains exactly what happens to your PDF, what we store, what we delete, and where the limits of a simple electronic signature are. No buzzwords — just verifiable facts.

Flow A — Sign it yourself

80% of cases

Your browser: open PDF → sign → build file → download

No server, no transmission

Flow B — Someone else signs

only if you choose to "send" it

Your browser → link (valid 7 days) → server (mailbox) → recipient's browser

The PDF is built in the recipient's browser, the server only passes it through

Flow A runs entirely in your browser, no internet connection needed. Only when you send a document to someone else to sign does a link get created on our server — and it's automatically gone after 7 days.

Your document stays with you

When you sign your own PDF, the file never leaves your browser — no upload, no server contact, no transmission. Signing happens on your device, using JavaScript libraries that run in the browser (the same kind of technology as an in-browser image editor).

  • The PDF is displayed and edited directly in your browser — the same way a photo editor that runs entirely on your own machine handles an image.
  • Your signature (drawn or uploaded as an image) is only saved on your device if you explicitly allow it — and then stays local in your browser, never on our server.
  • The finished, signed PDF is also assembled right in your browser. You download it directly or share it yourself — we never see it.

Your document never leaves your screen — from the first view to the final download.

For the technically curious

Technically: we use pdf.js for rendering and pdf-lib for embedding the signature — both open-source libraries that run entirely in the browser (WebAssembly/JS), with no server round-trip. This flow makes zero API calls.

What happens when you share a document

If you want someone else to sign, the PDF briefly needs to sit on our server — that's the only way the link can work. But: at the latest 7 days after creation, it's automatically and irreversibly deleted, whether or not it was signed.

  • Automatic deletion after 7 days — no user action, no request, no waiting period. A daily automated process cleans up.
  • Deletion covers both the file AND the associated database entry (status, creator's email address). After that, the link simply stops existing — it leads to a clear "document expired" page, not an error.
  • One tiny, content-free record deliberately survives: a checksum (hash) of the finished document, so you or someone else can later prove that a specific file was indeed signed via SignSent — without us having to keep your contract's contents around for that (more under "Verify authenticity").
For the technically curious

Technically: a daily cron job deletes all expired entries from the database (D1) and the corresponding files from object storage (R2). The checksum table is explicitly excluded from this — but it never contains the document's content, only a cryptographic fingerprint and a date.

What we never store

No account means: there's nothing for us to build a profile out of. Specifically, we never store the following:

  • User accounts or passwords — there's no login, so there are no credentials to lose.
  • Your signature images on our server — if saved at all, they stay local in your browser only.
  • Tracking data or analytics cookies that identify you across sessions — there are no trackers on this site.
  • The email address of someone you send a document to for signing — it's only passed through to our email delivery service to send the invitation, and never stored anywhere on our end afterward.
  • Document contents beyond the 7-day window — after that, only the content-free checksum remains, no text, no image, no signature.

Verify authenticity

Anyone can check whether a PDF was actually signed via SignSent — no login required, even long after the original has been deleted.

  • When signing, we calculate a unique checksum (SHA-256 hash) of the finished document — a digital fingerprint that changes completely with even the smallest change to the PDF.
  • This fingerprint stays permanently stored in our verification database — even after the document itself is deleted after 7 days. It contains no content at all, just the hash and the signing date.

Security at SignSent — the short version

  • Runs in your browser. When you sign your own document, your PDF never leaves your device.
  • Deleted automatically. Shared documents disappear after 7 days at the latest — for good.
  • No account, no trackers. Only an unguessable link decides who gets access.
More on legal validity