Where your PDF goes, who holds the key, and what proof you get.
This page is written from what the code does, limits included. Without an account the file never leaves your browser. With one, it is encrypted in your browser before it is saved.
EMPLOYMENT CONTRACT
Between the Employer and the Employee named in Schedule 1.
1. Position. The Employee joins as Senior Designer, full time, from the first day of next month.
2. Salary. 4,200 per month, paid on the last working day, reviewed every twelve months.
3. Probation. Three months. Notice during probation: one week.
4. Confidentiality. Everything learned about clients and projects stays private, during and after employment.
5. Notice. One month on either side after probation.
6. Hours. 37.5 a week, Monday to Friday, with flexible start and finish times agreed with the team.
7. Leave. 25 working days a year, plus public holidays.
The two paths of a file.
Which one your PDF takes depends on one thing: whether you are signed in.
Without an account
- You open itpdf.js reads the PDF in this tab, up to 50 MB.
- You sign itpdf-lib writes your signature into the PDF, in your browser. Nothing is sent.
- You pay on StripeWhile the payment page is open, the file waits in this browser's storage (IndexedDB).
- It downloads hereBack on SignQuick, the payment is checked and the file downloads from your browser. SignQuick never receives it.
With an account
- Signed in your browserWith a paid plan, a verification seal is added to the last page.
- FingerprintedYour browser computes the SHA-256 of the signed file; that fingerprint is kept so the file can be checked later.
- Encrypted, then savedAES-256-GCM, with your account's key, before the file leaves the browser.
Who holds the key.
It depends on how you sign in, and it changes who could read a stored file.
| How you sign in | How your key is protected | Who can decrypt a stored file |
|---|---|---|
| Email and password | Wrapped, in your browser, with a key derived from your password (PBKDF2, 100,000 iterations). The server keeps only the wrapped key. | You |
| Google sign-in | Generated on the server and stored encrypted with a server secret. The same goes for any account without a password-wrapped key. | You, and SignQuick's server |
| No account | No key: nothing is stored. | Nobody; the file never left your browser |
If you want to be the only one able to decrypt your files, sign up with an email and a password.
Who holds a signing link's key.
When you send a document, your browser encrypts it with a key made for that request. By default, SignQuick keeps that key, sealed with a server secret, until the request is signed, declined, canceled or expired, so it can email each signer their link, remind them and tell the next one it is their turn; then the key is deleted. In private mode, the key goes only into each signer's link, after the #. Browsers never send that part of an address to a server, so SignQuick's server never sees the key, and you send each link yourself.
signquick.app/sign/token#k=key&u=…&v=…
In private mode, the part in blue stays in the browsers of the people you send it to.
Without its key, a stored file is only bytes.
The proof you get.
On Pro and Business. A $2.99 download carries your signature and nothing else.
- The verification sealA band at the bottom of the last page of a PDF you sign yourself: “Verified by SignQuick”, the document's ID, and a QR code that opens its check page.
- The fingerprintThe SHA-256 of the signed file, computed in your browser and kept, so the file can be checked later.
- The audit certificateA PDF with the file's name, its SHA-256, and each signature or refusal: the email, the IP address and the time. Download it from your documents.
- Checking a documentScan the seal's QR code, or drop the PDF on the check page: your browser computes its SHA-256 and only that fingerprint is sent, never the file.
Try the fingerprint on any file.
Drop a file here. Its SHA-256 is computed in this tab, the way the check page does it, and nothing is sent anywhere. Change one byte of the file and the whole fingerprint changes.
What the seal covers: PDFs you sign yourself, in the signer, with a paid plan. A document sent to several signers gets no seal and can't be found by the check page, and its certificate lists signatures and refusals, not when it was sent or opened.
What SignQuick keeps, and for how long.
- Signed documentsThey stay in your account until you delete them.
- Unsigned draftsDeleted after 7 days without a plan, 30 on Pro, 90 on Business. A document in a signing request that hasn't been canceled or expired is never removed.
- Without an accountNothing on our side: the file stays in your browser. This browser keeps your signature and where you placed it, as a draft, until you download or start over.
- Your accountYou can delete it from Settings.
Legal standing, without the gloss.
This is not legal advice.
- What SignQuick makesA simple electronic signature (SES). Under the EU's eIDAS regulation (article 25), it can't be denied legal effect or refused as evidence because it is electronic. In France, article 1367 of the Civil Code recognizes electronic signatures. In the United States, the ESIGN Act and UETA (adopted by 49 states and DC; New York has its own law) give it legal effect for most transactions.
- Advanced (AdES)Uniquely linked to the signer and able to identify them (eIDAS article 26). SignQuick doesn't make these.
- Qualified (QES)The only level eIDAS treats as equal to a handwritten signature, with a qualified certificate. SignQuick doesn't make these.
- In courtAn electronic signature can't be refused as evidence because it is electronic. On Pro and Business, the audit certificate records who signed, when and from which IP address; how much weight it carries is up to the court.
- The usual exceptionsWills, some family-law documents, court orders, notarial deeds and some public forms need more than an electronic signature.
Where it runs, and who else is involved.
Stripe and Amazon SES never receive your documents. The server and the file storage only receive them encrypted.
| Service | What for | Where |
|---|---|---|
| Hetzner | The server (a VPS) that runs the app. | Germany (EU) |
| Vercel Blob | Stores the files saved to accounts, encrypted in the browser before they are sent. | Vercel's storage |
| Stripe | Card payments. | United States |
| Amazon SES | Emails: sign-in, notifications, signing invitations and reminders. | Ireland (EU) |
The full list is with the subprocessors.
The limits, plainly.
- Not end-to-end for every accountWith Google sign-in, our server holds your key, encrypted.
- Simple signatures onlyIf a law or the other party requires an advanced or qualified signature, use a qualified trust service provider.
- Proof needs a planThe seal and the audit certificate come with Pro and Business.
- Payments leave the EUStripe processes them in the United States. Your documents are not sent to it.
Found something wrong? Security reports go to [email protected].
Without an account, your PDF stays in your browser from start to finish.