Beebole Sub-processor List
Beebole s.r.l. (Brussels, Belgium) uses the third parties below to help deliver its time-tracking and planning service. This page identifies the sub-processors that may process Customer Data on Beebole’s behalf (Beebole acting as processor), separately identifies website/visitor-data processors that do not touch Customer Data, and clarifies which internal vendors are not customer-facing sub-processors.
1. Customer Data sub-processors
These sub-processors may process Customer Data (timesheets, absences, project records, and related account data) where Beebole acts as processor on behalf of the customer (controller). EU customers’ Customer Data stays in the EU.
Sub-processor | Purpose | Data categories | Hosting region | Applies to |
|---|---|---|---|---|
Google Cloud | Hosting, logs, backups, audit trails | Account and Customer Data; logs; audit trails | EU (EU customers) / US (US customers) | V2 (all V2 customers) |
Intercom | In-product support messenger and product notifications | Contact identifiers (name, email), support messages | EU | All |
Stripe | Payment processing | Billing identifiers, payment-method metadata | EU | V2 |
PostHog | Product analytics (session replay NOT enabled) | Product usage data of signed-in users (in-app product analytics) and consented website analytics | EU | All |
PEPPOL e-invoicing (EN 16931) | Customer billing identities, invoice data | EU | All | |
n8n Cloud | Automated Stripe → Factures.com billing-data sync | Billing identifiers, invoice/payment metadata | EU | V2 |
V1 legacy sub-processors (active during coexistence):
Sub-processor | Purpose | Data categories | Hosting region | Applies to |
|---|---|---|---|---|
Linode | Hosting of the V1 service, including Customer Data | Account and Customer Data | EU | V1 |
Adyen | Payment processing | Billing identifiers, payment-method metadata | EU | V1 |
Dual-platform coexistence
Beebole operates two platforms in parallel during a coexistence period expected to last approximately one to two years. This is a parallel operation, not a one-time cutover:
V1 (legacy): Customer Data hosted on Linode (EU); payments via Adyen.
V2 (new): Customer Data hosted on Google Cloud, region-segregated — an EU server for EU companies and a US server for US companies; payments via Stripe (EU-hosted).
EU customers’ Customer Data stays in the EU on both platforms and does not transfer to the United States under V2.
2. Website / visitor-data processors
These processors handle website and documentation-visitor data only. They do not process Customer Data.
Processor | Purpose | Data categories | Hosting region | Applies to |
|---|---|---|---|---|
Vercel | Hosting of the marketing website (no Customer Data) | Website visitor request data | — | All (website visitors) |
Mintlify | Documentation-site (beebole.com/help) visitor analytics | Docs visitor analytics data | — | All (docs visitors) |
3. Internal vendors (not customer-facing sub-processors)
The following vendors support Beebole’s own operations, with Beebole acting as controller of the relevant data. They are not sub-processors of Customer Data and do not process Customer Data on customers’ behalf:
Asana (internal project management)
Storyblok (content management)
GitHub (source code)
Vanta (compliance/security monitoring)
Partena (Belgian payroll)
Google Workspace (internal productivity and email)
Changes to sub-processors
Beebole will give customers reasonable prior notice of any new or changed sub-processor. A customer may object within thirty (30) calendar days of that notice on reasonable data-protection grounds. If a customer objects, Beebole will not appoint (or will not continue to use) the sub-processor for that customer’s Customer Data and will work in good faith to provide an alternative. This mechanism reflects GDPR Article 28(2).