Principle
Our infrastructure is hosted in Europe. We do not store generated documents: the PDF is saved to your HubSpot portal’s files. The temporary Google Docs copy is deleted right after export, and the job queue only holds technical identifiers.
Templates built in our editor are stored in our database (Neon, Frankfurt). They are printed to PDF by our own printing service, Gotenberg with Chromium, which we run on Railway in Amsterdam next to the generation worker, over a private network: no additional provider is involved. Images that a template refers to by web address are downloaded from their host at generation time.
Each subprocessor only accesses the data its role requires and is contractually bound to protect it, in line with article 28 of the GDPR. Transfers outside the European Union rely on an adequacy decision or on the European Commission’s standard contractual clauses.
List of subprocessors
| Subprocessor | Role | Location | Data involved | Safeguards |
|---|---|---|---|---|
| Vercel | Hosting of the website and the application, server functions | Functions in Frankfurt (Germany, fra1 region), global content delivery network (CDN) for public content | All data processed by the application, in transit; technical logs | Provider data processing agreement, standard contractual clauses for any access from the United States |
| Neon | PostgreSQL database | Frankfurt (Germany) | Accounts, organizations and members, templates (settings, mappings, content and versions of templates built in the editor), automation rules, generation history, encrypted OAuth tokens | Provider data processing agreement, encryption at rest, standard contractual clauses for any access from the United States |
| Railway | 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) | Amsterdam (Netherlands, EU West region) | HubSpot data read during generation and the document being printed, in memory only; technical logs | Provider data processing agreement, standard contractual clauses for any access from the United States |
| Upstash | Redis queue for generation jobs and rate-limiting counters | London (United Kingdom) | 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 | European Commission adequacy decision for the United Kingdom, provider data processing agreement, standard contractual clauses for any access from the United States |
| 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 | As set by the customer’s Google agreement | Google profile name, email address and picture; temporary filled copy of the template, deleted right after export | Google terms applicable to the customer’s account, standard contractual clauses | |
| HubSpot | 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 | As set by the customer’s HubSpot agreement | Record properties used by templates; generated PDFs | Agreement between the customer and HubSpot; revocable OAuth access |
| Stripe | Payment of subscriptions and credit packs, invoices, billing portal | European Union and United States | Organization name, email address of the paying admin, billing data; card details are entered with Stripe and never reach us | Provider data processing agreement, standard contractual clauses |
| Resend | Sending sign-in links, invitations, documents by email from the application and usage alerts to admins | [To be completed] | Recipient address, subject and body of the message, sign-in or invitation link, attached PDF | Provider data processing agreement, standard contractual clauses |
- 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
- 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
Google and HubSpot
Google and HubSpot act on the accounts you connect yourself. The data there remains governed by your own agreement with these vendors. We only access it through OAuth, with the permissions you grant and can revoke at any time.
Changes
We inform organization admins by email, and update this page, at least 30 days before adding or replacing a subprocessor. You may object on legitimate grounds within that period, as set out in the data processing agreement.
E-signature with Youtrust (formerly Yousign) is in preparation: Youtrust will be added to this list, through this procedure, before the feature is offered.
Contact
Questions about our subprocessors: contact@voiladocs.com.