Sub-processors

Version 1.0 · Effective 13 November 2026 · This is the first published version.

To run OliApp we use a small number of third-party services. Where any of them processes personal data that we hold on behalf of a client, it is a sub-processor under our Data Processing Agreement, and it is listed here.

We notify clients at least 30 days before adding or replacing a sub-processor, by updating this page and emailing the contact on file. You may object within that period, as provided in Clause 9 of the Standard Contractual Clauses.

1Sub-processors — candidate data

These services process personal data that our clients control. The Platform's databases, servers and file storage are in the European Union; where each service below processes data is given in its row.

Sub-processorEntity and registered addressLocation of processingWhat it doesTransfer mechanism
Google Cloud — hosting, storageGoogle Cloud Poland Sp. z o.o., Rondo Daszyńskiego 2C, 00-843 Warszawa, Poland / Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USAeurope-central2 Warsaw, europe-west4 Eemshaven, europe-west3 FrankfurtDatabases, application servers, backend services and file storageEU-U.S. Data Privacy Framework — third-line Google LLC engineering support can reach the data
Google Cloud Vertex AI — AI Search, Resume BreakdownGoogle Cloud Poland Sp. z o.o., Rondo Daszyńskiego 2C, 00-843 Warszawa, Poland / Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USAEuropean Union — eu endpoint, processed within EU member statesAI Search and Resume Breakdown. Text sent to the models is not used to train them; Google may keep prompts for a limited period to detect abuse and may cache inputs and outputs for up to 24 hours in the same regionEU-U.S. Data Privacy Framework — third-line Google LLC engineering support can reach the data
PostHogPostHog, Inc., 2261 Market Street #4008, San Francisco, CA 94114, USAEU region — FrankfurtProduct analytics about users of the Platform. Candidate data is excluded from events, masked at source in session recordings, and stripped from logsEU-U.S. Data Privacy Framework — staff outside the EEA can access the EU instance for support
CrispCrisp IM SAS, 2 Boulevard de Launay, 44100 Nantes, FranceFranceLive chat supportNot required — processed within the EEA
HubSpotHubSpot, Inc., USAUSACustomer relationship managementEU-U.S. Data Privacy Framework
CannyCanny, Inc., 800 N King Street, Suite 304 1121, Wilmington, DE 19801, USAUSACollecting product feedbackEU-U.S. Data Privacy Framework
StripeStripe Payments Europe, Limited, Ireland / Stripe, Inc., USAIreland, with transfers to the USA for compliance and fraud preventionPayments. Card details are entered on Stripe's own hosted checkout and never reach usEU-U.S. Data Privacy Framework

Data-protection contacts: Google — data-access-requests@google.com · PostHog — privacy@posthog.com · Crisp — dpo@crisp.chat · Canny — privacy@canny.io

Your own AI provider key. Conversation summaries (those made by message sync on an OpenAI key only), AI-drafted messages and template improvement run only on an OpenAI or Google Gemini API key that a user enters in their own settings, as does AI Search when a request carries such a key. The provider that key belongs to processes the text for the user's organization, under the terms of the provider account the key belongs to; it is not our sub-processor and is not listed here. See Privacy Policy §11.1.

Calendar providers. Where a user connects a calendar, Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) or Microsoft Ireland Operations Limited (One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland) receives the reminders that user creates. Authorisation tokens stay in the user's own browser storage; our servers do not keep them and do not read calendar history.

2Services on our marketing website only

These run on oliapp.co. None of them is present in the Platform behind sign-in or in the browser extension, so no candidate record, CV, recruiter note or work activity reaches them. They are governed by the Cookies Policy and by your cookie choices, and none loads before you consent.

ServiceEntityWhat it doesTransfer mechanism
Google Analytics, Tag ManagerGoogle LLC, USAWebsite measurement, tag loadingEU-U.S. Data Privacy Framework
HotjarHotjar Ltd., Dragonara Business Centre, 5th Floor, Dragonara Road, Paceville, St. Julian's STJ 3141, Malta (Contentsquare group)Heatmaps and recordings of visits to public pagesNot required — processed within the EEA
Meta PixelMeta Platforms Ireland Limited, 4 Grand Canal Square, Grand Canal Harbour, Dublin 2, IrelandMeasuring and targeting our own advertisingEU-U.S. Data Privacy Framework

Data-protection contacts: Hotjar — dpo@hotjar.com

The website itself. oliapp.co is a static site — pages and images only. It runs no application code, stores no personal data and keeps no server-side request logs, and it is administered from within the European Union. What is collected while you browse goes to the tools above, not to the web server.

For the Meta Pixel we and Meta act as joint controllers under Article 26 GDPR in respect of the collection of your data through the Pixel and its transmission to Meta. The essence of that arrangement is set out in Privacy Policy §11.3; Meta's own agreement is at facebook.com/legal/controller_addendum.

3Transfers outside the European Economic Area

For each recipient we rely on one mechanism, named in the tables above and named identically in the Privacy Policy. We do not list two as alternatives. This rule covers transfers under the GDPR; transfers of data from Brazil rely on the Standard Contractual Clauses approved by the ANPD, as set out in Privacy Policy §18.2.

Storing data in the EU does not by itself settle the question: where a provider's non-EEA parent can reach the data for support or administration, that access is a transfer. That is why Google Cloud, including Vertex AI, and PostHog appear with a mechanism even though the data sits in the European Union.

We verify each Data Privacy Framework certification in the official register annually and whenever a provider changes. Where we rely on Standard Contractual Clauses, a copy is available on request from privacy@oliapp.co.

Last verified: November 2026.

4Integrations you connect yourself

Some services receive personal data because you chose to connect them, not because we engaged them. The clearest example is the Slack Integration: you install it into a Slack workspace your organisation owns and contracts for, and data reaches Slack on your instruction.

These are your processors, not ours. They are not listed above and they are not Sub-processors under the Data Processing Agreement — see DPA §8. We do not control them and we cannot answer for them. Disconnecting an integration stops further data flowing to it.

5Other recipients

Besides the sub-processors above, we disclose personal data to our own personnel and contractors — technical, sales, marketing and external legal — under confidentiality obligations. They are not sub-processors within the meaning of the Data Processing Agreement.