Local-first
PDF signing.
Cloud when you want it.

Yes. DashSign produces electronic signatures that meet the requirements of the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA), which together make e-signatures legally enforceable for the vast majority of business contracts. Pro users complete a one-time Activation Agreement establishing consent, intent to sign, and identity authorization — the four ESIGN/UETA pillars.

Certain documents are excluded from electronic signature under U.S. law: wills, court orders, divorce decrees, adoption papers, and a few others. For those, use traditional signing or consult an attorney.

Your PDFs are processed in your browser. They're never uploaded to our servers, never stored in a database, never seen by us. Your saved signatures, your profile information, and your signing history all live in your browser's local storage — the same place your bookmarks live.

The exceptions are Cloud Relay and Send for Signing (both optional Pro features). Cloud Relay passes your signed PDF through our servers in memory only — long enough to dispatch the email and no longer. With Send for Signing, your document is encrypted before it ever leaves your browser. What reaches our servers is an unreadable payload — not a PDF, not a file we can open, not something anyone at DashSign can view. It exists only long enough for your signers to complete the process; once all parties have signed, the envelope is cancelled, or it expires, it's permanently destroyed.

When you send via Cloud Relay, your signed PDF is sent over an encrypted (HTTPS) connection to our relay, which holds it in memory only — it's never written to disk on our servers. The relay hands the email to our delivery provider, which sends it to your recipient from signed@dashsign.app with reply-to set to your address. Once the email is on its way, the in-memory copy is released. Nothing is stored, logged, or accessible afterward.

In short: we can't read your document and we keep no copy of it. And if you'd rather not route through us at all, the other two send options — your own Gmail, or your default mail app — never touch our servers. Cloud Relay is a Pro feature.

The established e-signature services are built around storing your contracts on their servers, routing them through their own workflow, and often charging per document. DashSign inverts that: your documents stay on your device, you pay a flat fee (or nothing on the free tier), and the only thing our servers ever do is deliver signing requests, forward an email (optional), and co-sign an audit trail (optional). For prosumer and small-business signing, DashSign is faster, cheaper, and more private.

With Send for Signing (Pro), you can route documents to multiple people for their signatures — sequentially (one after another) or in parallel (everyone signs independently). Track status, resend reminders, or cancel, all from the extension. Signers don't need DashSign or an account.

Yes. DashSign fills standard interactive PDF forms (AcroForms) — click a field and type, check boxes, choose options — then sign and download with your entries baked into the final PDF.

Some older PDFs use Adobe's retired XFA (LiveCycle) format, which browsers — including Chrome and Edge — can't display; you'd normally see an "upgrade Adobe Reader" placeholder. DashSign detects these and tells you clearly instead of showing a blank page. To fill an XFA form specifically, open it in Adobe Acrobat. Standard PDFs and interactive forms work great in DashSign.

They're deleted. Local storage is wiped when you uninstall the extension. For Pro users, we'll offer a "Backup & Restore" feature that lets you export your saved signatures, profile, and history as an encrypted JSON file you keep yourself. Your Pro subscription itself is tied to your purchase email, not to your local data — reinstalling and logging in restores Pro entitlement.

Yes — Pro entitlement syncs across the Chrome profiles you're signed into. Your local data (signatures, profile, history) doesn't sync automatically, which is the privacy trade-off of local-first. If you want it on a second device, use the upcoming Backup & Restore feature to move your data deliberately, or set it up fresh.

Not yet. We may open-source parts of the free tier in the future — exactly the kind of "audit our claims" trust signal that fits our positioning. For now the code is proprietary (B2C Innovate LLC), and the architecture is designed so that the privacy-critical parts (local document handling, signing math) run entirely in your browser where you can inspect them in Chrome DevTools at any time.