Data processing summary
What this server processes, for whom, for how long, where, and how it is deleted.
What this page is, and what it is not
It describes what the software does with personal data. It is not a contract and not legal advice. If you need a signed data processing agreement, for example because the GDPR applies to you, that agreement is between you and whoever runs this server. The software cannot sign one for them, and no standard contract comes with it. The operator of this server has not said who they are. Ask them. Reach them through the contact form.
Who decides, and who handles
- You, the account holder, decide which documents are uploaded, who they are sent to and how long they are kept.
- The operator of this server stores and handles them for you with this software. The software does not read documents to sell anything, does not pass them to an AI service and does not use them to train one. What the operator does beyond the software is for them to say.
- The people you send to get what you send them, and keep their own copy of what they signed.
What is processed
- About account holders: name, email address, a salted hash of the password (never the password), a job title and company if given, a saved signature and initials if saved, team memberships, and notification settings.
- Documents: the files you upload, the text read from PDFs so that you can search your own envelopes, the fields placed on them, the signed PDFs with their certificates, and files that signers attach.
- About the people you send to: the name and email address you typed, an access code or a mobile number if you set one, what they filled in, their signature and initials as pictures, and when they opened, agreed, signed or declined.
- The audit trail of every envelope: each step with its time, the internet address it came from and the kind of browser.
- Emails: a copy of every email this server sends, and whether the mail server took it.
- Payments, if you pay: what was paid, refunded and bought, and the provider's reference for it. A full card number never reaches this server.
- Help requests: what was written, by whom, and the answers.
For how long
- As long as the account exists. Cancelling a plan or a failed payment deletes nothing.
- A draft, a template, or a closed envelope that nobody signed is deleted for good when you delete it.
- An envelope that somebody signed cannot be erased by itself. Deleting it takes it out of your lists, search and export, and its recipients keep their link and their copy. It is deleted when the account is.
- Our copies of emails that belong to no document (invitations, notices, receipts) are deleted after 90 days. Copies of emails about a document stay with that document.
- An unfinished start from a public form is closed after 24 hours without anyone touching it.
- A file dropped on Verify a document is not stored.
- A closed account is kept for 30 days so that it can be brought back, with an email to its owner 7 days before the end, and is then deleted. You can also delete it at once.
- Backups: The operator of this server has not said whether and where backups are kept. Ask them.
How it is deleted
Under Settings, Your data, Close my account, at once or after the 30 days. This goes for good:
- Your login, your profile and your saved signature.
- Every account you own: its envelopes, drafts and templates, the documents you uploaded, the signed PDFs, the files signers attached and every audit trail, with the names, email addresses and internet addresses in them.
- Its contacts, API keys, webhooks and their delivery logs, bulk send records, public forms and reports from recipients.
- Its click-to-agree terms with every version, every acceptance recorded for them (with the names, email addresses, customer numbers, internet addresses, browsers and pages in them), reports about their pages, and our stored copies of the emails that sent people a copy of what they accepted.
- Our stored copies of the emails about those envelopes, and of the emails we sent you about your account.
- Help requests of yours that have been answered or closed, each with everything written back and forth on it.
This stays, and why:
- The record of payments, refunds and of signatures bought and used, without your name or your email address, because accounts have to be kept. If you ever paid, the payment provider has its own record of that.
- A help request that nobody has answered yet, or on which we asked you something and wait for your reply. It is deleted once it has been answered. The answer is emailed to you first. An unanswered question of ours is kept for 30 more days, then deleted.
- A help request you wrote while signed in, but under somebody else's email address. Its answers go to that address, so it belongs to that mailbox and stays for it, without your login, your account or your name. It is deleted like the other requests of that address.
- Documents other people sent you, with what you did on them, such as your signature or a report you made. They belong to whoever sent them.
- What you sent as a member of a team you do not own. It belongs to that team and passes to its owner, and its audit trail says so. An API key you made there stays on the team's list as stopped, under your name.
- Signed PDFs your recipients downloaded or were emailed. Those are theirs. The links in our emails to them stop working.
- A fingerprint of the security code in each email about a document you sent, for one year. It holds no name, address or title. It only lets someone who still has that email learn that it was real and that the document has been deleted.
- For each completed document you sent: the fingerprint (SHA-256) of its signed PDF, its envelope ID and the day it was completed, for one year. Nothing else: no name, address or title. It only lets someone who holds that exact file learn at Verify a document that it was completed here on that day and that its sender has deleted it since.
- A fingerprint of your email address and the day you were given the welcome signatures, if your address was confirmed. The welcome signatures are given once per address, and this is how we know after your login is gone, or after it moved to another address (that fingerprint is kept from the day it moved). It is made with a key only this server has, cannot be turned back into your address, and holds no name.
- Our stored copies of emails to other people are deleted with the account when we know they are about you: an invitation you sent, or a notice to a team about your API keys or that you left. Any other copy that happens to mention your name goes with all such copies, 90 days after it was sent.
Where it is, and who else handles it
- The server and its files: Frankfurt, Germany. Hosted by Render. There is one region, and it cannot be chosen.
- What leaves the server: only what the table lists. There is no analytics service, no advertising and no AI service.
| Who | Where | What for | What reaches them | Whose data |
|---|---|---|---|---|
| Render | Frankfurt, Germany | Runs the server and stores the database and every file. | Everything: documents, signed PDFs, signatures, names, email addresses, internet addresses, audit trails and our copies of emails. | Everyone who sends or signs here. |
Not in use on this server: No mail server is set up on this server, so no email leaves it. Payments are not connected on this server, so nothing goes to a payment provider. Signing in with Google or Microsoft is switched off on this server. Text messages are switched off on this server, so no phone number goes to a text message provider.
Not stated by the operator of this server. Ask them before you rely on this page for any of it:
- The operator of this server has not said who they are. Ask them.
- The operator of this server has not said whether and where backups are kept. Ask them.
How it is protected
- Passwords are kept as salted scrypt hashes. API keys and login sessions are kept as fingerprints, never as written.
- Only the people a document was sent to, its sender and the admins of the sender's account can open it. Sign-in attempts, access codes and the public forms are rate limited.
- The audit trail of every envelope is hash chained, so a changed or missing entry shows.
- What the software does not do: it adds no encryption of its own to stored files, so how the disk is protected depends on the host. It has no security certification. The security page lists the rest.
Taking your data with you
Settings, Your data, Export everything: one ZIP file with every signed PDF, every audit trail and a list of all envelopes. Free on every plan, also after cancelling.
Something on this page that is not true? Tell us. A person reads every message.