DashSign Privacy Policy

Effective date: June 3, 2026 Last updated: September 29, 2026

DashSign ("we", "our", or "the Extension") is a Chrome browser extension that lets you sign PDF documents directly in your browser. We built DashSign on a local-first principle: your sensitive document data stays on your device. This Privacy Policy describes exactly what we collect, what we don't, and why.

1. The short version

• We don't have a database of your documents, signatures, or profile.
• Your PDFs are processed in your browser. They are never uploaded to our servers in readable form. The two exceptions are Cloud Relay (see §4), where the signed PDF is forwarded in memory and immediately discarded, and Send for Signing (see §4b), where your document is encrypted before it leaves your browser — what reaches our servers is an unreadable payload that we cannot open or view.
• We don't sell, share, or rent any of your information to third parties.
• We use a single third-party service (Stripe via ExtensionPay) to process Pro subscription payments, and an email-sending service (Resend) for the optional Cloud Relay feature. Their privacy policies apply to data they handle on our behalf.

2. What stays on your device (we never see it)

The following data is stored exclusively in your browser's local storage (chrome.storage.local) and never transmitted to any server under our control:

• Your profile information (name, title, company, email, mailing address) that you optionally enter to use as one-click placeable fields.
• Your saved signature and initials images, whether drawn, typed, or uploaded as photos.
• Your signing history (Pro users only): a local log of PDFs you have signed, their timestamps, and their cryptographic hashes.
• The Pro Activation Agreement record — the version and timestamp at which you consented to use electronic signatures (legal recordkeeping; stored locally).
• Your preferences, including which send method is your default, whether you've dismissed onboarding banners, and your welcome-flow progress.
• Your recently seen PDFs list (file names and URLs of PDFs DashSign detected in your tabs or downloads). This is cached in chrome.storage.local for up to 24 hours and capped at 10 entries.

You can delete all of this at any time using the "Clear all data" button in DashSign's Settings tab. Uninstalling the extension also removes all of it.

3. What we receive (and why)

We receive the following limited information from third parties acting on our behalf:

Pro subscription status

