Skip to content

Legal

Data processing agreement (DPA)

The commitments of VoilaDocs as processor of your CRM data and templates, under article 28 of the GDPR.

Last updated: November 11, 2026

1. Purpose, parties and scope

This agreement is part of the contract between the customer (the “Customer”, controller) and [To be completed] (the “Provider”, processor), made up of the terms of service and, for paid plans, the terms of sale. It applies to every plan, the free plan included, as soon as these terms are accepted, with no separate signature.

It sets the conditions under which the Provider processes personal data on behalf of the Customer, in accordance with article 28 of Regulation (EU) 2016/679 (GDPR). If it conflicts with other contractual documents on data protection, this agreement prevails.

Processing for which the Provider is itself the controller (user accounts, billing, support, security of the service) is described in the privacy policy and is outside the scope of this agreement.

2. Definitions

The terms “personal data”, “processing”, “controller”, “processor”, “data subject” and “personal data breach” have the meaning given in article 4 of the GDPR. “Customer Data” means the personal data from the Customer’s HubSpot CRM, or provided by the Customer (in particular in its templates), that the Provider processes to deliver the service.

3. Subject matter, duration, nature and purpose

The subject matter of the processing is generating documents from the Customer’s templates and HubSpot CRM data. It lasts for the whole term of the contract, then until Customer Data is deleted under article 14. Its nature and purpose, the categories of data and data subjects and the retention periods are described in annex 1.

4. Customer instructions

The Provider processes Customer Data only on the Customer’s documented instructions, including for transfers outside the European Union. These instructions are: the contract, this agreement, and the settings made by the Customer in the service (templates, mappings, automation rules, workflow actions, emails sent).

If Union or member state law requires the Provider to carry out processing not covered by these instructions, it informs the Customer before processing, unless that law prohibits it on important grounds of public interest.

The Provider immediately informs the Customer if it considers that an instruction infringes the GDPR or another applicable provision. It does not process Customer Data for its own purposes.

5. Confidentiality

The Provider keeps Customer Data confidential. Only people who need it to deliver the service, provide support at the Customer’s request or fix an incident have access, and each of them is bound by a contractual or statutory duty of confidentiality.

6. Security

The Provider implements the technical and organizational measures required by article 32 of the GDPR, described in annex 2. It adapts them as risks and the state of the art evolve, without lowering the overall level of protection during the contract.

7. Sub-processors

The Customer gives the Provider a general authorization to use the sub-processors listed in annex 3 and on the Subprocessors page.

The Provider informs the Customer’s admins by email, and updates that page, at least 30 days before any addition or replacement. The Customer may object in writing, on legitimate data protection grounds, within that period. If no solution is found, the Customer may terminate the service without penalty, with a refund of the unused prepaid amount.

The Provider imposes on each sub-processor, by contract, data protection obligations at least equivalent to those of this agreement, and remains fully liable to the Customer for their performance.

The e-signature provider planned for the upcoming signature feature is not a sub-processor today; it will be added through the procedure above before the feature is offered.

8. Transfers outside the European Union

Customer Data is processed in the European Union and the United Kingdom, as set out in annex 3. The Provider only transfers it to another third country, or allows access to it from such a country, on the basis of a European Commission adequacy decision, including the one covering the United Kingdom and the EU-US Data Privacy Framework for certified companies, or on the basis of the standard contractual clauses adopted by the European Commission, supplemented with additional measures where needed.

9. Assistance to the Customer

  • The Provider assists the Customer, through appropriate technical and organizational measures, in answering data subject requests, and forwards without delay any request received directly, without answering it unless instructed by the Customer.
  • It assists the Customer with its obligations on security, breach notification, data protection impact assessments and, where relevant, prior consultation of the supervisory authority (articles 32 to 36 GDPR), taking into account the nature of the processing and the information available to it.
  • Unless prohibited by law, it informs the Customer of any request from an authority concerning Customer Data, and only discloses the data strictly required.

10. Personal data breaches

The Provider notifies the Customer of any personal data breach affecting Customer Data without undue delay, and no later than 48 hours after becoming aware of it, by email to the Customer’s admins. The notice describes, as far as possible, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or planned and a point of contact. Information not yet available is provided as soon as possible.

The Provider documents every breach and cooperates with the Customer. As controller, the Customer is responsible for notifying the supervisory authority and, where required, the data subjects.

