Security and trust
This page says what the software does today, in plain words. It also says what it does not do. If something is not written here, do not assume it.
For people who sign
- You never need an account or a password.The link in your email is all you need. Nobody is asked to register, log in or start a trial in order to sign.
- You are never sent marketing.We email signers only about documents they are part of: the request, reminders, changes and the completed copy. You can switch off reminders for a document with one click.
- Your link does not wear out.It works for as long as the document is open, however many times you open it. There is no limit on clicks. If a deadline passes, the sender can reopen the document and the same link works again.
- You can check that an email is real.Signing requests, reminders and completion emails carry a security code. Type it in at Check an email and we tell you which address sent it and under what name. You can report the email there too, without opening the document.
- You always know who is asking.Each request names the sender and their email address, and a reply goes straight to that person.
- You get your copy, also later.Everyone on a document gets the completed PDF. Find my documents sends the link again to the same inbox, for as long as the sender keeps their account. A sender who deletes a completed document only takes it out of their own lists: your link and your copy stay.
- Extra protection when the sender wants it.A sender can put an access code of at least 4 characters on a document. They give it to you themselves. It is never in our email. After 10 wrong tries the code is frozen, so it cannot be guessed, until the sender sets a new one.
- A one-time code, when the sender asks for one.Before the document opens we can send a 6-digit code to your email address, and you type it in. It is sent only when you press the button, works for 10 minutes and for 5 tries, and the screen shows the address or number with most of it hidden. Until the code is typed, the page shows nothing of the document: not its name, not the message, not who else is on it. If the code never comes, or the number is not yours, a button on the same screen tells the sender, who is the only one who can change it. A code by text message exists in the software, but the operator of this server has not switched text messages on, so nobody is offered it here.
- What each check proves, and what it does not.The link alone. With no check, a document opens for whoever has the link from our email. That shows the email reached a mailbox, and says nothing about who opened it. An access code. A secret the sender chooses and passes on themselves, by phone or in person. It shows that whoever opened the document was told the code, so it is as strong as the way the sender passed it on. A one-time code by email. Shows that the person could read the mailbox at the moment they opened the document. The code goes to the same mailbox as the link, so it proves little more than the link does: it mainly stops a link that was forwarded or left open on another device. A one-time code by text message. Shows that the person held the phone with the number the sender typed, at the moment they opened the document. That is a second thing besides the mailbox, so it proves more than a code by email, but it is only as right as the number the sender typed and does not show who was holding the phone. None of these looks at a passport or an identity card, and none makes a signature "advanced" or "qualified" in the legal sense. The certificate of completion says for every signer which check was passed, to which masked address or number the code went and when, and says "Link sent by email only" when there was none, or "Link shared by the sender only" for someone whose link the sender passed on themselves.
- A link the sender passed on themselves.A sender can put someone on a document with a name and no email address, and send them the link by WhatsApp, text message or chat. We never write to that person. The certificate says "Link shared by the sender" for them, which shows less than our email does: not how the link travelled, and not who opened it.
Keeping scams out
E-signature services get abused to send fake invoices. These checks are made where a sender starts something that emails a person (a first send, a correction to a document that is out, a reminder, reopening, a bulk send, a public form, a team invitation) and again where the email to the next person in a signing order is written.
- Senders confirm their email address first.An account cannot send anything or invite anyone until its address is confirmed. The link in the confirmation email works in the browser that signed up. Anywhere else it asks for the password of the login, so the owner of a mailbox cannot confirm a login that someone else made in their name by clicking a link out of habit.
- New accounts have a daily limit.An account that has not paid for anything can send to 50 people a day in its first week and to 200 a day after that. Everyone a sender newly emails counts, however they are reached. A public form has the same limit of its own, counted for that form alone, so strangers filling in a form never use up what its owner may send. A team can invite 20 people a day. Paying does not lift the limit at once: it goes when a payment is 14 days old and was not refunded or disputed. A person on our team can lift it sooner.
- Fake payment notices are stopped.Until that same day an account cannot send something that reads like a payment notice from a well-known brand with a phone number to call, and cannot send or invite under a name that reads like such a brand. We read what the emails print: the subject, the message, notes to recipients, document names, what the sender wrote on the pages, the reason for voiding, the names the email goes out under and the name of a public form, which its page shows to anyone with the link, also when a brand is glued to another word or spelled with look-alike letters. It is a filter for the common trick, not a guarantee: a scam worded another way passes it, which is what reports are for. A refusal says which words set it off, and a person can clear a genuine sender.
- Every request can be reported.Each signing email has a report link that needs only its security code, and the signing page has one too. The code still works for a report after the sender has deleted the document. Reports go to a person.
- Enough reports pause the sender.When 3 different recipients report one account, it is paused until a person has reviewed it. Nothing its senders start is emailed to anyone meanwhile: no new documents, no new or changed recipients, no reminders, no reopening, no invitations and no email about a change, and people further down a signing order are asked only once the pause is lifted. What recipients do themselves still works and is confirmed to them: people who already have a document can sign it, decline it and get their copy. The account keeps access to its own documents. A report from a visitor of a public form reaches a person but does not count towards the pause, because a form takes whatever name and address is typed into it.
- We never ask for money or passwords by email.Not for a password, not for a card number, not for a payment. An email that does is not from us. Report it.
Proof you can check
- What the audit trail records, and what it does not.Written down, with the time in UTC and the internet address it came from (the browser is kept beside it): sending; what became of each email to a person at the mail server; the first time each person opens the document, and later visits at most once a day for each person; agreeing to sign electronically, with the wording; signing, approving and declining; corrections, reminders, reassignments, questions, reports and disputes; the completed copy handed to the mail server for each person, and the first time each person opens or downloads it. Not written down: whether an email was opened in the mailbox, how long someone looked at a page, more than one later visit a day, how a signature was made (typed, drawn or uploaded), and anything done with a copy after it was downloaded. The certificate is sealed when everyone has finished, so what happens after that is in the envelope's live audit trail, not in the PDF.
- The audit trail is hash chained, and what that does not stop.Each line of the audit trail carries a SHA-256 fingerprint made from the line itself and the fingerprint of the line before it. Changing or removing a past line without recomputing every line after it breaks the chain, and the app then shows that the record was altered. The chain has no secret key and is kept in the same database as the lines. So whoever can write to that database, the people who run the server or someone who broke into it, could change a line and recompute the rest, and the app would still show the record as intact. What would show such a rewrite is the chain head printed on the certificate of the completed PDF that each person was emailed: the stored trail must still lead to that same value. The browser description stored with a line is not part of its fingerprint.
- Completed documents come with a certificate.A document everyone has finished includes a certificate of completion with the full audit trail. A voided, declined or expired one has none, and its copies say so on the first page and across every page. On the certificate, read the names, times and places for what they are. A name is the one the sender typed, attached to whoever used that person's link, which can be the sender. Times are in UTC. An internet address is a connection, not a place: many people can share one, and it can be the sender's own. How to read a Sign&Grow certificate goes through every line. For every signer it says how they were checked before the document opened: a one-time code with the masked address or number it went to and the time it was typed in, an access code, or “Link sent by email only” when there was no check, so nobody reads more into it than happened.
- Anyone can verify a signed PDF.Drop the file on Verify a document. We compare its SHA-256 fingerprint with the one recorded when signing finished. One changed byte and it no longer matches. A match shows that the file is unchanged since then, not who was behind each signature. No account is needed, and the file is not kept. When a sender deletes their account, the fingerprint of each completed document is kept for one more year with its envelope ID and its day, so the check can still say that the file was completed here and has been deleted since. A printed copy can be looked up by the envelope ID at the foot of each page.
Your documents stay yours
- Export everything, free, at any time.One ZIP file with every signed PDF, every audit trail and a list of all envelopes. It is free on every plan and keeps working after you cancel.
- Stopping payment never costs you your documents.Cancelling, a failed payment or moving to the free plan deletes nothing and locks nothing. A paused account can still open, download and export everything.
- Closing an account can be undone for 30 days.Nothing is deleted during that time, and signing in again brings the account straight back. While it is closing nothing new starts in it: nothing is sent, nobody joins, and its API keys are off. 7 days before the end the owner is emailed the date, how to keep the account and how to export everything first.
- Deleted means deleted.When an account is deleted, 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.
- What stays after a deletion, 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.
- A team does not lose documents when someone leaves.What they sent (envelopes, drafts, templates and bulk sends) passes to a member an admin chooses, each envelope's audit trail says who handed it to whom, and the owner can hand the account to someone else. The person who was removed keeps their login and gets a workspace of their own.
- Templates are shared, not up for grabs.Everyone on a team can use a template unless it is set to admins only or to chosen members, and then nobody else sees it at all. Only the person it belongs to and the admins can change it, unless they let chosen members or the team change it as well, and only they can delete it or change who may. A template can lock its wording, so whoever may not change it can fill in names and addresses but cannot send an altered version. Members see their own envelopes, folders and bulk sends, and admins see all of them.
- A signing link opens the document for whoever holds it.So do the sender's login and the logins of the owner and admins of the sender's account. The whole list, with what the people who run this server can see, is under Who can see your documents. A recipient cannot open a document before their turn. On a public form, typing someone else's email address never opens their document: an unfinished one is only given back to the browser that started it.
- A QR code is the link.The app can show a signing link or the link of a public form as a QR code. The code is drawn in your browser from the link, by our own code: the link is not sent to another service to be turned into a picture. Whoever scans the code, or a photo of it, holds the link. A code for one person's signing link is taken off the screen again after 2 minutes. A code can do no more than its link: once an address is corrected the old code no longer opens the document, a voided envelope cannot be signed from it, and the code of a paused or deleted form opens a page that says the form is not available.
Who can see your documents
In one list, so nobody has to guess. A signing link is the key to its document: read the first line before you forward one.
- The people it was sent to, and anyone they pass their link to.A signing link opens the document for whoever holds it. There is no login behind it, so forwarding the email, or sharing an inbox, shares the document. That is why a sender can put an access code on a document, which they give to the signer themselves and which is never in our email, or ask for a one-time code that is sent to the signer when they open the link. A recipient cannot open a document before their turn in a signing order. After it has been voided, declined or left to expire, only someone who already signed can still open the copy of what they signed.
- The person who sent it.They see the document, what each person filled in, the signatures, the audit trail, and whether each email left and each person opened it.
- The owner and the admins of the sender's account.On a team, the owner and every admin can open every envelope, template and bulk send of every member. A member sees only what they sent themselves, and every template. If you send from a team, its admins can read what you send.
- The people who run this server.Inside the app they work a queue of help requests and reports. There they see what somebody wrote to them. For a reported document they see its subject, the sender's message, the sender's name and address and who reported it. For an account they see its name, its age, its plan and whether it renews or ends and when, a free code it uses, its last payment, a card dispute, how many signatures it has left, the names and addresses of its owner and admins, and whether it is paused or marked as trusted. The queue has no screen and no function that opens a document, a signed PDF, a signature, an answer typed into a field or an audit trail. Outside the app it is different: the software adds no encryption of its own to the database, and the key to the stored files, where it encrypts them, is in the server's settings, so whoever has the disk, the database and the settings of the server can read everything on them. The rule for that is: only to answer a help request or a report about that document, or to repair the service, and never for anything else. That rule is a promise by the people who run the server. Software cannot enforce it.
- The companies that carry it.The host of the server, and the mail provider that delivers the emails with the signed PDF attached. Who they are on this server is listed under "Where your data is" on this page.
- Nobody else.These pages load no advertising and no tracking of any kind. No document, contact, name or address is sold or handed to an advertiser, a data broker, a parent company or a partner. Nothing you upload or sign is sent to an AI service or used to train one. The first and the last of these you can check in the code. That nothing is sold is a promise by the people who run this server.
Privacy and AI
- Your documents are not sent to any AI system.Nothing you upload or sign is passed to an AI service, and nothing is used to train one.
- Search stays inside your account.The text of PDFs you upload is indexed so you can search your own envelopes. Files that signers attach are not indexed.
- A file you verify is not stored.The verify page works out the fingerprint of the file and discards it. In the result, signers' email addresses are partly hidden.
Where your data is
This block is filled in from the settings this server runs on. What its operator has not stated is said as exactly that, not left out.
- Who runs this server.The operator of this server has not said who they are. Ask them. They are the ones who hold your data, and the ones to ask about it.
- Where the server and its files are.Frankfurt, Germany. It runs on machines of Render. The database and every uploaded and signed file are on one disk in that one place. There is one region. You cannot choose another.
- Backups.The operator of this server has not said whether and where backups are kept. Ask them.
- What leaves the server.Only what the table below lists, for the reason it gives: on this server that is the hosting alone. A webhook you set up yourself sends the events you chose to the address you gave. There is no analytics service, no advertising and no AI service behind these pages.
| 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.
- A summary you can keep, and what a signed agreement would be.The data processing summary says what is processed, for whom, for how long and how it is deleted, on one page you can save as a PDF. It is a description, not a contract. If you need a signed data processing agreement, it is between you and whoever runs this server. The software cannot sign one for them.
Accounts and access
- Passwords are never stored as written.Only a salted scrypt hash is kept. Password reset links work once and for one hour.
- API keys and login sessions are stored as fingerprints.An API key is shown once, when you create it. After that we only hold its hash.
- A browser stays signed in while you use it, and you can see where you are signed in.A browser is signed out 30 days after you last used Sign&Grow in it, and every visit starts the 30 days again. So a phone you use at least once a month does not ask you to sign in again, and a browser nobody uses is signed out by itself. Signing in on another device signs nothing out. Under Settings, Profile you see every browser that is signed in, with the device and browser it said it was and when it was last used, and you can sign out one of them or all the others at once. Changing your password also signs out every other browser.
- Signing in person locks the host's account on that device.When the signing page opens for someone who signs in person, Sign&Grow locks your account in that browser. To come back you type your password, or sign in again if your login has none. After 5 wrong passwords that browser is signed out. The signer's last screen asks them to hand the device back. The lock covers Sign&Grow in that one browser, and nothing else. What the person holding the device could still reach: (1) Everything else on the device: your email (signing links and password reset emails arrive there), other apps, other websites. (2) A password that your browser or password manager has saved and offers to fill in on the lock screen. (3) A Google or Microsoft account that is signed in on the device, if that is how you sign in to Sign&Grow. Signing in again is then one tap. (4) A page of your account that is open in another tab stays on screen until that tab is brought to the front. Then it locks too. If that is too much for the person in front of you, send them the document by email and let them sign on a device of their own.
- A help request opens with its own link, and only that request.Our emails about a help request carry a private link that opens that one request without a login, so someone who is locked out can still read the answer and reply. The request itself keeps only a fingerprint of the secret in the link. Our own copies of the emails about it hold the link, like every email we keep, and are deleted after 90 days or with the request. Anyone can type any address into the help form, so what was typed is not mailed back or shown on that page until it is known to come from the owner of the address or a person on our team has read it and written back, and someone who is not signed in under an address can only send a few requests to it a day. No API key can write, read or answer help requests.
- Two-step login with an authenticator app, if you switch it on.After your password you type the 6-digit code your phone shows (the standard time-based codes every authenticator app makes). A code works once. A wrong password is answered with the same second screen as a right one, so nobody can find out a password by trying it here. 5 wrong codes in a row pause the second step of that login for 15 minutes and email its owner. "Remember this device" skips it in one browser for 30 days, and you can withdraw that under Settings. 10 recovery codes are shown once and stored only as fingerprints. Without phone and codes, an admin of your team can switch it off (you are emailed, and it is recorded who did it), and an owner can reset it by email, which takes effect after 3 days with an email every day and stops when you sign in with a code. An owner can require it for everyone on a team. Changing your password, your email address or the second step itself asks for a code. API keys are not affected: a program that uses one is never asked for a code. Treat a key like a password, and revoke it under Settings, API and webhooks if it may have leaked. The secret your app shares with us is kept in the database as it is, because the server must read it to check a code, so the same goes for it as for the rest of the database.
- Guessing is slowed down.Sign-in attempts, access codes, security codes and the public forms on this site are rate limited. An access code is frozen after 10 wrong tries. A one-time code stops working after 5 wrong tries, a new one can be asked for once a minute and 5 times an hour, and the code itself is never stored, only a keyed fingerprint of it.
- Webhooks are signed.Every delivery carries an HMAC-SHA256 signature you can verify, and webhook addresses that point into a private network are refused.
- Our pages cannot be framed by another site.That stops a look-alike site from wrapping the real signing screen.
What this is not
Being straight about the limits, so you can decide whether this fits.
- Not certificate-based digital signatures.A signed PDF is not sealed with a cryptographic certificate inside the file. Its integrity rests on the recorded fingerprint, the audit trail and the verify page.
- Not advanced or qualified signatures.These are standard electronic signatures with an audit trail. If a law or the other party requires an advanced or a qualified signature, use a service that provides those. For high-stakes documents, ask a lawyer whether a standard electronic signature fits your case and country. What we know about signing outside the United States, and which documents not to sign here.
- Not translated yet.The signing screen and our emails are in English for now. Your document can be in any language. That includes the text every signer agrees to before signing, and the certificate.
- No check of identity documents.We do not look at a passport, an identity card or a face. A signer is known by access to their email inbox, plus an access code or a one-time code by email if the sender asks for one. What each of those proves is said under For people who sign.
- No single sign-on.Accounts are protected by a password, and by our own two-step login when it is switched on. There is no SAML or other sign-in through an organization's own system.
- No text-message codes or security keys for signing in.The second step of our two-step login is an authenticator app only. Codes by text message to sign in, passkeys and hardware keys are not built.
- Not for patient information.There is no HIPAA business associate agreement (BAA) for Sign&Grow. Nobody can sign one with us, on any plan, at any price. HIPAA is the United States law on health information, and it asks a healthcare provider to have such an agreement with every service that handles patient information for them. So if you are a healthcare provider in the United States, or work for one, do not put protected health information through Sign&Grow: no patient intake forms, no consent forms that name a patient or a treatment, nothing else that says who a patient is together with anything about their health, their care or their bills. What would have to be true first: (1) A business associate agreement written by a lawyer, signed by whoever runs this service. (2) The same kind of agreement between them and every company that handles the data for them: the host of the server, and the mail provider that carries the emails and the signed PDFs attached to them. (3) The database encrypted by the software itself, not only the stored files. Today the software can encrypt the files, when the people who run the server switch that on, and it never encrypts the database. (4) A record of who opened which document, and a written way of telling you about a breach. None of that exists today, and this page will say so on the day it does. Rules about health information differ by country and by kind of document: outside the United States too, check what applies to you before you send anything about a person's health.
- No payment collection.Sign&Grow never takes money for a sender. An account that has earned trust can show a link to its own payment page after a person presses Finish, with its name and the full address, and never in an email. We do not see that payment, cannot confirm it and cannot refund it.
- No security certification.We have not been audited against a security standard, and we will not hint that we have.
- Stored files and the database are not encrypted by the software on this server.The software can encrypt the uploaded documents, signed PDFs and the files signers attach, and the people who run this server have not switched that on, so those files are on the disk as they were uploaded and signed. The names and email addresses of everyone on a document, what they typed into its fields, their signatures as pictures and every audit trail are kept in the database, and the software does not encrypt it. Whoever has a copy of the disk can read all of that unless the disk itself is encrypted, which depends on where the service is hosted.
Found a security problem, or something on this page that is not true? Tell us. A person reads every message.