DocuAgree

Privacy Policy

Last updated: October 22, 2026

1. Who this policy covers

This policy covers two different groups of people, because DocuAgree works differently for each: account holders, who sign up, build documents, and send them for signature; and signers, who receive a document to sign and never create an account or agree to our Terms of Service. If you're a signer, Section 2 is written specifically for you — the rest of this policy still applies to your information, but Section 2 is the short version.

2. If you received a document to sign

You're reading this because someone sent you a document to sign through DocuAgree, not because you have an account with us — most people who see this section never will.

What we collect about you: your name and email address (given to us by the person who sent you the document), your IP address, browser/device information, and timestamps — captured when you view and sign the document, because the U.S. ESIGN Act and UETA require this information to make an electronic signature legally binding and to produce a certificate of completion. While you're viewing the document before signing, we also record which pages you looked at, how long you spent on each, and whether you clicked any links in it — see "Engagement analytics" in Section 3 for exactly how. If the document asks you to upload a file (a W-9, an ID, a certificate of insurance), that file — which can contain sensitive personal information — is stored as part of the signed record; see "Attachments" in Section 3 for what that means.

Who sees it: the person or organization who sent you the document, and — solely for support purposes, logged every time — DocuAgree staff (see Section 5). We don't sell it, and we don't use it for advertising.

How long we keep it: once you've signed, the completed document and its audit trail (your name, email, IP, timestamps, and signature) are retained indefinitely so that you and the sender can each retrieve your copy at any time — see Section 4 for why this doesn't change even if the sender's account is later closed.

Questions about your information specifically? Contact us at hi@docuagree.com — mention the sender's name or the document title so we can find the right record.

3. What we collect

Account information: your email address and authentication credentials (a password, or — if you choose to sign in with Google — your name, email, and Google account ID from Google; see Section 6).

Account security information: when you create an account, we record the IP address you signed up from and the approximate location (country and city) that address resolves to, using a local geolocation lookup we run ourselves — your IP is never sent to a third party for this. We also record the IP address associated with each document you send. This is separate from the signer IP address described above and in Section 2, which is captured for ESIGN/UETA compliance; this one exists for account security and to help us understand whether the free-document allowance is being used by one person opening several accounts, and it isn't used for anything else. Location from an IP address is approximate and sometimes wrong, particularly for mobile connections — we don't treat it as precise.

Document content: the documents, templates, and fields you create, and the documents you send for signature.

Signer information: when someone signs a document sent through DocuAgree, we collect their name, email address, IP address, browser/device information (user agent), and timestamps for consent and signing. This information is required to produce a legally defensible signature record under the U.S. ESIGN Act and UETA — see Section 4.

Engagement analytics: while a signer is viewing a document (after they've accepted the ESIGN consent disclosure, before they've signed), we record which pages of the document they viewed, how long they spent on each page, how many times they opened the signing link, and whether they clicked any links within the document. This is shown to the sender as a page-level breakdown on the document's detail page. It's captured only on the signer-facing signing link — we don't track a sender's own preview of their own document.

Attachments: if a document includes an Attachment field, the file a signer uploads there (limited to PDF, PNG, or JPG, up to 10MB) is stored as part of that document's signed record — this can include an ID, a tax form, or other sensitive personal information, depending on what the sender asked for. It's accessible only to that signer and the document's sender, is retained under the same policy as the signed document itself (Section 4), and — once the signer completes the document — can never be replaced or deleted by either party, the same way the signature itself can't.

Payment details: your subscription is billed by Stripe, our payment processor. We do not store your full card number — Stripe handles and stores that. We retain limited billing metadata (card brand, last 4 digits, subscription status).

4. Retention and deletion

Signed documents and their audit trail are retained indefinitely, regardless of account status or a deletion request, and this is a deliberate policy, not an oversight. Once a document is fully signed, we keep the completed PDF, the certificate of completion, any attachments uploaded as part of signing, and the full event history (consent, view, and signing timestamps, IP addresses, and signature data) for as long as the Service operates — so that every party to that agreement can retrieve their copy at any time, even if the sender's account is later closed, blocked, or deleted, and even if a signer asks us to delete their data. This is consistent with the retention expectations of electronic-signature law, and with the promise made to every signer before they sign (Section 2) that they'll be able to get their copy back later. We can't honor that promise selectively.

Data we can delete on request: an account holder's profile information, unsent draft documents and templates, and any documents that were never actually sent for signature. If you ask us to delete your account, we'll delete or anonymize this data; documents that were sent and are still awaiting signature will stop being accessible (their signing links deactivate) rather than continuing indefinitely with no one able to manage them.

We also retain limited operational data — audit and access logs — for as long as reasonably necessary for security, abuse prevention, and legal compliance, even after the underlying account or document is deleted.

5. Support and administrative access

