Data Processing Agreement
The processor agreement under Article 28 of the GDPR for organisations that use Sealsimple: what we do with the personal data in your documents, and what we promise in return.
1. About this agreement
This Data Processing Agreement (DPA) is between Sealsimple ("we") and the organisation that uses Sealsimple ("you"). It adds to our Terms of Service and covers the personal data we process for you while we provide Sealsimple, as Article 28 of the GDPR requires.
The DPA applies as soon as you use Sealsimple for your organisation. An owner of your workspace can also accept it in Sealsimple, under Settings, to keep a dated record. If this DPA and the Terms of Service disagree about personal data, this DPA applies.
2. Roles
You decide why and how the personal data in your documents is processed, so you're the controller. We process it on your behalf, so we're your processor. If you use Sealsimple for your own clients, you may be their processor; then we're your sub-processor, and this DPA applies in the same way.
For the data we need to run our own business, such as your account, billing, support and security logs, we're the controller. Our Privacy Policy covers that data.
3. Subject, nature, purpose and duration
- Subject: providing Sealsimple, an online service to prepare documents, send them for electronic signature, collect signatures, seal the signed PDF and keep an audit trail.
- Nature: storing, showing, converting, emailing and sealing documents, sending reminders and logging what happens to each document. Only when you use the AI add-on: having an AI model review a document, answer questions about it or turn a spoken question into text.
- Purpose: providing Sealsimple to you, supporting you and keeping the service secure. Nothing else.
- Duration: as long as you use Sealsimple, and after that until the data is deleted as described in section 13.
4. People whose data we process
Depending on how you use Sealsimple:
- you and your colleagues who use Sealsimple;
- the people you send documents to, whether they sign or get a copy, and anyone they pass signing on to;
- the contacts you save in Sealsimple;
- anyone whose details are in the documents you upload, such as employees, clients, tenants or suppliers.
5. Types of personal data
Which data depends on what you put into Sealsimple. Usually:
- contact details: names, email addresses and, if you add them, company, job title, phone number and address;
- document content: everything in the documents you upload and in the fields people fill in, such as addresses, dates of birth, salaries or bank details;
- signatures and initials, drawn, typed or uploaded;
- the audit trail: what happened to each document and when, with IP address, browser details, approximate country and how the signer's email address was checked;
- emails: the subject and message you send with a document, and whether it was delivered;
- only with the AI add-on: the document text sent for a review, questions asked in the document chat and recordings of spoken questions.
Sealsimple isn't designed for special categories of data, such as health data, or for national identification numbers. If your documents contain them, make sure you're allowed to process them, and ask only for what you need.
6. Your instructions
We process personal data only on your documented instructions. Your instructions are this DPA, the Terms of Service and what you do in Sealsimple, such as uploading, sending or deleting a document. This includes transfers outside the EU (section 15).
We never use your data for our own purposes: we don't sell it, don't use it for marketing and don't let it be used to train AI models. If EU or national law requires us to process it in another way, we tell you first, unless that law forbids it. If we think one of your instructions breaks data-protection law, we tell you straight away.
7. Confidentiality
Only people who need access for their work get it, and they're bound to confidentiality by contract or by law. We don't open your documents unless you ask us to, for example for support, or unless we must to keep the service secure or to obey the law.
8. Security
We protect personal data with appropriate technical and organisational measures, as Article 32 of the GDPR requires. Annex 1 summarises them, and our Security page explains more. We may change these measures as technology moves on, but never in a way that lowers the overall protection.
9. Sub-processors
You give us general permission to use sub-processors. Annex 2 lists them, with what each one does, which data it gets and where. The same list is on our Privacy Policy page.
Before we add or replace a sub-processor, we email the owners of your workspace at least 14 days in advance. If we must change sooner, for example because a provider stops its service, we tell you as soon as we can. You can object on reasonable data-protection grounds within that time. If we can't resolve your objection, you may stop using the part of the service concerned, and we refund what you paid in advance for the time after that.
Each sub-processor that processes your data for us is bound by a contract with data-protection obligations at least as strict as this DPA, and we remain responsible to you for its work. The service under Loaded by the browser never receives document content: it only counts visits, as Annex 2 describes.
10. Help with people's requests
People can ask to see, correct, delete or receive their data, or object to its use. You can handle most of these requests yourself in Sealsimple: look up a document or contact, download it, correct a contact or delete a draft. If a request reaches us, we pass it on to you without undue delay and don't answer it ourselves unless you ask us to. Where you can't handle a request yourself, we help you, within reason.
11. Help with security, impact assessments and authorities
We help you meet your obligations under Articles 32 to 36 of the GDPR, as far as our role and the information we have allow. For example, we give you the information you need for a data protection impact assessment (DPIA) or for a consultation with a supervisory authority.
12. Personal data breaches
If we become aware of a personal data breach affecting your data, we notify the owners of your workspace without undue delay, and at the latest within 48 hours. We tell you what happened, which data and people are affected as far as we know, the likely consequences, what we've done about it and who you can contact. When we learn more, we update you.
We take steps to limit the damage, and we record every breach. As the controller, you decide whether to report the breach to the supervisory authority or to the people affected. We help you do that.
13. Deleting or returning data
You decide how long documents are kept. You can download signed documents with their certificate at any time, and delete drafts and cancelled documents yourself. Completed documents stay available as evidence until you ask us to delete them or close your account.
When you close your account, we delete straight away the workspaces only you are in, with their documents, files, templates and contacts. In a workspace you share with colleagues, the documents belong to your organisation and stay with your colleagues. If our agreement ends in another way, you have 30 days to download your data before we delete it. Copies in backups disappear when those backups expire in the normal backup cycle. We keep data longer only where EU or national law requires it.
Would you rather have us return your data than download it yourself? Tell us before you close your account.
14. Information and audits
We keep a record of the processing we do for you, as Article 30(2) of the GDPR requires. We give you the information you need to show that we keep to this DPA and to Article 28 of the GDPR: this DPA, our security measures, the sub-processor list and, where available, our sub-processors' certifications and audit reports.
If that isn't enough, you, or an independent auditor bound to confidentiality, may audit us once a year with at least 30 days' notice, during business hours and without disrupting the service or seeing other customers' data. Each side bears its own costs. These limits don't apply when a supervisory authority requires an audit, or after a personal data breach.
15. Transfers outside the EU
Sealsimple's database and files are stored in the European Union. Some sub-processors are based in, or can reach data from, countries outside the European Economic Area, mainly the United States; Annex 2 shows where. We allow this only when the transfer is protected: by an adequacy decision of the European Commission, such as the EU-US Data Privacy Framework for certified companies, or by the EU Standard Contractual Clauses, with extra safeguards such as encryption where needed. Ask us and we'll tell you which safeguard applies to which sub-processor.
16. Liability
The limitations of liability in our Terms of Service also apply to this DPA, as far as the law allows. They don't limit the rights of the people whose data is processed.
17. Duration, changes and law
This DPA applies for as long as we process personal data for you. Obligations that by their nature continue afterwards, such as confidentiality and deletion, stay in force.
We may update this DPA when the law, our service or our sub-processors change. We never lower the protection of your data, and we announce important changes at least 30 days before they take effect, by email to the owners of your workspace.
This DPA is governed by Dutch law. Disputes go to the court named in our Terms of Service.
18. Contact
Questions about this DPA, a data subject request or a security concern: email privacy@sealsimple.com. Report a suspected personal data breach there too: we respond without undue delay.
Annex 1: Security measures
A summary of the technical and organisational measures we take under Article 32 of the GDPR.
- Encryption: all connections use HTTPS (TLS). The database and stored files, including documents and signatures, are encrypted at rest.
- Access control: the database's row-level security lets people see only the documents of their own workspace. Document files are private and only reachable through signed links that expire.
- Signers: every signer gets a personal link. With email verification on (the default), a link that was copied or forwarded asks for a code sent to the signer's email address.
- Proof of integrity: every event on a document is logged with time, IP address and browser, and chained with SHA-256 hashes, so a later change would show. The signed PDF gets a SHA-256 fingerprint and a certificate of completion.
- Accounts: passwords are stored only as salted hashes, and sign-in sessions use short-lived tokens.
- Separation: each workspace's data is kept apart by the database's access rules.
- Availability: Sealsimple runs on managed cloud platforms with automated backups and monitoring.
- People: only those who need access for their work get it, and they're bound to confidentiality.
- AI add-on: AI features run only when someone in your workspace starts them, and only the document concerned is sent.
- Sub-processors: chosen with care and bound by contract (Annex 2).
- Incidents: personal data breaches are handled and recorded as described in section 12.
Annex 2: Sub-processors
The providers we use, what they do, which data they get and where. The same list is on our Privacy Policy page, and we update both when something changes.
Running Sealsimple
Lovable
Lovable Labs, Sweden and USA- What for
- The platform Sealsimple is built and hosted on. It runs our backend (Lovable Cloud) and passes payment requests on to Stripe.
- Data
- Everything in Sealsimple: accounts, documents, signatures, recipients, contacts and audit trails, plus visitors' IP addresses and browser details.
- Where
- EU for stored data; USA
Supabase
Part of Lovable Cloud- What for
- Database, sign-in and file storage.
- Data
- Accounts, documents and signed PDFs, signatures, recipients, contacts, audit trails and settings.
- Where
- EU (storage region)
Cloudflare
Cloudflare, Inc., USA- What for
- Network and hosting: every page and request passes through Cloudflare, which also protects the service against attacks.
- Data
- IP addresses, browser details and everything sent to and from Sealsimple as it passes through, including documents.
- Where
- Worldwide, in the data centre nearest to the visitor
Resend
Plus Five Five, Inc., USA- What for
- Sends our emails: invitations to sign, reminders, verification codes, completed documents and account emails. Also receives the email sent to our support address.
- Data
- Names and email addresses, the content of the emails and the signed PDFs attached to them. The emails people send to our support address.
- Where
- EU sending region (Ireland); USA
AI: the add-on (only when someone uses AI review or the document chat), the support chat, and support messages (draft replies and automatic sorting)
Lovable AI Gateway
Lovable Labs, Sweden and USA- What for
- Passes AI requests on to the model providers below and returns their answers.
- Data
- The document being reviewed, questions asked in the document chat and recordings of spoken questions. With the AI review add-on: short texts from a draft for automatic field placement (see Google Gemini). Support conversations we have a reply drafted for, every message to our support for automatic sorting, and messages in the support chat.
- Where
- USA
Google Gemini
Google- What for
- The AI model behind AI review, the document chat and the support chat's assistant. With the AI review add-on, it also matches the signature blocks of a draft to its signers when fields are placed automatically. Also drafts our replies to support messages, which we read before anything is sent, and sorts support messages automatically (type, product area, grouping of similar reports) so we can find and fix problems; the sorting makes no decisions about anyone.
- Data
- The document's file and text, the review and the chat questions. For automatic field placement: the signers' names and signing order, the email domain of signers with a company address, up to 300 characters of text around each signature block (at most 60 blocks) with its page and position, and up to 1,200 characters from the start of the contract where the parties are introduced. Email addresses, IBANs and numbers of 5 or more digits are removed first, and the file itself is never sent. For a draft reply: the support conversation, with the sender's name and email address. For sorting: the support message's subject and text and the page it was sent from; we don't add the sender's name or email address. For the support chat: the visitor's messages and, if they're signed in, their first name.
- Where
- USA and other countries
OpenAI
OpenAI, USA- What for
- Turns a spoken question in the document chat into text.
- Data
- The voice recording.
- Where
- USA
Sign-in, payments and support
Stripe
Stripe Payments Europe, Ltd., Ireland- What for
- Payments, subscriptions and invoices for paid plans.
- Data
- The account holder's name, email address, billing details and payment method. We never see full card numbers. No document content.
- Where
- EU and USA
Google sign-in
Google- What for
- Signing in with a Google account, only if you choose to.
- Data
- Your name, email address and the fact that you sign in to Sealsimple.
- Where
- USA and other countries
Gmail
Google- What for
- Our support mailbox: messages sent with our contact form arrive here.
- Data
- The name, email address, message and country of the person writing to us.
- Where
- USA and other countries
Migadu
Migadu-Mail GmbH, Switzerland- What for
- Hosts our @sealsimple.com mailboxes: email to support@sealsimple.com and our other addresses arrives here first.
- Data
- The name, email address and message of the person writing to us, and any attachments.
- Where
- France (EU)
Loaded by the browser
Visitor statistics
Lovable Labs, using Tinybird Inc., USA- What for
- Counts visits to Sealsimple's pages for our hosting platform's statistics: no profiles and no tracking across sites.
- Data
- The page visited, the referring site, browser and device type, language, country (from the time zone) and a random session number kept in a cookie for 30 minutes. No document content.
- Where
- EU and USA
Never receives document content. Fonts and the PDF viewer come from Sealsimple itself, so no other service sees who opens a page.
Questions? Email legal@sealsimple.com.