11. Customer obligations

  • have a legal basis for the processing it entrusts and inform data subjects;
  • not use the service to process special categories of data (article 9 GDPR) or data relating to criminal convictions, without the Provider’s prior written agreement;
  • manage its users’ access and the security of its HubSpot and Google accounts, which remain governed by its own agreements with these vendors;
  • check the content of generated documents before sharing them, and choose the recipients of emails sent from the service.

12. Records and documentation

The Provider keeps the record of categories of processing activities carried out on behalf of the Customer (article 30(2) GDPR) and makes available to the Customer the information needed to demonstrate compliance with this agreement.

13. Audits

The Provider answers the Customer’s reasonable security questionnaires. If this information is not sufficient, the Customer may have an audit carried out, at most once a year except after a confirmed breach, by an independent auditor bound by confidentiality and not a competitor of the Provider, with 30 days’ notice. The audit is at the Customer’s expense and must not disrupt the service or compromise the confidentiality of other customers’ data. Sub-processors are audited through the reports and certifications they publish.

14. End of processing: return and deletion

Before the contract ends, the Customer may request an export of the Customer Data held by the Provider (editor templates and their versions, mappings, automation rules, generation history), in a structured, commonly used format.

When the contract ends or the organization is closed, the Provider deletes Customer Data within 30 days, unless a legal retention obligation applies. Copies in database backups disappear when their retention cycle expires. The Provider confirms deletion on request.

Since generated documents are stored in the Customer’s HubSpot portal, and Google Docs templates in its Google Drive, they remain under its control after the contract ends.

15. Liability and governing law

Each party’s liability under this agreement is subject to the limits set in the terms of service, unless a mandatory rule provides otherwise. This agreement is governed by French law; disputes fall under the court designated by those terms.

Annex 1: description of the processing

Purpose
Description:Generate documents (quotes, contracts, proposals, invoices, certificates…) from the Customer’s templates and HubSpot CRM data, save them to HubSpot, trigger these generations from the application, the HubSpot card, rules or workflows, and email a document at a user’s request
Nature of operations
Description:Reading through APIs, consultation, structuring into a document, printing to PDF, transmission to HubSpot and to an email recipient, storage of templates and history, erasure
Data subjects
Description:Contacts, customers, prospects, partners and employees of the Customer in its CRM or in its templates; recipients of emails sent from the service; users of the service
Categories of data
Description:Identification and contact data, professional data, company, deal, line item and ticket data, any other HubSpot property the Customer chooses to use in its templates, and the content the Customer types into editor templates
Sensitive data
Description:None expected; the Customer undertakes not to use any without prior agreement
Frequency
Description:At each generation, each template preview on a record and each email sent; continuously for stored templates and history
Retention
Description:HubSpot record data: read at each generation and processed in memory; only the record type and ID, the file name and, for a rule, the triggering property value are kept in the history. PDFs: stored in the Customer’s HubSpot portal, never by the Provider. Editor templates, versions and history: term of the contract. Temporary Google Docs copy: deleted right after export. Job queue: only the latest jobs are kept. Technical logs: 30 days at most
Location
Description:European Union (Germany, Netherlands) and United Kingdom; for emails, the sending region shown in annex 3

Annex 2: technical and organizational measures

Encryption and secrets

  • TLS (HTTPS) encryption of traffic between the browser, our services and the HubSpot, Google, Stripe and Resend APIs; TLS-encrypted connections, with the server certificate checked, to the database and the job queue.
  • HubSpot and Google OAuth tokens encrypted with AES-256-GCM (authenticated encryption, random initialization vector for each value) before storage, with a key supplied by the runtime environment and never stored in the database.
  • Managed database encrypted at rest, with backups and point-in-time restore.

Access control

  • Sign-in with Google or Microsoft (OAuth with PKCE) or with a one-time link sent by email, valid for 15 minutes and stored hashed; HttpOnly, Secure, SameSite=Lax session cookie.
  • Owner, admin and member roles. Billing (subscription, credit packs, portal), deleting templates and automation rules, managing members and invitation links, disconnecting HubSpot and organization settings are reserved to the owner and admins.
  • Organization membership and role checked again at least every 5 minutes, so a removal or role change applies quickly.
  • Partitioning per organization: every read and write is filtered on the signed-in user’s organization. PDFs are private HubSpot files; links in the application only send signed-in members of the organization to a short-lived signed URL.
  • Provider operations console restricted to a named list of addresses; access to provider consoles restricted to authorized people, with strong authentication.