DocuAgree staff can, for support purposes (for example, investigating a billing issue or a report of abuse), look up an account, view its documents and templates, and take a small number of account-level actions like blocking or unblocking it. Every such lookup, view, and action is logged — who accessed it, what account or document, what they did, and when — separately from the ESIGN audit trail on your documents.

Support can also edit a draft document or a custom template on your account directly — for example, to fix a broken field placement you reported. This never extends to a document that's already been sent, viewed, completed, voided, or expired: once a signature could be bound to it, nothing in our support tooling can modify it, enforced the same way for our own staff as for you. It also never includes the ability to send a document, delete anything, or change your contacts, account settings, or billing. Before this kind of edit can even begin, the staff member has to record a short reason for it, and that reason — along with what was changed and when — is both logged and emailed to you automatically, every time, with no exception and no way to turn it off. An admin edit is never counted as your own activity in your document history.

6. How we use this information

We use it to operate the Service: rendering and sending your documents, authenticating signers, producing the audit trail and certificate of completion, showing you the engagement analytics described above, processing billing, providing support (Section 5), and sending transactional email (signing requests, reminders, receipts, account notices).

If you choose to sign in with Google, we use the identity Google gives us (your verified email address) only to create or log into your account — we don't request or receive access to your Google Drive, contacts, or other Google data.

7. Third-party processors

We share data with a small number of service providers who help us run the Service, and only for that purpose:

We do not sell your personal information.

8. Cookies and tracking technologies

We use a small number of essential, first-party cookies: one to keep you signed in, one to protect forms against cross-site request forgery, one short-lived cookie to show a one-time confirmation message after certain actions, and (only if you use "Sign in with Google") two short-lived cookies to secure that round trip. Inside the app and on signing links, those are the only cookies there are: no advertising or tracking cookies of any kind.

The engagement analytics described in Section 3 don't use a cookie on the signer's device at all — they're tied to a one-time session identifier embedded directly in the signing page itself, not stored in the signer's browser beyond that page.

On our public marketing pages (the homepage, pricing, comparisons, guides, and similar pages — not the app itself, and never a signing link), we use Plausible, a privacy-friendly analytics service. It doesn't use cookies or any other persistent identifier, doesn't collect personal data, and doesn't track you across other websites — it reports only aggregate numbers like how many people visited a page or completed a signup, never anything tied to a specific visitor.

Those same public marketing pages also load the Google Ads tag, so we can tell whether our ads on Google lead to visits and signups, and so Google can show our ads to people who have visited this site before ("remarketing"). It's set by Google, not by us: it may store advertising cookies (such as _gcl_au) in your browser and send Google your IP address, browser details, and the pages you view, which Google handles under its own privacy policy. If you're visiting from the European Economic Area, the UK, or Switzerland, the tag is set to store no advertising cookies at all. It's never loaded on a signing link, and inside the app it appears on exactly one page: the confirmation screen right after you start a paid subscription, where it records that a subscription was purchased (the amount and an order reference) and is told a fixed page address and title. So nothing about your documents, or about anyone you send a document to, reaches Google through it. You can opt out of personalized Google ads at adssettings.google.com, or block it with any standard ad or tracker blocker without affecting how DocuAgree works.

9. Your choices

You can access, export, or request deletion of your account data by contacting us at hi@docuagree.com. Signers can request a copy of a document they signed, or ask what information we have about them, the same way. As explained in Section 4, we may need to retain a signed document and its audit trail even after a deletion request, where the record is still legally relevant to the parties involved.

10. Security

We use industry-standard measures to protect your data, including encryption in transit (TLS/HTTPS) for the entire Service, access controls limiting who can reach account data (including the logged administrative access described in Section 5), password hashing (we never store passwords in plain text), and a tamper-evident hash of every completed document. We also use the account signup and sending IP information described in Section 3 to look for patterns of one person opening multiple accounts to bypass the free-document allowance — this is a measurement we look at internally, not an automated system that blocks or restricts an account. No system is perfectly secure, and we can't guarantee absolute security. If we experience a data breach affecting your personal information, we'll notify affected users without undue delay, consistent with applicable law.

11. International users

DocuAgree is built for the U.S. market and hosted in the United States, and this policy is written around U.S. law (the ESIGN Act, UETA). We know some visitors and signers may be located outside the U.S. — we haven't built out region-specific mechanics like a GDPR data processing agreement or an EU representative, so if you're located outside the U.S., understand that your information will be processed in the U.S. under U.S. law. If you have a specific regional privacy requirement, contact us at hi@docuagree.com.

12. Changes to this policy

We may update this policy from time to time. We'll update the "last updated" date above when we do, and for a change we consider material we'll make reasonable efforts to notify account holders before it takes effect.

13. Contact

Questions about this policy, or a request to access or delete your data? Contact us at hi@docuagree.com.