Privacy Policy
I use OliApp
You are a recruiter, a manager, or a client of ours. This covers your account, your activity in the product, your billing and your support conversations.
My data is with you
You did not sign up — a recruiter added you, or you applied for a role. The organisation that added you controls your data; we process it on their instructions.
Make a request about your data1Who We Are
OliApp is operated by FreySoft Poland Spółka z ograniczoną odpowiedzialnością ("FreySoft Poland Sp. z o.o."), registered address ul. Domaniewska 45, 02-672 Warszawa, Poland ("OliApp," "we," "us," "Company"). This Policy covers every surface through which OliApp is used: app.oliapp.co (the Platform), oliapp.co (our website), our browser extension, and our Slack integration. Where a section applies to only one of these, it says so. A mobile application is not yet released; this Policy will be updated before it is.
We kindly invite you to share your concerns with us in the first place regarding any issue related to your personal data processing. You may contact us to address your inquiries: privacy@oliapp.co.
Supervisory Authority under GDPR:
In case of any questions regarding data protection, you can apply to the supervisory authority. We will cooperate with the appropriate governmental authorities to resolve any privacy-related complaints that cannot be amicably resolved between you and us. You can find the full list of EU supervisory authorities through the link.
2Definitions
The following terms are used throughout this Policy:
Data controller — the natural or legal person who determines the purposes and means of processing personal data.
Data processor — the natural or legal person who processes personal data on behalf of the controller.
Data subject — any living individual whose personal data we process.
Personal data — any information relating to, and helping identify, a data subject.
Processing — any operation performed on personal data, automated or not.
Joint controllers — two or more controllers jointly determining the purposes and means of processing.
You may interact with us as a visitor (browsing the Site), a recruiter/client (registered account holder), or a candidate (your data was submitted to us by a client for recruitment purposes).
3Scope: Two Roles, Two Tables
We process personal data in two capacities, kept separate throughout this policy. The two subsections below are the starting points for the two kinds of reader; each one says where to go next.
3.1 If you use OliApp
You are a recruiter, a manager, or a client of ours, and you have an account.
For everything about you in that capacity we are the controller — we decide why and how your data is used. That covers your account, billing, your activity in the product, your position on the market leaderboard, and your support conversations.
Where to go next: what we hold about you is listed in §5, the legal grounds in §7, and your rights and how to exercise them in §17.
3.2 If your data is with us
You did not sign up. A recruiter added you, or you applied through a Job Ads page.
For your data we are the processor: the recruiting organisation decides why and how it is used, and we act only on their documented instructions under our Data Processing Agreement. That organisation is named on the Job Ads page you applied through. Contact them first — they are the ones who decide. If you cannot reach them, or you want to be removed from the platform as a whole rather than from one organisation, come to us.
Where to go next: what is held about you is listed in §6, your rights in §17, and you can ask us directly at Your Data Request.
4Sources of Personal Data
| Source | What we get |
|---|---|
| Directly from you | Registration, billing, support requests |
| Your use of the product | Activity logs, sourcing actions, extension usage |
| Third-party sign-in providers | Name, email, profile photo — see §10 |
| Your organization | Candidate data entered or imported by your recruiters |
| Candidates, via Job Ads | Application content, contact details, referral consent |
| Third-party job boards | Applicant data for vacancies your organization published there, received through the board's API. Excluded from the Referral Pool by default (§6) |
| Third-party platforms accessed via our extension | Profile/page view events, message metadata — page content is never scraped (§22) |
| Your workspace's Slack, where the integration is connected | Actions a recruiter takes in Slack: a status change, a comment. The same data as in the Platform, reached through a different interface — see §22 |
| Our Site, the post-install welcome page, and our extension | Product-analytics events: pages viewed, which feature you arrived for, language, browser and extension version, and counts of actions taken. An identifier that is anonymous until you sign in — see §5 and §21 |
| Your device, before you sign up | In Guest Mode the templates, keywords and stopwords you create stay in your browser's local storage and are not sent to us until you sign in — see §22 |
5Categories of Personal Data — Controller Mode
Data about you, the recruiter. We determine the purpose.
| Category | What it includes | Purpose | Legal basis | Recipients | Retention |
|---|---|---|---|---|---|
| Account & billing | Name, email, password hash, billing address, plan, invoices, payment method (held by our payment provider) | Provide and bill for the service | Contract, Art. 6(1)(b) | Payment provider; CRM (§11) | Duration of the account, then |
| Recruiter activity & sourcing logs | Profile/page views via extension (URL + timestamp), group-view events (view only), extension usage, IP-derived geolocation and "likely VPN" flag, message-count metadata (not content) | Run the product; feed leaderboard | Contract for core logs; consent for leaderboard portion | Internal | |
| Market leaderboard / reputation score | Performance score linked to a nickname, tied to your account — not disclosed to other users unless you reveal your name | Peer benchmarking | Consent (declining moves you to a paid plan) | Internal | Current score kept while you participate, deleted when you stop participating (§9). Weekly snapshots |
| Support communications | Emails/tickets, and the live-chat conversations you have with us through the support widget | Respond to requests | Legitimate interest / contract | Internal; Crisp (§11) | . Your Crisp profile and all of your support conversations are deleted at Crisp when your account is purged |
| Product analytics and session replay | Pages and screens you open, features you use, counts of actions, browser and extension version, an identifier that is your internal user id once you are signed in — not your name or email — and an approximate location (country and city) derived from your IP address; and, on the Platform, a replay of your screen in which all text, input values, images and file previews are masked and console output and network payloads are not captured | Understand how the product is used and where people get stuck | Consent for the storage used on your device (§21); legitimate interest for the analysis itself, Art. 6(1)(f) | PostHog (§11), EU region | Session replay recordings: 30 days. Events: |
On the leaderboard score: the categories of input are disclosed above; the weights and thresholds are not, as they are a trade secret. The score affects nothing about your price, your access, or your position in any ranking shown to a customer.
How Referral Pool requests are routed. Where a request is raised in the Referral Pool, an automated relevancy algorithm routes it to the recruiters most likely to be able to help. Routing is decided by subject-matter fit: how many relevant candidate profiles a workspace holds in the required specialisation, and whether that workspace has historically held matching skill sets. The algorithm does not evaluate any personal metric about an individual recruiter — not their score, not their speed, not their activity. It looks at what a workspace holds, not at who works there. We may refine the matching parameters to keep response quality up.
6Categories of Personal Data — Processor Mode
Data about candidates and your team, controlled by your organization, processed by us under instruction and our DPA (Data Processing Agreement).
Retention for every category in this table is determined by your organization as controller. We delete on its instruction, and in any event on closure of its account, in accordance with DPA §5.6. We do not set independent retention periods for data we process on your behalf. The exceptions are the text passed to the AI features that run on Vertex AI, which Google may keep for a limited period under the Google Cloud terms to detect abuse and may cache for up to 24 hours, and text sent under a user's own AI provider key, which that provider keeps under the terms of the provider account the key belongs to (see §11.1).
| Category | What it includes | Notes |
|---|---|---|
| Candidates added manually | CV content, contact details, notes, custom fields | Standard recruiting-CRM use |
| Candidates via Job Ads | Application content, contact details, referral-pool consent flag | Job-Ads-creating organization is controller; the notice shown at the point of application identifies it |
| Candidates from third-party job boards | Applicant data received through the board's API | Excluded from the Referral Pool by default, because the board's own terms typically restrict use to the vacancy applied for |
| Resume parsing — extracted fields | Fields taken directly from resume text | Direct extraction |
| Resume parsing — inferred fields | Industry, experience duration when not explicit | Marked as inferred; correctable; exportable |
| Referral pool ("Ask for Help") | Per-candidate flag: included by default (legitimate interest, manual entries) / excluded (objected) / explicit consent (Job Ads opt-in) | External-job-board candidates excluded by default; no data reaches requester until candidate confirms |
| Messaging synchronization | Factual conversation summary; raw text deleted after summary generated | Opt-in per user, off by default, admin cannot enable on your behalf; no sentiment/intent extraction |
| Team performance metrics | Per-person metrics visible to same workspace | Your organization's purpose; their duty to inform employees |
Cross-platform identity linking. Our extension can associate activity across supported platforms (e.g., a professional-network profile and a messaging account) with one underlying person, using shared identifiers. Disclosed explicitly, not left implicit.
7Lawful Basis for Processing
We rely on the same four grounds the current policy already commits to, applied more specifically per data category above:
Consent (Art. 6(1)(a)) — leaderboard/analytics participation, Job Ads referral checkbox, message-sync opt-in. Withdrawable at any time by emailing privacy@oliapp.co, without affecting prior processing.
Legitimate interests (Art. 6(1)(f)) — referral-pool default for manually-added candidates, fraud prevention, site functionality.
Contract performance (Art. 6(1)(b)) — core service provision.
Legal obligation (Art. 6(1)(c)) — accounting, tax, regulatory record-keeping.
8Automated Decision-Making and Profiling
The current live policy states: "We DO NOT use automated decision-making and profiling." This is inaccurate and is corrected here.
Not happening: fully automated decisions about candidates with legal or similarly significant effects; ranking or scoring candidates for suitability. Article 22 GDPR does not apply to any current feature.
Happening, and is profiling in the GDPR sense:
Resume inference of industry/experience (§6) — new data about a person that didn't previously exist in that form.
The leaderboard score (§5) — a computed evaluation of your own activity as a recruiter.
| Feature | What it does | What it does not do |
|---|---|---|
| AI Search | Turns a natural-language query into structured search filters | Does not evaluate or rank candidates |
| Resume Breakdown | Extracts, and where not explicit, infers structured fields | Does not score candidate suitability |
| Chat Summary | Produces a factual summary of a candidate conversation | Does not infer sentiment, emotion, or intent — deliberate design choice |
9Aggregate and Pseudonymized Data (the Leaderboard)
We do not call leaderboard data "anonymous" — the nickname stays linked to your account, and revealing your real name ties your score to your professional identity. Until you do, your score is not disclosed to other users in an identifying way.
Two separate controls: hide my score (calculation continues, visibility to others stops) and stop participating (calculation stops entirely, existing values deleted, excluded from future percentile calculations).
10Third-Party Sign-In and Calendar Access
Signing in with Google, Microsoft, LinkedIn or Facebook
You can sign in to OliApp with any of these providers. We request the minimum needed to identify you and create your account:
| Provider | Scopes requested | Why |
|---|---|---|
openid, profile, email | Identify you through OpenID Connect; read your name and profile picture for your account; read your verified email address to create or match your account | |
| Microsoft | User.Read | Read your basic profile — name, identifier and work email — through Microsoft Graph |
openid, profile, email | Identify you through OpenID Connect; read your name and profile picture; read your primary email address | |
email, public_profile | Read your email address to create or link your account; read the basic public profile (name, picture) the platform provides by default |
We do not request and do not have access to the contents of your mailbox, your private messages, your contacts or your address book, through any of these four sign-in flows. We do not store the identity providers' authorisation tokens on our servers.
Calendar access
Where you use the scheduling and reminder features, you can connect a calendar:
| Provider | Entity | Scopes requested |
|---|---|---|
| Google Calendar | Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland / Google LLC | openid, userinfo.profile, userinfo.email, calendar |
| Microsoft Outlook Calendar | Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland / Microsoft Corporation | openid, profile, email, offline_access, User.Read, Calendars.ReadWrite |
Calendar authorisation tokens are held in your browser's own extension storage on your device. Our servers do not store them and do not read your calendar history; processing is limited to exchanging the authorisation code for a token and creating the reminders you ask for.
Our use of data received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.
11Who We Share Data With
11.1 Infrastructure and processing — where the product actually runs
The Platform itself — its databases, servers and file storage — runs on Google Cloud Platform, contracted through Google Cloud Poland Sp. z o.o., Rondo Daszyńskiego 2C, 00-843 Warszawa, Poland, in European regions only:
| Region | What runs there |
|---|---|
europe-central2 — Warsaw, Poland | Database, application servers (Compute Engine), backend services and functions (Cloud Run), file buckets (Cloud Storage) |
europe-west4 — Eemshaven, Netherlands | Additional backend services and functions, file buckets |
europe-west3 — Frankfurt, Germany | File buckets |
eu — European Union multi-region | AI Search and Resume Breakdown (Vertex AI); requests are processed within EU member states |
Uploaded CVs and attachments are held in Google Cloud Storage in those regions and served directly from it. We use no content delivery network.
AI Search and Resume Breakdown run on Gemini models through Google Cloud's Vertex AI (AI Search unless a request carries a user's own key, below), contracted through Google Cloud Poland Sp. z o.o. under the same terms as the rest of the Platform. We call it through its European Union endpoint (eu), so the text passed to these features is processed within EU member states. Google does not use that text, or the models' answers, to train or fine-tune its models. Google may keep prompts for a limited period to detect abuse, as Section 4.3 of the Google Cloud Platform Terms of Service allows, and may cache inputs and outputs for up to 24 hours, in the same region and for our project only, to answer faster.
Features that run on your own AI provider key. Chat Summary, AI-drafted messages and replies in the browser extension, and template improvement run only on an OpenAI or Google Gemini API key that a user of your organization enters in their own settings, and the summaries made when message sync is on run only on an OpenAI key; without a key these features do not run. AI Search, which otherwise runs on Vertex AI, uses such a key only when a request carries one. With one, the text is sent, on your organization's instruction, to the provider the key belongs to — OpenAI in the United States, or Google's Gemini API, which guarantees no processing region — and is processed under the terms of the provider account the key belongs to. That provider acts for your organization, not as our sub-processor, in the same way as a Slack workspace you connect (DPA §8); a user who enters their own key acts for your organization, which is responsible for the terms with that provider. That provider also sets how long it keeps the text.
11.2 Other recipients
| Recipient | Purpose | Data shared |
|---|---|---|
| Stripe (Stripe Payments Europe, Limited, Ireland) | Payments | None collected by us. When you pay, you are taken to Stripe's own hosted checkout page. We do not collect or store card details and we place no payment cookies on our pages |
| PostHog (PostHog, Inc., USA — stored in the EU region, Frankfurt) | Product analytics and session replay inside the Platform | Data about you as a user — your internal user identifier, which pages and screens you open, feature-usage counts, browser, device and extension version, and an approximate location (country and city) that PostHog derives from the IP address of your browser. Your name and email address are not sent — you are identified by the internal id alone. Session recordings have all text, input values, images and file previews masked at source, and page titles, URLs and network payloads are redacted or dropped before they leave your browser. No candidate data reaches PostHog: candidate fields, CV content and recruiter notes are excluded from events and masked in recordings, and stripped from logs |
| Crisp (Crisp IM SAS, France) | Live chat support | Your name and email, and the content of your support conversations |
| HubSpot (HubSpot, Inc., USA) | Customer relationship management | Contact and account information |
| Canny (Canny, Inc., USA) | Collecting product feedback | Contact information |
| Google (Google LLC, USA) — Analytics, Tag Manager | Website measurement on oliapp.co | Pages visited, device and browser information, and the identifiers Google sets in your browser |
| Hotjar (Hotjar Ltd., Malta — Contentsquare group) | Heatmaps and visit recordings on our marketing website only | Pages visited, mouse movement, clicks and scrolling, device and browser information |
| Meta (Meta Platforms Ireland Limited) | Measuring and targeting our own advertising on our marketing website only | Pixel events: pages visited and the fact of an install or registration, with the identifiers Meta sets in your browser |
What does not touch your candidates. Hotjar, Meta and Google Tag Manager run on the public marketing website. They are not present in the Platform behind sign-in and not in the browser extension. No candidate record, CV, recruiter note or work activity reaches them.
Slack is not on this list, deliberately. Where you connect our Slack integration, data moves into a Slack workspace your organisation owns and contracts for. That is a disclosure we make on your instruction to a service of yours, not a sub-processor we engaged. See Data Processing Agreement §8.
The full, current list of sub-processors — with the jurisdiction, the purpose and the transfer mechanism for each — is published at oliapp.co/subprocessors, where you can also subscribe to be notified of changes. We also disclose personal data to our own personnel and contractors — technical, sales, marketing and external legal — under confidentiality obligations.
11.3 Joint controllership with Meta
For the collection of your data through the Meta Pixel on our website, and its transmission to Meta, we and Meta Platforms Ireland Limited (4 Grand Canal Square, Grand Canal Harbour, Dublin 2, Ireland) act as joint controllers under Article 26 GDPR. The essence of that arrangement, as Article 26(2) requires:
- What it covers. Joint control applies only to the collection of page-visit events on our website through your browser and their transmission to Meta. Meta's subsequent processing inside its advertising network — personalisation, analytics, profiling — is carried out by Meta as an independent controller.
- Legal basis. The Pixel does not run and collects nothing until you give consent through the cookie banner on our website. You can withdraw that consent at any time in the cookie settings.
- Your rights. For anything concerning processing inside Meta's systems — access, correction, erasure, restriction under Articles 15–21 — Meta Platforms Ireland Limited is the responsible party. You can approach Meta directly through your account settings, or contact us and we will pass the request to Meta.
- The agreement itself is Meta's Controller Addendum, at facebook.com/legal/controller_addendum.
12Sales and Sharing of Personal Data
Candidate data: no. We do not sell, rent or share the personal data held in a Customer's workspace, and we do not disclose it to third parties for their own marketing or commercial purposes. The Referral Pool does not change this: matching is performed by an algorithm against anonymised attributes, no other Customer is given access to your database, and no candidate's identity or contact details are disclosed by the Platform to anyone. See §6 and Terms of Use §2.5.
Website advertising: yes, under the Californian definition. The advertising and analytics tools on our public marketing website collect online identifiers and browsing activity for advertising purposes. Under the broad statutory definitions of the CCPA, that activity constitutes "sharing", and may constitute a "sale". It concerns website visitors, not candidates. See §19 for how to opt out.
13International Data Transfers
Where your data is. All platform infrastructure — databases, application servers, backend services, file storage and the Vertex AI processing behind AI Search and Resume Breakdown — is in the European Union, in the Google Cloud regions listed in §11.1. Features that run on a user's own AI provider key send text to the provider that key belongs to, on the organization's instruction (§11.1). We store no candidate data, CV or recruiter activity outside the European Economic Area. Text sent under a user's own AI provider key is sent by our servers on the recruiting organization's instruction to the organization's own provider, not to a recipient of ours, so it has no row below. Outside the Platform, data about our clients' own users reaches the US providers in §11.2, such as HubSpot and Canny, and some providers' US staff can reach data held in the EU for support, under the mechanism named for each below.
Where a transfer still arises. Storage inside 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 counts as a transfer. For each such recipient we rely on one mechanism, named below and named identically on our sub-processor page. This rule covers transfers under the GDPR; transfers of data from Brazil are covered in §18.2.
| Recipient | Transfer outside the EEA | Mechanism |
|---|---|---|
| Google Cloud (hosting, storage) — Google Cloud Poland Sp. z o.o. / Google LLC | Yes, third-line engineering support from Google LLC | EU-U.S. Data Privacy Framework |
| Google Cloud Vertex AI (Gemini models) — Google Cloud Poland Sp. z o.o. / Google LLC | Yes, third-line engineering support from Google LLC, as for Google Cloud. The requests themselves are processed within EU member states (eu endpoint); 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 region | EU-U.S. Data Privacy Framework |
| Google LLC (Analytics, Tag Manager) | Yes | EU-U.S. Data Privacy Framework |
| PostHog, Inc. | Yes — stored in Frankfurt, but engineering and support staff outside the EEA can access it | EU-U.S. Data Privacy Framework |
| Meta Platforms Ireland Limited / Meta Platforms, Inc. | Yes | EU-U.S. Data Privacy Framework |
| HubSpot, Inc. | Yes | EU-U.S. Data Privacy Framework |
| Canny, Inc. | Yes | EU-U.S. Data Privacy Framework |
| Stripe Payments Europe, Limited / Stripe, Inc. | Yes, for compliance and fraud prevention | EU-U.S. Data Privacy Framework |
| Crisp IM SAS (France) | No | Not required — processed within the EEA |
| Hotjar Ltd. (Malta) | No | Not required — processed within the EEA |
Our marketing website. oliapp.co is a static site — pages and images, served from a server in Germany. It runs no application code of its own, stores no personal data, and keeps no server-side request logs. The data collected while you browse it goes to the analytics and advertising tools listed in §11, loaded through Google Tag Manager after you consent; it does not land on the web server. The site is administered from within the European Union.
We check each certification in the Data Privacy Framework register annually, and whenever a provider changes.
A copy of the Standard Contractual Clauses is available on request from privacy@oliapp.co.
14How We Store and Retain Your Data
Retention for data we control is set out below. For data your organization controls (§6), your organization determines the period; we delete on its instruction and in any event on closure of its account, in accordance with DPA §5.6. The exceptions are the text passed to the AI features that run on Vertex AI, which Google may keep for a limited period, and text sent under a user's own AI provider key, which that provider keeps under the terms of the provider account the key belongs to (see §11.1).
| What | How long | Why |
|---|---|---|
| Invoices and financial records | 5 years from the end of the calendar year in which the tax became due | Statutory accounting and tax obligations (Art. 6(1)(c) GDPR; Art. 70 Ordynacja podatkowa) |
| Raw activity events | 30 days | The scoring window is 14 days, so older events carry no weight; plus system diagnostics |
| Leaderboard snapshots | 12 months | Legitimate interest (Art. 6(1)(f)): year-on-year analytics for business customers |
| Support conversations | 3 years from the last contact | Legitimate interest: handling disputes within the general limitation period (Art. 118 Kodeks cywilny) |
| Product-analytics events | 24 months | Engagement analysis, product development, cohort analysis |
| Session replay recordings | 30 days | Interface diagnostics and UX research; deleted automatically |
You may request deletion at any time by emailing privacy@oliapp.co.
15Data Security
We maintain organizational, technical, administrative, and physical measures to protect personal data, reviewed regularly.
Concretely: data at rest is encrypted with AES-256 by the underlying Google Cloud infrastructure, and particularly sensitive fields — integration keys, candidate data aggregates, conversation summaries, operation audit records and CV upload-link secrets — are encrypted a second time at application level. Public endpoints are served over TLS 1.2 or higher, with no fallback to earlier versions. Logs are stripped of personal data and tokens before leaving our systems, at the logging layer itself. Databases are backed up daily to storage in Poland and kept for 30 days, with an alert if a backup does not arrive. Access to production is limited to five named people, reached through an identity-aware tunnel rather than exposed credentials, with multi-factor authentication enforced at organisation level on the cloud console and on source control; deployment runs through workload identity federation, so our build system holds no long-lived cloud credentials. Container images and dependencies are scanned for known vulnerabilities and committed secrets, and the list of accepted findings can only shrink.
The full description is in our Trust Center and in Annex II of the Data Processing Agreement.
16Children
Our Site and Services are intended for users aged 18 or over. We do not knowingly collect personal data from anyone under 18.
If we become aware that a person under 18 has provided us with personal data, we will delete it promptly. If you believe a minor has provided us with personal data, please contact us at privacy@oliapp.co.
Where United States law applies, we additionally observe the Children's Online Privacy Protection Act ("COPPA"), which concerns children under 13.
17Your Rights (GDPR / UK GDPR)
If you are a recruiter (controller-mode data, §5), contact privacy@oliapp.co to:
access your personal data;
correct it, including inferred data;
request erasure;
restrict or object to processing;
receive your data in a portable format;
withdraw consent, without affecting prior processing;
lodge a complaint with a supervisory authority — see §23.
If you are a candidate, contact the organization that manages your data first (identified on the page where you applied); we assist as processor if they're unreachable.
Where a request for erasure reaches us directly. A recruiting organization can delete your record from its own database at any time using the ordinary controls in the product. Separately, where a request reaches us rather than a recruiter, we can act across the whole platform: we locate every record that holds your contact details, across every organization using OliApp, export it on request, and erase it. After erasure each record keeps only an internal identifier, its dates, the vacancies it was linked to, its stage history, structured rejection codes and a label marking it erased — nothing from which you can be identified. Free-text notes written about you are removed with the rest. If your CV was passed to Resume Breakdown, or a search about you was run through AI Search, on Vertex AI, Google may keep that text for a limited period to detect abuse, and cache it for up to 24 hours, under the Google Cloud terms, and deletes it when that period ends (see §11.1); we cannot shorten it. If text about you — conversation text sent for a summary, the context of an AI-drafted message, or a search — was sent under a recruiter's own AI provider key, the provider that key belongs to keeps it under the terms of the provider account the key belongs to; ask the recruiting organization to have it deleted there.
What we keep afterwards, and why. So that the same erasure does not have to be repeated every time your details are imported again, we keep a one-way hash of the contact details that were erased, together with the date. It cannot be read back into a contact detail; its only function is to refuse the re-creation of your record. Only the contact details confirmed to be yours are held this way: a CV can carry a referee's email or an agency's phone number, and those belong to someone else and are not placed on that list.
Before anything is erased, an operator reviews the records we found and confirms which values belong to you. Only those are suppressed; a referee's email or an agency's phone number that happened to be in a CV is erased with the record but never placed on that list.
18Your Brazil Privacy Rights (LGPD)
If you are in Brazil, Brazil's General Data Protection Law (Lei Geral de Proteção de Dados, Law No. 13.709/2018, "LGPD") applies to our processing of your personal data. The LGPD is closely modelled on the GDPR, and the roles described in §3 apply in the same way: we are controlador for the data in §5 and operador for the data in §6.
In addition to the rights listed in §17, you may request:
- confirmation that we process your personal data, and access to it;
- correction of incomplete, inaccurate, or out-of-date data, including data inferred by resume parsing (§6);
- anonymisation, blocking, or deletion of data that is unnecessary, excessive, or processed in a way that does not comply with the LGPD;
- portability of your data to another service provider;
- deletion of data processed on the basis of your consent;
- information about the public and private entities with which we have shared your data (§11);
- information about the possibility of refusing consent, and the consequences of refusing;
- withdrawal of consent at any time;
- review of decisions taken solely on the basis of automated processing — see §8, which explains that no such decisions are made about candidates.
Requests go to privacy@oliapp.co. Where your data is processed on behalf of a recruiting organization (§6), contact that organization first; it is identified in the notice shown at the point your data was collected.
18.1 Communication channel instead of an encarregado
OliApp qualifies as a small-scale processing agent (agente de tratamento de pequeno porte) under Resolution CD/ANPD No. 2 of 27 January 2022, and under Article 11 of that Resolution is exempt from formally appointing an Encarregado pelo Tratamento de Dados Pessoais.
In place of that appointment, and as Article 11(1) requires, we maintain a direct channel for data subjects and for the ANPD:
- privacy@oliapp.co, subject line "LGPD – Direitos do Titular"
- Requests from Brazilian data subjects are handled within the LGPD deadlines, as extended for small-scale agents by ANPD Resolution No. 2/2022.
18.2 International transfers from Brazil
Personal data collected from data subjects in Brazil is transferred to and hosted on our infrastructure in the European Union (Google Cloud regions in Poland, Germany and the Netherlands). Some of it also reaches the United States: the US recipients listed in §13 either hold data there, as HubSpot and Canny do, or can reach it from there for support, compliance or fraud prevention.
Those transfers, to the European Union and to the United States alike, are made under Article 33 LGPD and Resolution CD/ANPD No. 19/2024, relying on the Standard Contractual Clauses approved by the ANPD (Cláusulas-Padrão Contratuais), which provide a level of protection equivalent to Brazilian standards.
Separately, where a user of a recruiting organization uses their own AI provider key (§11.1), text passed to those features goes to the provider that key belongs to on that organization's instruction: OpenAI in the United States, or Google's Gemini API, which guarantees no processing region. Our servers send it on the organization's instruction to the organization's own provider, not to a recipient of ours, so the clauses above do not cover it.
19Your California Privacy Rights (CCPA/CPRA)
This section applies to California residents under the California Consumer Privacy Act as amended by the California Privacy Rights Act.
19.1 Notice of "sale" or "sharing"
Workspace and candidate data. We do not sell, rent or share the personal data held in a Customer's workspace — candidate profiles, recruiting notes, CVs — for money or for any other valuable consideration. The Platform grants no third party access to a candidate database.
Third-party advertising on our marketing website. When you visit our public website, third-party analytics and advertising tools, including the Meta Pixel, may collect online identifiers, device identifiers and browsing activity in order to deliver cross-context behavioural advertising. Under the CCPA's broad definitions, that activity constitutes "sharing", and may constitute a "sale".
19.2 Categories disclosed for cross-context behavioural advertising
- Category A — Identifiers: IP address, cookie identifiers, other online identifiers.
- Category F — Internet or network activity: pages viewed, interaction telemetry, referring URLs.
19.3 Your right to opt out
You may direct us not to sell or share your personal information. You can do that by:
- using the cookie settings link in our website footer to withdraw consent to the statistics and marketing cookies; or
- enabling a recognised opt-out preference signal in your browser, such as Global Privacy Control (GPC). Where our website detects an active GPC signal, non-essential advertising cookies and trackers are disabled automatically for that session.
19.4 Your other rights
Right to know and access, right to delete, right to correct, right to limit the use of sensitive personal information, right to opt out of profiling, and the right not to be discriminated against for exercising any of them. We respond within 45 days. Requests go to privacy@oliapp.co.
20Other U.S. State Privacy Rights
Additional state-specific sections will be added as the product gains users in those states.
21Cookies
Full detail is in the separate Cookies Policy. In short: necessary cookies always run; statistics and marketing cookies run only after you consent, through the consent banner on our website.
The same rule applies to technologies that are not cookies. What the rule covers is storing information on your device, or reading what is already stored there — so it reaches browser local storage, session storage and the storage our extension uses, not only cookies.
Known providers today:
- Necessary — our own session keys and Keycloak for sign-in. These are set by the Site and the Platform directly.
- Statistics — Google Analytics, Hotjar, and PostHog.
- Marketing — the Meta Pixel.
- Support chat — Crisp.
The statistics and marketing tools on our website, including those on the post-install welcome page, are loaded through Google Tag Manager and only after consent. PostHog runs inside the Platform rather than on the website, and is loaded by the application itself.
22Third-Party Platforms, Our Browser Extension, and Guest Mode
Our extension operates through a Chrome side panel and does not modify pages you visit, except an optional keyword-highlighting feature, off by default, enabled only by you. You're responsible for complying with third-party platform terms (e.g., LinkedIn, WhatsApp) accessed through our extension; we don't guarantee continued access to any third-party platform or its API and aren't liable for account restrictions a platform imposes.
We do not position OliApp — in marketing, in this policy, or in our Chrome Web Store listing, which must match this policy — as a tool for extracting, scraping or harvesting data from LinkedIn or from any other third-party platform, and we do not use any equivalent phrase.
Our Chrome Web Store listing reflects this: in Guest Mode nothing leaves your device.
The Slack integration. A client can connect OliApp to their own Slack workspace. Once connected, a recruiter who has signed in can look at a candidate, change a candidate's status, and write a comment, from inside Slack. The integration adds nothing to what that person could already do in the Platform: it reads and writes the same records, under the same permissions, and a person who cannot see a candidate in OliApp cannot see them in Slack either. No data is stored in Slack that is not already in OliApp.
One behaviour works differently, and we state it plainly. When a link to a candidate is pasted into a Slack channel where the integration is connected, Slack asks us to expand it, and we return a small card showing:
- the candidate's name;
- their current pipeline status — for example Screening, Shortlisted, Offer;
- the time that status was last updated, and buttons to change the status or open the discussion.
That card becomes part of the Slack message, so everyone in that channel sees it, including colleagues with no OliApp account and external guests in shared or Slack Connect channels. Slack's architecture offers no way to show a link preview to some members of a channel and hide it from others.
Contact details, CV files, photographs, recruiter notes and conversation history are never in the card. The card links to the full profile, and opening that link requires an authenticated OliApp session with permission to see that candidate; anyone else gets an access-denied page.
We say this in full because the status is the sensitive part. A name tells a channel little; a name next to "Offer sent" or "Rejected" tells it a great deal. Who is in a Slack channel is decided by the organisation that runs that workspace, not by us, and we set out how to handle that in our guidance for recruiters.
What the integration asks for and what it keeps. The Slack app requests bot-level permissions only: links:read to be told when a link to our domain is posted, links:write to return the card, chat:write to send its own notifications and update its own cards, and commands for the /oliapp command. It does not read channel message history. Workspace and user authorisation tokens are held in a VPC-isolated database in our European infrastructure, encrypted at rest; channel identifiers are not stored; the text of a comment in transit is deleted automatically within 24 hours. A comment written from Slack is recorded in the candidate's discussion under your own account. Uninstalling the app revokes and deletes the workspace token immediately and invalidates the linked user sessions.
Where the data goes. The card, and anything a recruiter types into Slack, passes through Slack's own infrastructure. Slack is a service your organisation contracts with, not one we chose on your behalf: you install the integration into your workspace, and Slack handles that data under your agreement with them. We are not responsible for what Slack does with it, and Slack is not one of our sub-processors — see §11.
Guest Mode — using the extension before you sign up. You can install the extension and use part of it without creating an account: keyword highlighting, and a limited number of outreach templates. While you do:
the templates, keywords and stopwords you create are held in your browser's local storage on your own device. They are not sent to us, and we cannot read them.
we receive product-analytics events about what you do — that a template was inserted, that highlighting ran, how many keywords you have — as counts and identifiers only. The words themselves, and the text of your templates, are never sent.
you are identified to us only by an anonymous identifier. If you arrived through our post-install welcome page, that identifier is the one that page generated, so that we can tell that one person installed the extension and then used it.
When you later create an account and sign in, the extension offers to move your local templates, keywords and stopwords into your new account; from that point they are stored on our servers and this policy applies to them in full. At the same moment the anonymous identifier is linked to your account, which means the activity recorded before you signed up becomes attributable to you.
If you never sign in, the data on your device stays on your device, and uninstalling the extension removes it. Deleting it earlier is a matter of clearing your browser's storage for the extension.
23How to Complain
Contact us first at privacy@oliapp.co, though you're never required to. You may also lodge a complaint directly with a supervisory authority. For data we control, this is Poland's:
Urząd Ochrony Danych Osobowych (UODO) ul. Stawki 2, 00-193 Warszawa, Poland Telephone: +48 22 531 03 00 Email: kancelaria@uodo.gov.pl Electronic submissions: through ePUAP (/UODO/SkrytkaESP) uodo.gov.pl
If you are elsewhere in the EU or EEA, you may complain to the authority where you live, where you work, or where you believe the infringement took place.
24Changes to This Policy
Each version carries a version number and an effective date. Previous versions are archived and linked from our change-history page. Where a new version differs materially, we notify active users at least 30 days before it takes effect.
25Contact Us
If you have a question related to this Privacy Policy, our processing activities, or your data subject rights under GDPR and other applicable laws, you can contact us directly using the following details:
Our email: privacy@oliapp.co
Address: FreySoft Poland Sp. z o.o., ul. Domaniewska 45, 02-672 Warszawa, Poland