Incoming requests

  • HubSpot signature (v3) checked on every webhook, CRM card call and workflow action, with constant-time comparison and rejection of requests older than 5 minutes.
  • Connection of a HubSpot portal protected by a signed state and a single-use nonce valid for 5 minutes.
  • Stripe event signatures checked, each event processed only once.
  • Rate limiting of generations (per organization and per HubSpot portal), workflow actions and emails sent (50 per hour per organization).

PDF printing and images

  • Printing service (Gotenberg and Chromium) hosted in Amsterdam in the same project as the worker, with no public domain: only the worker can reach it, over the host’s private network. Unused features disabled (URL download, webhooks, office conversion).
  • Chromium refuses any request to a private address (loopback, private networks, link-local); rendering only keeps public web image addresses.
  • Header and footer images downloaded by the worker: HTTPS only, every address resolved and refused if it points to a private address, every redirect checked (3 at most), image type recognized from its content, download size and time limited. A refused image is left out of the document.

Minimization

  • Only the properties used by the template are read. HubSpot permissions: reading CRM objects, their schemas, owners, line items and tickets; writing files, and writing on objects only to create the notes that attach PDFs to records; workflows and custom objects optional depending on the HubSpot subscription.
  • Google Drive permission limited to the files the user picks or that the service creates.
  • Temporary Google Docs copy deleted after export, including when generation fails; PDFs not stored by the Provider; job queue limited to identifiers, the file name and the job’s log.

Logs and continuity

  • Tokens never written to logs, third-party API error responses truncated, retention of 30 days at most.
  • Generations retried automatically on temporary errors, credit given back on final failure.

Organizational measures

  • Access to Customer Data limited to what the service, support requested by the Customer and incident resolution require.
  • Confidentiality duty for every authorized person; incident procedure with notice to the Customer within 48 hours.
  • Review of sub-processors and their safeguards before any addition.

Annex 3: sub-processors

Vercel
Role:Hosting of the website and the application, server functions
Location:Functions in Frankfurt (Germany, fra1 region), global content delivery network (CDN) for public content
Data involved:All data processed by the application, in transit; technical logs
Safeguards:Provider data processing agreement, standard contractual clauses for any access from the United States
Neon
Role:PostgreSQL database
Location:Frankfurt (Germany)
Data involved:Accounts, organizations and members, templates (settings, mappings, content and versions of templates built in the editor), automation rules, generation history, encrypted OAuth tokens
Safeguards:Provider data processing agreement, encryption at rest, standard contractual clauses for any access from the United States
Railway
Role:Runs the worker that generates documents and the PDF printing service for editor templates (Gotenberg and Chromium, reachable only over the worker’s private network)
Location:Amsterdam (Netherlands, EU West region)
Data involved:HubSpot data read during generation and the document being printed, in memory only; technical logs
Safeguards:Provider data processing agreement, standard contractual clauses for any access from the United States
Upstash
Role:Redis queue for generation jobs and rate-limiting counters
Location:London (United Kingdom)
Data involved:Technical job identifiers (organization, template, HubSpot record), requested file name and the job’s run log; no record or document content. Only the latest jobs are kept for troubleshooting
Safeguards:European Commission adequacy decision for the United Kingdom, provider data processing agreement, standard contractual clauses for any access from the United States
Google
Role:Sign-in with Google; for Google Docs templates, Google Docs and Google Drive APIs called on the Google account of the user who added the template, to copy it, fill the copy and export it as a PDF
Location:As set by the customer’s Google agreement
Data involved:Google profile name, email address and picture; temporary filled copy of the template, deleted right after export
Safeguards:Google terms applicable to the customer’s account, standard contractual clauses
HubSpot
Role:The customer’s CRM: source of the data read and destination of the PDFs, saved as private files and attached to records through a note
Location:As set by the customer’s HubSpot agreement
Data involved:Record properties used by templates; generated PDFs
Safeguards:Agreement between the customer and HubSpot; revocable OAuth access
Stripe
Role:Payment of subscriptions and credit packs, invoices, billing portal
Location:European Union and United States
Data involved:Organization name, email address of the paying admin, billing data; card details are entered with Stripe and never reach us
Safeguards:Provider data processing agreement, standard contractual clauses
Resend
Role:Sending sign-in links, invitations, documents by email from the application and usage alerts to admins
Location:[To be completed]
Data involved:Recipient address, subject and body of the message, sign-in or invitation link, attached PDF
Safeguards:Provider data processing agreement, standard contractual clauses