RolePark Subprocessors
This page lists the vendors that process personal data in RolePark. Section 1 lists subprocessors: they process the data of companies’ candidates and staff on the company’s behalf, under the Data Processing Agreement. Section 2 lists providers RolePark uses for its own purposes as a controller — website analytics, payments and indexing of public vacancies. Section 3 lists integrations a company or a user chooses to connect. Each vendor processes data under its own data processing terms.
1. Subprocessors (on the company’s behalf)
| Vendor | What it does | Which data | Where / transfer safeguard |
|---|---|---|---|
| Hosting provider of the application server | Virtual server on which the RolePark application and its PostgreSQL database run; the server is administered by the operator. | All service data | The data-centre country is available on request at help@rolepark.com |
| Cloudflare, Inc. | Network in front of rolepark.com: TLS, protection from attacks and caching. | All traffic in transit, IP addresses, technical request data | Global network; Cloudflare data processing addendum with EU Standard Contractual Clauses |
| Google Cloud (Google Cloud Storage) | Storage of uploaded files (CVs, photos, documents) and daily database backups. | Files and database backups | Google Cloud data processing addendum with EU Standard Contractual Clauses |
| Grafana Labs (Grafana Cloud) | Technical request logs, monitoring and alerts. | User and company identifiers, role, company name, request address and result; no IP addresses, search queries or request content | Grafana Labs data processing addendum with EU Standard Contractual Clauses |
| Email delivery: own mail server, Resend, Inc., Sendinblue SAS (Brevo) | Sending service emails: invitations, interview letters, sign-in links, notifications. Providers are used as primary or fallback channels. | Recipient name and email address, email content | Own server — together with the application server; Resend — USA, Brevo — EU; their data processing terms |
| Telegram | Delivery of notifications through RolePark’s own bot to company users who connected it. | Approval and workflow notifications, which may contain the candidate’s name and email from company templates; an employee’s own position, manager and leave requests | Telegram’s terms; global network |
| Browser push services: Google (Firebase Cloud Messaging), Mozilla, Apple, Microsoft | Delivering push notifications to company users who turned them on. | Device subscription address and a short generic text without names or companies | The push service of the user’s browser |
| JetBrains s.r.o. (YouTrack Cloud) | Our issue tracker: feedback messages and screenshots you send us, and technical error reports. | What you write in feedback and what is visible on your screenshot; technical error details | JetBrains data processing terms |
2. Providers for RolePark’s own purposes
| Vendor | What it does | Which data | Where / transfer safeguard |
|---|---|---|---|
| Google Ireland Limited / Google LLC (Google Analytics 4) | Usage statistics of public informational pages (home, product, pricing, FAQ, legal documents) — only after consent to analytics cookies; never in the workspace, the cabinet or on job pages. | Page address, events, technical parameters, cookie identifiers | Google’s terms; may be processed in the USA |
| Microsoft Corporation (Microsoft Clarity) | Recordings of how the public pages, registration, sign-in and the first screen of new companies are used — only after consent to analytics cookies; all text and images are masked; never elsewhere in the workspace, in the cabinet or on job pages. | Page address, layout, clicks and scrolling, technical parameters, cookie identifiers | Microsoft’s terms; may be processed in the USA |
| Cloudflare, Inc. (Web Analytics) | Cookieless statistics of page views and loading speed. | Page address, technical request data; IP addresses are not stored in reports | Cloudflare’s terms |
| Google Search (Indexing API) | Telling Google about published and closed public vacancies. | Public vacancy address only | Google’s terms |
| LiqPay (JSC CB PrivatBank, Ukraine) | Online card payment for paid plans, where online payment is available. RolePark does not see card numbers. | Company, order, amount, payment status | Ukraine; LiqPay terms |
3. Integrations you choose
These services receive data only if a company or a user connects them, and they process it under their own terms with that company or user: Google Calendar and Google Meet, Zoom, Calendly, the AI assistant a person connects (for example Claude by Anthropic or ChatGPT by OpenAI), single sign-on (SAML) and user provisioning (SCIM) providers, and any system the company connects through the API, webhooks or a job feed. What each of them receives is described in the Privacy Policy (https://rolepark.com/privacy).
4. Changes to this list
We will inform customers in advance of material changes to subprocessors and keep this page up to date. A company may object to a new subprocessor on reasonable data-protection grounds at help@rolepark.com; if we cannot resolve the objection, the company may stop using the affected part of the service or terminate the contract.
RolePark does not use AI or language-model providers to process candidate data on its own servers: CVs are parsed on our server.
Service operator
RolePark (the service operator at rolepark.com)
personal data enquiries: help@rolepark.com