Who processes your data
[To be completed] ([To be completed]), publisher of VoilaDocs, is the controller for processing related to accounts, billing, support and the website.
For your HubSpot CRM data and the content of your templates, your organization is the controller and we act as a processor, under the data processing agreement (DPA). If your data sits in the CRM of one of our customers, please contact that customer first.
If you sign in with Google or Microsoft, that provider sends us your name, email address and an account identifier, and acts for this as an independent controller, under its own terms.
Contact for any question about personal data: contact@voiladocs.com.
Data processed, purposes and legal bases
| Data | Purpose | Legal basis |
|---|---|---|
| Name, email address and, depending on the sign-in method chosen, picture and Google or Microsoft account ID | Create your account and sign you in (Google, Microsoft or a one-time link sent by email) | Performance of the contract |
| Email address and sign-in link token, stored hashed | Send you a one-time sign-in link | Performance of the contract |
| Organization name, members and roles, invitation links | Manage the organization and everyone’s permissions | Performance of the contract |
| Plan, credits and usage, Stripe customer ID, email address of the paying admin, payment history and invoices | Bill the subscription and credit packs, keep accounting records | Performance of the contract, legal obligation |
| HubSpot portal ID, HubSpot, Google and Microsoft OAuth tokens (encrypted) | Access HubSpot and Google on your behalf, sign you in with Microsoft | Performance of the contract |
| Templates: name, Google Doc ID, variables, mappings, conditions, associated objects, settings; for editor templates, content and saved versions | Create, edit and fill templates | Performance of the contract |
| Generation history: template, HubSpot record type and ID, file name and ID, status, duration, error message | Show the history, count credits, provide support | Performance of the contract |
| Automation rules and their runs, including the property value that triggered generation | Run automations and troubleshoot them | Performance of the contract |
| Emails sent from the application: recipient, subject, message, attached PDF | Send a document at your request; these emails go through our email provider and are not kept in our database | Performance of the contract |
| Admins’ email addresses and credit usage level | Send usage alerts at 80% and 100% of credits | Performance of the contract |
| Onboarding preferences (skipped steps, hidden checklist), stored in a cookie | Show the getting-started checklist as you left it | Performance of the contract |
| Technical logs: IP address, browser, requests, errors | Secure the service and fix incidents | Legitimate interest |
| Exchanges with support | Answer your requests | Legitimate interest |
- Name, email address and, depending on the sign-in method chosen, picture and Google or Microsoft account ID
- Purpose:Create your account and sign you in (Google, Microsoft or a one-time link sent by email)
- Legal basis:Performance of the contract
- Email address and sign-in link token, stored hashed
- Purpose:Send you a one-time sign-in link
- Legal basis:Performance of the contract
- Organization name, members and roles, invitation links
- Purpose:Manage the organization and everyone’s permissions
- Legal basis:Performance of the contract
- Plan, credits and usage, Stripe customer ID, email address of the paying admin, payment history and invoices
- Purpose:Bill the subscription and credit packs, keep accounting records
- Legal basis:Performance of the contract, legal obligation
- HubSpot portal ID, HubSpot, Google and Microsoft OAuth tokens (encrypted)
- Purpose:Access HubSpot and Google on your behalf, sign you in with Microsoft
- Legal basis:Performance of the contract
- Templates: name, Google Doc ID, variables, mappings, conditions, associated objects, settings; for editor templates, content and saved versions
- Purpose:Create, edit and fill templates
- Legal basis:Performance of the contract
- Generation history: template, HubSpot record type and ID, file name and ID, status, duration, error message
- Purpose:Show the history, count credits, provide support
- Legal basis:Performance of the contract
- Automation rules and their runs, including the property value that triggered generation
- Purpose:Run automations and troubleshoot them
- Legal basis:Performance of the contract
- Emails sent from the application: recipient, subject, message, attached PDF
- Purpose:Send a document at your request; these emails go through our email provider and are not kept in our database
- Legal basis:Performance of the contract
- Admins’ email addresses and credit usage level
- Purpose:Send usage alerts at 80% and 100% of credits
- Legal basis:Performance of the contract
- Onboarding preferences (skipped steps, hidden checklist), stored in a cookie
- Purpose:Show the getting-started checklist as you left it
- Legal basis:Performance of the contract
- Technical logs: IP address, browser, requests, errors
- Purpose:Secure the service and fix incidents
- Legal basis:Legitimate interest
- Exchanges with support
- Purpose:Answer your requests
- Legal basis:Legitimate interest
We do not sell any data, we do not run targeted advertising, we use no audience measurement tool, and we do not use your data to train artificial intelligence models.
HubSpot data and generated documents
- The data in your HubSpot records is read at generation time, only for the properties the template uses, and processed in memory.
- A Google Docs template is copied into the Google Drive of the user who added or took it over; the copy is filled, exported as a PDF and deleted right after export. Google Drive access is limited to the documents picked as templates and the copies the application creates.
- VoilaDocs’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- An editor template is stored in our database, with its versions. It is printed to PDF by our own printing service, hosted in Amsterdam next to the generation worker and reachable only by it.
- Images that a template refers to by web address are downloaded from their host at generation time. That host receives our server’s request and no other data.
- The PDF is saved to your HubSpot portal’s files as a private file and attached to the record through a note. We do not keep it on our servers. Links to a document in the application only work for signed-in members of your organization.
- The generation queue only holds technical identifiers, the requested file name and the job’s log, not record or document content.
Recipients
Your data is available to authorized members of your organization according to their role, to our team as far as needed (support, maintenance, security) and to our technical subprocessors, listed on the Subprocessors page with their locations.
We may disclose data to authorities where required by law.
Location and transfers
Our infrastructure is hosted in Europe: server functions and database in Frankfurt, generation worker and PDF printing service in Amsterdam, job queue in London (United Kingdom, covered by a European Commission adequacy decision). The email sending region is shown on the Subprocessors page.
Several of our providers are companies based in the United States. Where access from a third country is possible, it is covered by an adequacy decision, including the EU-US Data Privacy Framework for certified companies, or by the European Commission’s standard contractual clauses.
Retention periods
| Data | Period |
|---|---|
| Account, organization, templates and their versions, rules and history | For as long as you use the service, then deleted within 30 days after the organization is closed |
| Template deleted from the application | Removed from your lists and deactivated at once; erased with the rest of the data when the organization is closed, or earlier on request |
| HubSpot, Google and Microsoft OAuth tokens | Until the service concerned is disconnected, the linked account is removed from settings, or the organization is closed |
| Email sign-in link tokens | 15 minutes at most, erased as soon as they are used |
| Job queue entries | Only the last 100 successful jobs and the last 500 failed jobs are kept for troubleshooting, for at most 7 days and 30 days respectively; the others are deleted automatically |
| Invoices and accounting records | 10 years, as required by the French Commercial Code |
| Technical logs | 30 days at most |
| Exchanges with support | 3 years after the last exchange |
- Account, organization, templates and their versions, rules and history
- Period:For as long as you use the service, then deleted within 30 days after the organization is closed
- Template deleted from the application
- Period:Removed from your lists and deactivated at once; erased with the rest of the data when the organization is closed, or earlier on request
- HubSpot, Google and Microsoft OAuth tokens
- Period:Until the service concerned is disconnected, the linked account is removed from settings, or the organization is closed
- Email sign-in link tokens
- Period:15 minutes at most, erased as soon as they are used
- Job queue entries
- Period:Only the last 100 successful jobs and the last 500 failed jobs are kept for troubleshooting, for at most 7 days and 30 days respectively; the others are deleted automatically
- Invoices and accounting records
- Period:10 years, as required by the French Commercial Code
- Technical logs
- Period:30 days at most
- Exchanges with support
- Period:3 years after the last exchange
Security
OAuth tokens are encrypted with AES-256-GCM before being stored, traffic goes over HTTPS, every request coming from HubSpot is signature-checked, the PDF printing service can only be reached over our private network and refuses internal addresses, and our team’s access is limited to what is strictly needed. Details are on the Security page and in annex 2 of the DPA.
Your rights
You have the right of access, rectification, erasure, restriction, portability and objection, as well as the right to set instructions about your data after your death.
To exercise them, write to contact@voiladocs.com. We answer within one month. Proof of identity may be requested if there is reasonable doubt.
An admin can disconnect HubSpot at any time from the application. Anyone can unlink their Google or Microsoft account from settings, and remove the application’s access from their HubSpot, Google and Microsoft accounts.
You can lodge a complaint with the CNIL, the French data protection authority (cnil.fr), or with the authority of your country.
Changes
We may update this policy. For any significant change, we notify organization admins by email before it takes effect. The date of the last update is shown at the top of the page.