When you upgrade to Pro, payment processing is handled by Stripe via a service called ExtensionPay. We receive a unique subscription token from ExtensionPay that lets your DashSign installation verify your Pro entitlement. We do not receive your credit card number, billing address, or full name; those are handled entirely by Stripe under their privacy policy (https://stripe.com/privacy).

We may receive your email address from ExtensionPay solely to restore Pro on another device or after a reinstall.

Crash and error reports

The Chrome Web Store may automatically send us anonymized crash reports if the extension throws unhandled errors. These reports do not include the contents of any PDF and are used only to fix bugs. You can disable this in Chrome's settings.

4. Cloud Relay (optional Pro email feature)

If you are a Pro user and you choose "DashSign Cloud Relay" as your send method:

1. The signed PDF is transmitted over HTTPS to our server, along with the recipient's email address, your reply-to address, and the subject and body of the email you composed.
2. Our function holds the PDF in memory only — never written to disk, never logged — long enough to dispatch the email to your recipient through our email infrastructure.
3. As soon as the send completes, the memory holding the PDF is released. We do not retain copies of the signed PDF, the message body, or the message contents anywhere on our systems.
4. We do keep a minimal access log (timestamp, your Pro token, no document content) for the purpose of rate-limiting (100 sends per user per day) and abuse detection. These logs are retained for 30 days and then deleted.

If you select "Send from my Gmail" or "Open in default mail app" instead, none of this applies — your PDF and message do not pass through our servers.

4a. Google API Services

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

4b. Send for Signing (Pro feature)

If you use the Send for Signing feature to route a document to other people for their signatures:

1. Your document is encrypted in your browser before it is transmitted. What reaches our servers is an unreadable encrypted payload — not a PDF, not a file we can open, and not something anyone at DashSign can view or access.
2. The encrypted payload exists only while signers need access to the document. Once all parties have signed, the envelope is cancelled, or it expires, the payload is permanently destroyed.
3. We store minimal envelope metadata on our servers: the envelope ID, the creator's email, signer email addresses, signing status, and timestamps. This metadata is needed to coordinate the signing workflow and is not shared with third parties.
4. Signers receive an email notification with a secure link to sign the document. These emails are dispatched through our email infrastructure. Signer email addresses are used solely for delivering these notifications and are not used for marketing or shared with third parties.
5. Phone numbers, if provided for SMS verification, are used only for identity verification during signing and are deleted from our records when the envelope completes or is cancelled.

4c. SMS Messaging

When a document sender chooses SMS verification for a signing request, DashSign sends a one-time verification code to the recipient's mobile phone number. The following terms apply to SMS messages sent through DashSign:

• We will not sell, rent, or share your mobile phone number with third parties for marketing or promotional purposes.
• When a document is sent to you for signing via DashSign, you will receive one SMS verification code per signing request. Message frequency varies based on signing activity.
• Message and data rates may apply. Contact your wireless carrier for details about your messaging plan.
• You can opt out of SMS messages at any time by replying STOP. For help, reply HELP or contact hello@dashsign.app.

5. Server-side audit records (Pro feature, opt-in)

If you opt into server-side audit records (Pro feature, off by default), the following minimal data is recorded on our server for each signed document:

• The SHA-256 hashes of the original and signed PDF (not the PDFs themselves; hashes cannot be reversed into document content)
• Your email address as the signer
• An ISO timestamp of the signing event
• A reference to the version of the Pro Activation Agreement you consented to

Why: this lets recipients independently verify, via a public URL on our site, that a document hash was signed by you at a specific time, without trusting your local device clock alone. This makes the audit trail more legally defensible.

You can disable this at any time in Settings → Audit trail.

6. What we do NOT collect

We do not collect, store, or transmit:

• The readable contents of PDFs you sign (Cloud Relay holds the PDF in memory briefly — see §4; Send for Signing stores only an encrypted payload we cannot read — see §4b)
• Your typed signature drawings, photos, or saved signature images
• Browsing history, page contents, cookies, or login credentials
• Your IP address, beyond standard server-access logs for the Cloud Relay function (kept 30 days, used only for abuse detection)
• Usage analytics, behavioral tracking, or telemetry of any kind
• Any data from PDF tabs you have open while DashSign is installed but inactive

DashSign does not include third-party analytics scripts, advertising trackers, or external telemetry SDKs of any kind.

7. Permissions we request

We request the following Chrome permissions for the reasons stated:

• storage — to save your local signatures, profile, and preferences on your device.
• activeTab — to detect when you're viewing a PDF and offer to sign it.
• tabs — to read tab URLs (only to surface "recently seen" PDFs) and to redirect the current tab to DashSign's viewer when you click "Sign this PDF".
• contextMenus — to add a "Sign with DashSign" right-click option on PDF links.
• downloads — to surface PDFs from your downloads list in the "Recently seen" panel, and to save signed PDFs to your downloads folder.
• <all_urls> host permission — required to detect and sign PDFs hosted on any website. We do not read or interact with page content unless the page is a PDF you've asked DashSign to handle.

We never use these permissions to read non-PDF page content, track your browsing, or collect any data beyond what is described in this policy.

8. Your rights

You have the right to:

• Access any data we hold about you (subscription status, audit records you opted into).
• Delete your local data anytime via "Clear all data" in Settings, or by uninstalling the extension.
• Cancel your Pro subscription anytime via Stripe's customer portal (link in Settings).
• Withdraw consent to use electronic signatures (ESIGN/UETA), which cancels the Pro tier and removes server-side audit records.
• Request a copy of any server-side audit records associated with your email address by contacting us at the address below.
• Lodge a complaint with your local data protection authority if you are in the EU/UK or California.

For users in California, you have additional rights under the CCPA (right to know, delete, opt out of sale). DashSign does not sell personal information.

For users in the EU/UK, our legal basis for processing the limited data described above is your consent (Pro subscription, Cloud Relay opt-in) and our legitimate interest in maintaining the service (rate-limiting, abuse detection).

9. Age requirements and children

DashSign is a professional document-signing tool intended for adults with a legitimate business or personal need to sign, fill, or send PDF documents. It is not directed at children, and no part of the Service is designed to appeal to minors. You must meet the minimum age for electronic signatures and data processing consent in your jurisdiction to use DashSign:

• United States: we do not knowingly collect data from children under 13 (COPPA). Signing and Pro features require you to be at least 18.
• European Union / EEA / United Kingdom: we do not process personal data of users below the age of digital consent in their member state (16 in most EU countries; as low as 13 in some). Legally binding electronic signatures require you to be 18 or the age of majority in your country.
• Canada: 18 or the age of majority in your province.
• Brazil: 18 (LGPD).
• South Korea: 14 for data processing consent (PIPA); 19 for binding electronic signatures.
• Japan: 18.
• All other jurisdictions: the age of majority or minimum age for data processing consent, whichever is higher.

If we learn that we have collected personal data from a user below the applicable age threshold for their jurisdiction, we will delete that data promptly. If you believe a minor has provided us with personal data, please contact us at the address below.

10. Changes to this policy

If we materially change this policy, we will notify Pro users by email and post a notice in the extension. The "Last updated" date at the top reflects the most recent version.

11. Contact us

For privacy questions, data requests, or to report a concern:

hello@dashsign.app B2C Innovate LLC