Third parties OpesQ relies on to run the platform.
Last updated: 1 May 2026
OpesQ Ltd engages sub-processors to help deliver the platform. A sub-processor is a third party that processes personal data on OpesQ’s behalf (and therefore on the tenant’s behalf as data controller) to provide part of the service.
Each tenant authorises these sub-processors through the Data Processing Agreement at opesq.com/data-processing. OpesQ remains responsible for the acts and omissions of its sub-processors.
| Provider | Purpose | Data processed | Region | Cross-border | Engaged |
|---|---|---|---|---|---|
| Supabase | Postgres database, authentication, storage, edge functions | All tenant and staff data | Ireland (EU, AWS eu-west-1) | No (EEA, UK adequacy) | Always |
| Vercel | Hosting, edge runtime, CDN | Request / response metadata | Functions in Ireland (EU, Dublin dub1); global edge | Routing only | Always |
| Resend | Transactional email delivery | Recipient email, name, message body | UK / EU | No | When email is sent |
| Anthropic | Claude API for the in-app tenant assistant | Signed-in staff chat messages and that company's assistant context | United States | Yes (UK IDTA / SCCs) | In-app tenant assistant only |
| Vercel AI Gateway (OpenAI) | Public ADA support chat on opesq.com. Default model openai/gpt-4.1-nano, overridable with ADA_MODEL. Authenticated with the deployment OIDC token. | Public website chat messages and the sales prompt. The route does not load tenant or staff records. | United States | Yes (UK IDTA / SCCs) | Public website chat only |
| Stripe | Passport Premium subscription payments | Name, email; card data handled by Stripe Elements and never stored on OpesQ servers | UK / EU / US | Yes (UK IDTA / SCCs) | Paid passport features only |
| Veriff | Identity verification (KYC) | ID document, selfie, liveness check | European Union | No | Passport verification flow |
| DVLA (data source, not processor) | UK driving-licence validity check | Licence number, name, date of birth | United Kingdom | No | Driving-credentials module |
| Google (Calendar) | OAuth and Google Calendar API | OAuth tokens, calendar event content | United States | Yes (UK IDTA / SCCs) | Tenants who connect Google Calendar |
| Google (Places API) | Address autocomplete | Address query string (anonymous) | United States | Yes (UK IDTA / SCCs) | When the address-lookup component renders |
| Microsoft (Graph) | Azure AD OAuth and Outlook Calendar integration | OAuth tokens, calendar event content | United States / EU | Yes (UK IDTA / SCCs) | Tenants who connect Outlook |
| Gotenberg | HTML to PDF rendering | Document content during render | Self-hosted where configured | Depends on deployment | PDF generation paths |
| OpenAI / Groq (pluggable) | Audio transcription (Whisper-compatible) | Audio file and returned transcript | United States | Yes (UK IDTA / SCCs) | Feature-flagged via environment |
Where a sub-processor operates outside the UK in a country without an adequacy decision, we rely on the UK International Data Transfer Agreement (IDTA) or the UK Addendum to the EU Standard Contractual Clauses, with appropriate supplementary measures as required under UK GDPR.
OpesQ will give tenants at least 30 days’ advance notice by email and in-app banner before adding or replacing a sub-processor. During that window tenants may object on reasonable data-protection grounds by posting their objection to Settings → Legal → Sub-processors (head admins only). If we cannot accommodate an objection, the tenant may terminate the subscription without penalty before the change takes effect.