Subprocessors
This is a list of providers that process personal data for Renly — data of our customers as well as data that visitors to our customers' websites enter via the AI assistant. For each one we state what we use it for, what it receives, where it processes the data and what transfers outside the European Economic Area (EEA) rely on.
Last review of the list: 18 November 2026.
This is a translation. In case of any discrepancy, the Slovak version prevails.
01How we maintain the list
We review the list with every change of provider and at least once a quarter. During the review we compare the list with what the platform actually calls and with the providers' current terms.
We will notify customers of a new sub-processor that will process data of customers or their visitors by email to the billing address at least 14 days before we start using it. The customer may object to it following the procedure in the data processing agreement. A provider we stop using is removed from the list.
What exactly goes to AI providers in which situation is described in the Privacy Policy.
02Language models
Renly uses language models from three providers through their paid business APIs, not through consumer applications such as ChatGPT, Claude or Gemini. Which model is used for an assistant depends on its settings and on the customer's package. A single assistant may use models from different providers for different tasks — answers, semantic search, AI knowledge clean-up, auxiliary tasks.
We have not agreed with any of them a mode with no data retention at all by the provider (Zero Data Retention) or processing exclusively in the EU.
OpenAI
| Service | OpenAI API — GPT language models and a semantic search model. |
|---|---|
| What for | The assistant's answers, preparing knowledge and visitors' questions for semantic search, AI knowledge clean-up and auxiliary tasks — whenever an OpenAI model is set for the given task. |
| What it receives | The assistant's instructions, part of the conversation including attachments, knowledge excerpts and, depending on the settings, the page and shared location; for search, knowledge texts and visitors' questions. |
| Contracting party | OpenAI Ireland Ltd., Ireland. |
| Where | USA and other countries in which OpenAI or its sub-processors have infrastructure. |
| Transfers outside the EEA | EU standard contractual clauses under the OpenAI data processing addendum. |
| Training and retention | Under OpenAI's terms, API inputs and outputs are not used to train models without explicit consent. For abuse detection, OpenAI generally retains them for no more than 30 days, longer only when required by law or to protect the service. |
| Documents | Data processing addendum · OpenAI sub-processors |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
Anthropic
| Service | Anthropic API — Claude language models. |
|---|---|
| What for | The assistant's answers, AI knowledge clean-up and auxiliary tasks, when a Claude model is set for them. Anthropic does not provide a semantic search model. |
| What it receives | The assistant's instructions, part of the conversation including attachments, knowledge excerpts and, depending on the settings, the page and shared location; for AI clean-up, parts of the knowledge text. |
| Contracting party | Anthropic Ireland, Limited, Ireland. |
| Where | It stores data in the USA; it may also process requests in other countries in Europe, Asia and Australia. |
| Transfers outside the EEA | EU standard contractual clauses, which form part of the data processing addendum incorporated into Anthropic's commercial terms. |
| Training and retention | Under its commercial terms, Anthropic does not train models on API customers' content. It generally deletes inputs and outputs within 30 days; content flagged as a usage policy violation may be retained for up to two years. |
| Documents | Data processing addendum · Anthropic sub-processors |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
Google (Gemini API)
| Service | Gemini API (paid services) — Gemini language models and a semantic search model. We do not use the free tier of the Gemini API. |
|---|---|
| What for | The assistant's answers, preparing knowledge and visitors' questions for semantic search, AI knowledge clean-up and auxiliary tasks — whenever a Gemini model is set for the given task. |
| What it receives | The assistant's instructions, part of the conversation including attachments, knowledge excerpts and, depending on the settings, the page and shared location; for search, knowledge texts and visitors' questions. |
| Contracting party | Google Cloud EMEA Limited, Ireland (paid Gemini API services). |
| Where | In any country where Google or its sub-processors have facilities, including the USA. |
| Transfers outside the EEA | Under the Google data processing addendum: the EU–US Data Privacy Framework (Google LLC is certified), otherwise EU standard contractual clauses. |
| Training and retention | For paid services, Google does not use prompts or responses to improve its products. It retains them for 55 days for abuse detection. |
| Documents | Gemini API Additional Terms · Data processing addendum · Google sub-processors |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
03Other assistant features
These providers are involved only for a specific feature — if the package and the assistant settings include it and the visitor uses it. Place lookup via OpenStreetMap is in the Other recipients section.
ElevenLabs
| What for | Chat voice mode — speech-to-text transcription and reading the answer aloud. |
|---|---|
| What it receives | The visitor's voice recording for transcription and the answer text it is to read out. |
| Contracting party | Eleven Labs Inc., USA. |
| Where | USA; for accounts that are not Enterprise, also in the EU or in Singapore. |
| Transfers outside the EEA | The EU–US Data Privacy Framework (Eleven Labs Inc. is certified) and EU standard contractual clauses in the ElevenLabs data processing addendum. |
| Training and retention | We have switched off the use of our account's data for training ElevenLabs models in the settings. The no-retention mode (Zero Retention) is only for Enterprise, which we do not have. |
| Documents | Data processing addendum · ElevenLabs sub-processors |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
Exa
| What for | Web search, when the model requests it while answering. |
|---|---|
| What it receives | Only the search query that the language model builds from the visitor's question — not the whole conversation. |
| Contracting party | Exa Labs, Inc., USA. |
| Where | USA. |
| Transfers outside the EEA | EU standard contractual clauses in the Exa data processing addendum. Exa is not part of the EU–US Data Privacy Framework. |
| Training and retention | Under Exa's policies, search queries may be used to improve its models; the no-retention mode is only for Enterprise. That is why Exa receives only a short search query, not the conversation. |
| Documents | Data processing addendum · Exa makes its list of sub-processors available on request in its Trust Center |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
04Platform operation
Hetzner
| What for | Servers on which the platform, its database and this website run. |
|---|---|
| What it receives | It stores all platform data. |
| Contracting party | Hetzner Online GmbH, Germany. |
| Where | Germany (Falkenstein data centre). |
| Transfers outside the EEA | None — the data stays in Germany. |
| Documents | Data processing agreement · Hetzner sub-processors |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
Mailgun
| What for | Sending emails — confirmations, replies, invitations, notifications and invoices — and receiving emails for tickets. |
|---|---|
| What it receives | The recipient's address and the content of the email. |
| Contracting party | Mailgun Technologies, Inc. (Sinch group), USA. |
| Where | EU (Germany and Belgium) for emails, delivery records and statistics; account data is also replicated outside the EU. |
| Transfers outside the EEA | The EU–US Data Privacy Framework (Sinch Email is certified) and EU standard contractual clauses in the Sinch data processing addendum. |
| Documents | Data processing addendum · Sinch sub-processors |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
Sentry
| What for | Technical error reports from the platform, the administration, the chat and the mobile app. |
|---|---|
| What it receives | Technical data about the error; for an error in the administration also the identifier and email of the signed-in user. |
| Contracting party | Functional Software, Inc. (Sentry), USA. |
| Where | Error reports in the EU (Frankfurt); data about accounts and organisation settings in the USA. For AI error analysis (Seer), the report also goes to Sentry's sub-processors in the USA. |
| Transfers outside the EEA | The EU–US Data Privacy Framework (Functional Software, Inc. is certified) and EU standard contractual clauses in the Sentry data processing addendum. |
| Documents | Data processing addendum · Sentry sub-processors |
| Added · reviewed | 7 October 2026 · 7 October 2026 |
Google (Firebase)
| What for | Renly mobile app: notification delivery (Firebase Cloud Messaging) and anonymous screen and action statistics (Google Analytics for Firebase), which the user can turn off in the app. |
|---|---|
| What it receives | Device token, operating system type and notification text (for example that a new document arrived); for statistics the screen or action name and technical device data, without names, e-mail addresses, content or the advertising identifier. |
| Contracting party | Google LLC and Google Ireland Limited under the Firebase and Google Analytics terms. |
| Where | EU and USA; on iPhone, notifications are passed on by Apple (APNs). |
| Transfers outside the EEA | EU-US Data Privacy Framework (Google LLC is certified) and the EU standard contractual clauses in the Firebase data processing terms. |
| Documents | Firebase Data Processing and Security Terms · Firebase subprocessors |
| Added · reviewed | 18 November 2026 · 18 November 2026 |
05Electronic invoices
Only for companies that activate delivery of electronic invoices in the Peppol network in the Finance module. We use it for customer data from 1 December 2026 (Special terms for electronic invoice delivery, in Slovak).
Verteco
| Purpose | Sending and receiving electronic invoices in the Peppol network. Verteco is the certified delivery service provider through which Renly delivers documents. |
|---|---|
| What it receives | Sent and received documents in XML format, including supplier and customer details (for example the name of a sole trader, a contact person, e-mail and phone), and the company and contact person details from activation. |
| Contracting party | Verteco digital services, s. r. o., Žilina, Slovakia (company ID 53 412 834, certified provider EFSK000031). |
| Where | EU — DigitalOcean servers in Frankfurt (Germany). Document content is kept only temporarily, delivery records longer. |
| Transfers outside the EEA | Some of Verteco's subcontractors are based in the USA (DigitalOcean, Cloudflare, Sentry) and may access the data; transfers rely on the EU–U.S. Data Privacy Framework, otherwise on the EU standard contractual clauses. |
| Documents | Data processing agreement (in Slovak) · Verteco privacy policy and subcontractors (in Slovak) |
| Added · reviewed | 10 November 2026 · 10 November 2026 |
06Measurement on this website
On renly.sk we measure traffic only if the visitor allows it in the cookie banner. Customer data and chat conversations are never part of this measurement.
Google (Analytics, Tag Manager)
| What for | Measuring traffic and conversions on renly.sk (Google Analytics 4) and managing measurement tags (Google Tag Manager). |
|---|---|
| What it receives | Visit data — pages viewed, traffic source, device and browser, events on the website; the IP address only to determine the country, it is not stored. Without consent, only anonymous signals without cookies. |
| Contracting party | Google Ireland Limited, Ireland. |
| Where | Google servers in the EU and the USA. |
| Transfers outside the EEA | EU–U.S. Data Privacy Framework (Google LLC is certified) and the EU standard contractual clauses in the Google data processing terms. |
| Documents | Google data processing terms · Google sub-processors |
| Added · reviewed | 8 October 2026 · 8 October 2026 |
07Other recipients that are not our processors
For some features, data goes to services that you choose yourself or that process data in their own name as independent controllers, not on behalf of Renly:
- Card payments — GoPay. The payment gateway is operated by GoPay Czech odštěpný závod (Worldline NV), Czech Republic, as a payment institution. It processes payment data under its own terms; full card details never reach Renly.
- Place lookup — OpenStreetMap. The public Nominatim service is operated by the OpenStreetMap Foundation in the United Kingdom, which is covered by an EU adequacy decision on data protection. The call is made from the Renly server and the service receives only the name of the place or address being searched for, not the whole message.
- Sign-in with Google, Microsoft or Apple — if you choose it, your identity is verified by Google Ireland Limited, Microsoft Ireland Operations Limited or Apple Distribution International Ltd. under their own terms, and they pass us the data described in the Privacy Policy.
- Connected Google or Apple calendar — if you connect a calendar, Renly reads its events and writes the ones you edit in Renly through the Google Calendar API or iCloud CalDAV in your account and under your terms with the provider.
- Documents from Google Drive — if you connect a Google Drive folder to the Knowledge Base, Renly reads the files you have made available from it.
- Facebook and Instagram leads — Meta. If a business turns on the integration with its Facebook Page, Renly retrieves leads from its lead forms via Meta Platforms Ireland Ltd. (Merrion Road, Dublin 4, Ireland) and stores them in its CRM. Meta processes data in the EU and the USA; transfers rely on the EU-U.S. Data Privacy Framework.
- Connection with Claude or ChatGPT — if you connect Renly to your own AI application, the data from Renly is received by that application in your account and under your contract with its provider.
- VAT ID verification — when invoicing, we verify the company's VAT ID in the European Commission's VIES system.