Privacy Policy
Contents
Who We Are and How to Contact Us
DocSpring, Inc. is a Delaware corporation. Our mailing address is 9450 SW Gemini Dr, PMB 95273, Beaverton, OR 97008-7105, United States. For privacy questions or requests, contact our privacy officer at support@docspring.com (attention: Privacy).
Our EU representative under Article 27 of the GDPR is Rickert Rechtsanwaltsgesellschaft mbH, Colmantstraße 15, 53115 Bonn, Germany. You may contact our representative at art-27-rep-docspring@rickert.law.
Our Role
DocSpring is the controller for information we use to manage our website, customer accounts, billing, support, and business relationships. When customers use DocSpring to generate documents, collect form responses, or obtain signatures, we handle that content on their instructions as a processor or subprocessor. The customer determines the purposes of that processing and is responsible for its privacy notice and lawful instructions. Our Data Processing Agreement (DPA) governs our handling of that content, subject to any applicable separately executed DPA.
If your information appears in a document or form submitted by one of our customers, contact that organization to exercise your rights. If you contact us, we will help identify the appropriate customer where possible and assist under their instructions and applicable law.
Information We Collect
- Account and contact details, including names, email addresses, company details, how you heard about us (if you tell us), user identifiers, permissions, and authentication information.
- Billing contacts, addresses, tax IDs and business details, invoices, payment status, and payment references. Stripe handles card entry and payment processing.
- Support and sales correspondence, including information and attachments you choose to send.
- Usage and security information, including IP addresses, browser and device information, request and event records, timestamps, and error reports.
- Customer-provided templates, document contents, form answers, and signatures. Form and signing records can also include names, emails, IP addresses, browser information, and completion events.
- Page images from our free tools. When you use Make a PDF fillable, your browser sends us an image of each page of your PDF to find its form fields. A page image shows anything already filled in on the page.
- Details you type into our public demos, such as form library web forms and code examples. We use them only to show you the demo.
We receive information from you, your organization's administrators and users, customers who submit documents or forms, and providers involved in authentication, payment, support, and service operation. Some information is collected automatically when you use the service. Account and authentication details are needed for access, and billing details are needed for paid services. Without required information, we may be unable to provide the relevant service. You choose what to include in optional communications.
How and Why We Use Information
Where the GDPR applies to our activities as a controller, we rely on the following legal bases:
- Accounts, billing, and requested support: performance of our contract when you are the contracting individual, or our legitimate interests in providing and administering services to your organization.
- Security, abuse prevention, troubleshooting, and improvement: our legitimate interests in operating a reliable, secure service and understanding its use, subject to your rights and reasonable expectations.
- Business correspondence and administration: our legitimate interests in responding to inquiries, managing relationships, and maintaining necessary records.
- Free tools and public demos: our legitimate interests in providing the tool or demo you choose to use. We use page images only to find their form fields, and demo details only to show the demo.
- Legal obligations and claims: compliance with applicable obligations where they provide a legal basis under the GDPR, and our legitimate interests in establishing, exercising, or defending legal claims.
- Optional marketing and tracking: consent where required by law. Where permitted, we may rely on our legitimate interests in communicating relevant information to existing business contacts. You can object to direct marketing at any time.
Customer document contents are processed to provide the requested document, form, signature, storage, delivery, and support services under customer instructions. The legal bases for our own business activities do not authorize unrelated uses of customer document contents.
Service Providers and Other Recipients
We use Amazon Web Services for hosting, storage and marketing email, Cloudflare for network delivery and security, Stripe for payments, Intercom for support, Postmark for transactional email, Kickbox to check email addresses before we send marketing email or account deletion notices, and Sentry for error monitoring. Google reCAPTCHA protects sign-up, email preferences and some free tools from abuse. Business email and collaboration services include Google Workspace, Slack, and Notion. We use Savio to track customer feedback and Shortcut for project management. We also use tools for development, access control, and compliance. Our Plausible analytics service is hosted on Render. Each provider's access depends on its function and the features you use; a billing or development provider does not necessarily receive document contents.
We use AI assistants from Anthropic and OpenAI for software development and support, with model training turned off. We don't deliberately give consumer AI plans customers' documents or form data; API services under a data processing agreement may see them when we debug a support case. AI field setup and section suggestions send a template's page images and field details to Claude on Amazon Bedrock, within your account's US or EU geography, and they aren't used to train models. We keep a searchable archive of our company records, including support history: OpenAI's API powers its search and Backblaze B2 stores its encrypted backups.
We may share information with professional advisers where necessary, authorities when legally required, or in connection with a business transfer, subject to applicable privacy requirements. Customer-configured webhooks and integrations deliver information to destinations the customer selects. We do not sell personal information. Our DPA and subprocessor list describe processing on your behalf. Contact us for details of the terms applicable to your use of DocSpring.
International Processing and Transfers
DocSpring, Inc. is a United States company. Customers can select production hosting in the United States (Northern Virginia) or Germany (Frankfurt). These environments have separate databases and document storage. EU database backups are configured in Frankfurt without cross-region copying. Our team operates from New Zealand through DocSpring NZ Limited, a separate service provider for development, operations and support. Authorized personnel may access customer data for those purposes under our instructions and data-protection requirements.
Migrating an account between regions does not delete the copy in the former region. That copy stays there until the customer confirms they no longer need it. It is then deleted after a 14-day grace period, and it is never deleted automatically before that. Recovery copies have their own retention periods. Security log entries are not moved with an account: they stay in the region where they were recorded. Applicable customer instructions, agreements and retention requirements continue to govern those copies.
Regional document storage does not mean all processing remains in that region. Network and security providers, email, support, billing, and other business services may process information in other countries. Customer-selected delivery destinations may also be outside the EEA.
International transfers subject to the GDPR require an applicable adequacy decision or appropriate safeguards, such as applicable European Commission Standard Contractual Clauses. New Zealand has an EU adequacy decision; it does not cover transfers to our US company or every other provider. We do not rely on the former EU-US Privacy Shield. Contact support@docspring.com to request details or a copy of the safeguards applicable to your information, with confidential information redacted where necessary.
Retention and Deletion
We retain information for the relevant service or business purpose, considering customer instructions, account status, unresolved support matters, applicable recordkeeping requirements, and legal claims. Different records have different retention periods, described below.
Submissions and documents
Each account has three data retention settings: one for submissions, one for submissions with signature requests (signed documents), and one for the PDFs made with our PDF tools, such as combined PDFs. Each template can set its own "Expire Submissions" setting instead. New accounts delete submissions 30 days after they're processed and the PDF tools' files after one day, and keep signed documents until they're deleted. Accounts created before these settings were introduced in November 2026 keep everything until it's deleted, unless a setting is turned on; an account whose template defaults expired submissions keeps that period for submissions and signed documents. A template's own setting defaults to seven days when enabled. When a setting is turned on or shortened, records already older than the new period are expired too, starting 24 hours after we email the account's owner and the person who made the change. You can also expire a submission through the API. Downloading a document does not delete it.
Expiring a submission deletes its generated documents and preview, its submitted data and metadata, its webhook data, the submitter's IP address, browser and location, its compiled HTML, and its images. For a signed document, it also deletes the signature requests, the signers' names, email addresses, answers and signatures, their authentication and event records, the emails we sent about it, the audit trail, and the hash manifest. We keep technical details of the submission, such as its ID, state, template, test or live status, times, and document hashes.
A submission that fails is kept for at least 48 hours, even if its period is shorter, so that a retry still has its data. Test submissions are deleted after 30 days. Details typed into our public demos are deleted within an hour. Page images sent to our free tools are deleted once their fields are found, or within an hour if something goes wrong. Where the fields are on each page is kept for an hour, for your browser to collect. Account export archives are deleted after 6 months. If storage charges on a credit-based plan stay unpaid for 90 days after live processing pauses, we expire the account's stored documents that are past their included 30 days of storage in the same way, after notifying the billing contact.
Signing integrity records
When a live signing completes, we write an integrity record: hashes of the signed PDF, its audit trail and its signing events, with the account, submission and template IDs, the times, the number of signers and how each one was authenticated, and the kind of record. It does not include signers' names, email addresses, IP addresses or document contents. We keep it for at least 10 years, with no fixed deletion date, including after the submission expires or the account is deleted. For the first 10 years it's in storage that can't be changed or deleted. Anyone with a copy of a signed document can check it against this record at docspring.com/verify, or eu.docspring.com/verify for a document signed in the EU region. Test and demo signings get no integrity record. The integrity record can't reproduce a document or show who signed it, so customers are responsible for keeping the signed document and audit trail for as long as they need them.
Deleted templates and removed users
A deleted template goes to Trash, where it can be restored for 30 days. After that we permanently delete it. If it still has submissions, we keep what they need until the account is deleted, such as its name, ID, field definitions, shared field values, and its expiry and webhook settings. Users removed from an account are permanently deleted after 30 days.
Suspending and deleting an account
Suspending an account is a pause: its data is kept, and it can be reactivated. A suspended account that hasn't been used for a year is deleted 30 days after we email its billing contact, or its other users if that address can't be reached. If nobody can be reached, the 30 days start anyway.
Deleting an account, with Delete Account or by asking us, cancels the subscription, suspends the account and rejects its API requests. We permanently delete the account's data at least 14 days later, unless a user of the account signs in first, which cancels the deletion.
After we delete an account's data, we keep:
- a minimal record of each account, paid or free (such as its company name and website, plan, lifetime value, how it signed up and heard about us, dates, and the date of any BAA), indefinitely;
- billing records in Stripe, which have no fixed deletion date, for at least as long as accounting law requires;
- signing integrity records, which have no fixed deletion date, for at least 10 years;
- security log entries, for 3 years from when each one was recorded;
- a record of the deletion itself, which we use to reapply it if we ever restore a backup.
For erasure of associated personal information, contact support@docspring.com. We review each request and any lawful retention requirements, and tell you what we erased and what we kept. Account closure alone is not confirmation of complete erasure.
Support history
We keep support history indefinitely as business records: conversations in Intercom, our searchable company archive, customer feedback in Savio, and sometimes project tickets in Shortcut, code review comments and commit messages. Please don't send us documents through support unless we ask for them, because anything you send stays there until you ask us to remove it. When someone explicitly asks us to delete or erase support history, we review the request and delete or anonymize it. Notifications about account activity in our internal Slack channels are kept for up to 1 year.
Recovery copies and logs
Recovery copies have separate configured periods: automated database backups are retained for 30 days, weekly snapshots for 90 days, and monthly snapshots for 365 days. Automated Redis snapshots are retained for 7 days in both regions. One-off snapshots taken for maintenance or migrations are deleted within 30 days of creation. These periods run from creation of each backup. A backup created shortly before live data is erased can therefore remain for almost another 365 days. Previous versions of deleted or replaced document files in Amazon S3 are scheduled for permanent deletion after 180 days as a previous version. Uploaded files waiting to be used are deleted from our upload cache after 30 days, and earlier versions of them after 7 days. S3 lifecycle deletion runs asynchronously. Personal data removed from the live service can remain for up to 1 year in backups and internal notifications. These descriptions do not override obligations under an applicable DPA or data protection law.
API and webhook database logs are subject to a 90-day deletion schedule. Audit history, sign-in records, records of emails we've sent, and records of visits and events in the app are kept for up to 3 years. Some go sooner, with the submission, template or account they belong to. Records of access to stored documents, including IP addresses, are kept for 3 years, and EU records are stored in the EU. Security log entries record actions on an account, such as sign-ins, changes to credentials, API tokens, team members, billing and settings, exports and imports, and our staff's access to it. They hold account, user and record IDs, IP addresses and details of the action, and no names, email addresses or document contents. We keep them for 3 years to investigate security incidents, including after the account is deleted. The users of an account may also see its entries and the IP addresses in them. Hashes of these entries, with account IDs and no IP addresses, stay in storage that can't be changed and have no fixed deletion date. Other security and access logs have separate periods, described on our security page. Billing, correspondence, and legal records can require retention after an account closes. Contact us for retention information relating to a particular record or request.
Cookies and Similar Technologies
We use browser storage for account sessions, security, and preferences. We self-host Plausible at pa.docspring.com for usage statistics; it does not use cookies. Two optional purposes use cookies on our website: referral attribution, which remembers the page or campaign that first brought you to us so that we can attribute a later sign-up, and advertising, which lets Google Ads tags measure conversions. In the EEA, UK, and Switzerland, or when we cannot determine your country, these optional cookies wait for your consent. Elsewhere, they may operate unless you decline them or your browser sends a Global Privacy Control signal, which we honour in every region.
Use Cookie settings to allow or decline referral attribution and advertising separately, or to allow or decline both. Your choice is stored in a cookie shared by our website and app and can be changed at any time; declining a purpose removes its cookies. Declining optional cookies does not affect our cookieless Plausible statistics. We retain server-side session and security history, including sign-in attempts and relevant account actions, to operate and secure the service. That history is not browser analytics, uses no optional cookies, and is not controlled by Cookie settings.
Intercom provides the support messenger and is independent of Cookie settings. In the app, it loads for signed-in users as part of the service. On our website, it loads automatically only where consent for optional cookies is not required; elsewhere it loads when you request support through Help or Open Live Chat, and that request is remembered for your browser session. Signing out ends the local Messenger session and removes its cookies. You can also manage stored cookies through your browser and contact us about your privacy choices. Blocking cookies needed for authentication or security may prevent parts of the service from working.
Visual forms can save unfinished answers in your browser so they are available after you reload the page. The saved draft is removed when you successfully submit or clear the form. Otherwise, it can remain until you clear that site's browser storage.
Marketing Choices
Unsubscribe from marketing using the link in a message or by contacting us. Withdrawing marketing consent or objecting to direct marketing does not prevent necessary account, billing, security, or service messages. Permission to use your name, logo, or testimonial for publicity is agreed separately; accepting this privacy policy does not grant it.
Your Privacy Rights
Where the GDPR applies, you may request access, correction, erasure, or restriction of processing. You may request a portable copy of information you provided where processing is automated and based on consent or a contract. These rights are subject to the conditions and exceptions in applicable law.
You may object to processing based on legitimate interests for reasons relating to your situation, and to direct marketing at any time. Where processing relies on consent, you may withdraw it at any time without affecting the lawfulness of earlier processing.
Send requests to support@docspring.com or our EU representative. You do not need a paid account or a particular form. We may ask for information reasonably necessary to verify identity or authority, without collecting unnecessary identification documents. For requests we handle as controller, we respond without undue delay and normally within one month of receipt. If the law permits an extension because of complexity or the number of requests, we will explain the reason and extension within that first month. Requests are normally free; any refusal or permitted fee must meet the conditions in applicable law and will be explained.
You may complain to a supervisory authority, particularly in the EEA country where you habitually reside, work, or believe an infringement occurred. You do not have to contact us first. Contact details are available from the European Data Protection Board.
Security and Restricted Data
Public service connections use HTTPS/TLS. RDS databases, Redis and S3 document storage are encrypted at rest, and connections to Redis are encrypted in transit with TLS. Our safeguards are described on the security page. Do not submit payment-card information as document or form content. DocSpring is not PCI DSS certified. Requirements for other regulated information, including US protected health information, are described on our security page and in applicable agreements.
Changes to This Policy
We may update this policy as our services or practices change. We announce changes to this policy on docspring.com/updates. An updated notice does not replace required consent or amend a separately agreed DPA.
Questions?
Contact support@docspring.com with questions about this policy or your personal information.