Working with OliApp Lawfully

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

This page is practical guidance, not a contract and not legal advice. Your obligations are set out in the Terms of Use and the Data Processing Agreement; what follows is how recruiters usually meet them while working in OliApp.

We wrote it because the rules place most of the responsibility on you, and a product that says "that's your responsibility" without showing how is not much help.

If anything here conflicts with advice from your own lawyer, follow your lawyer.

1Who is responsible for what

Two roles, and almost everything follows from which one applies.

You are the controller for the candidates in your workspace. You decided to collect their data, you decided why, and you decide how long to keep it. The law puts the duties on you: telling candidates you hold their data, answering their requests, deleting when you should.

We are the processor. We hold and process that data on your instructions, under the Data Processing Agreement. We do not decide what to do with it, we do not use it for our own purposes, and we do not contact your candidates.

We are the controller only for data about you — your account, your billing, your activity in the product, your support conversations. That part is described in our Privacy Policy.

One consequence worth stating plainly, because it surprises people: OliApp never emails your candidates. No "you have been added to a database" notices, no automatic disclosures. If a candidate needs to hear from someone, it is you.

2When you add a candidate yourself

Someone whose data you collected without them giving it to you directly — sourced from a profile, imported from a spreadsheet, passed on by a colleague — has to be told. This is the obligation people most often miss, and it is the one that most often turns into a complaint.

What you have to tell them: who you are, where you got their data, what you intend to do with it, how long you will keep it, and that they can ask for a copy, ask for corrections, object, or ask to be deleted.

When: within a month of getting their data, or at your first contact with them if that comes sooner. In practice this means: put it in your first message.

How much: a short paragraph. Not a policy, not a wall of text.

A paragraph you can paste into your first outreach

I found your profile on [where] and I'm contacting you about [role] at [company]. I've saved your name, contact details and professional background in our recruiting system so I can follow up. [Company] decides how your data is used and keeps it for [period]. You can ask me for a copy of what we hold, ask me to correct it, object to us holding it, or ask us to delete it — just reply to this message. You can also complain to your local data protection authority.

Adjust it to your voice. Keep the five facts: who, where from, why, how long, how to say no.

When you do not have to notify

There is an exception where the person already has the information. It is narrower than people hope — "they put their CV on a job board, so they know recruiters will contact them" is not enough on its own. Treat the exception as rare and notify by default.

3When a candidate applies through Job Ads

Here the notice is already handled. The application page shows a notice naming your organisation as the controller, explaining what happens to the application, and offering two optional, unticked choices: keeping the CV on file for other roles, and allowing referrals to other recruiters.

Your part is to make sure the controller details on your Job Ads page are accurate and current. They are what the candidate sees, and they are how the candidate reaches you.

4Free-text notes — the single most useful section on this page

A note you write about a candidate is personal data about that person, in the same way their phone number is.

Three consequences that catch people out:

  • They can ask to see it. A request for a copy of their data covers your notes about them.
  • It does not survive deletion. When a candidate is erased, free-text notes go with everything else, because a note identifies a person even with the name stripped out: "strong Java dev, fintech background, asked for 6k, declined over relocation" is a description of one specific individual.
  • Some of it should never have been written. A note recording health, pregnancy, religion, ethnicity, political views, sexual orientation or trade-union membership is a special category of data, and it needs a legal ground that a recruiting note almost never has.

Do not write

Health or disability. Pregnancy or family plans. Religion. Ethnicity or nationality as a judgement rather than a fact relevant to the role. Political views. Union membership. Sexual orientation. Comments about appearance, accent, age, or personality that you would not say to the person's face in a room with their lawyer in it.

Write instead

The pipeline stage. A structured rejection reason from the list. Dates. Facts the candidate told you about what they are looking for. Anything you would be comfortable reading back to them.

This is not only a legal point. Structured fields survive erasure; free text does not. If your team's institutional memory lives in free text, erasure takes it. If it lives in stage history and reason codes, erasure leaves it intact.

5Rejections

Use the reason codes rather than a free-text explanation.

A structured code — "did not meet the experience requirement", "withdrew", "salary expectation outside range" — records why you stopped, survives a deletion request, and is far easier to defend if the candidate ever asks why they were rejected. A free-text sentence saying the same thing does none of those three things.

6The Referral Pool

The Referral Pool lets recruiters ask each other for help finding someone. Three things about it matter for compliance, and all three are in your hands.

Participation is per candidate. Each candidate record carries a participation state. Candidates you added manually participate by default; candidates who came through a third-party job board do not, because those boards generally restrict use to the vacancy applied for; candidates who applied through Job Ads participate only if they ticked the box.

You can exclude anyone, at any time. If a candidate objects, or you simply judge it inappropriate, set their state to excluded. It is final — the record stays out of the pool from then on.

The platform never hands over contact details. When another recruiter is looking for someone with a matching background, we tell you. Whether to put that person forward, and whether to pass on anything about them, is your decision, taken outside the platform. There is no "share this candidate" button, and there will not be one.

7When a candidate contacts you directly

They ask for a copy of their data, or a correction. That is yours to answer, as the controller. Everything we hold for you is visible and exportable in the product.

They ask you to delete them. Delete the record from your workspace with the ordinary controls. That removes them from your base. It does not affect other organisations that may hold the same person independently — their copies are theirs, collected separately.

They want to disappear from OliApp entirely. Send them to our request page. We will verify that it is really them, then locate and erase every record of that person across every organisation using OliApp. You do not need to do anything, and you will not be asked to approve it.

They object to being in the Referral Pool but want to stay in your base. Set their participation state to excluded. Nothing else changes.

Timing

A person who makes a request is entitled to an answer within a month. You can extend it by two more months for complicated requests, but you have to tell them inside the first month and say why. The clock starts when the request arrives, not when you get round to it.

8If you connect Slack

The Slack integration lets your team look at a candidate, change a status and leave a comment without leaving Slack. It is the same data under the same permissions — someone who cannot see a candidate in OliApp cannot see them in Slack.

One thing works differently, and it is worth knowing before you connect it.

When anyone pastes a link to a candidate into a channel, Slack expands it into a small card showing the candidate's name, their current pipeline status — Screening, Shortlisted, Offer — the time that status changed, and buttons to change it or open the discussion. That card is part of the message, so everyone in the channel sees it: colleagues with no OliApp account, and anyone from outside your company in a shared or Slack Connect channel. Slack offers no way to show a preview to some members of a channel and hide it from others.

Contacts, CV files, photographs and notes are never in the card, and clicking through to the full profile requires an OliApp session with permission to see that candidate — anyone else gets an access-denied page.

The status is the part to think about. A name alone tells a channel little. A name next to "Offer sent" or "Rejected" tells it that a specific person is at a specific point in a specific hiring process, and that is not always something the candidate would expect to be visible to a room.

What to do about it, in order of effort:

  • Pick the channels. Keep the integration in channels whose membership you would be comfortable showing a candidate list to. A recruiting team channel, not a company-wide one.
  • Watch shared and guest channels. Slack Connect channels and channels with guest accounts include people outside your organisation. A card is visible to them too.
  • Paste deliberately. If a particular candidate is sensitive — a confidential search, someone still employed and discreet about looking — do not paste their link into a channel. Say "the second candidate on the shortlist" instead.
  • Tell your team. Most of the risk here is someone pasting a link without thinking about who is in the room.

Who is in your Slack channels is yours to decide; we have no visibility of it and cannot restrict it from our side.

9Message synchronisation

If you turn on message sync, conversations with a candidate are summarised and the original message text is deleted once the summary exists. The summary is factual: what was discussed and agreed. We do not infer mood, sentiment or intent from it, by design. Summaries run only on an OpenAI API key that you enter in your own settings, so the conversation text goes to OpenAI in the United States under the terms of the OpenAI account the key belongs to (Privacy Policy §11.1).

Two things to keep in mind:

  • It is off by default and only you can turn it on. An administrator cannot enable it on your behalf. That is deliberate: a conversation has two people in it, and the other one did not agree to anything.
  • Free text in messages is still free text. Everything in section 4 applies to what you write in a chat with a candidate, not just to notes in the record.

10How long to keep candidate data

You decide. We do not set retention periods for data we hold on your behalf, and we do not delete it on our own initiative — we delete when you tell us to, and in any event when your account closes.

"Forever" is not a retention period. Pick one you can justify: the time it takes to fill the role, or a defined period after which an unplaced candidate is removed or asked whether they want to stay on file. Write it down, and put the same figure in the notice you send candidates — section 2 asks you for it.

11Where to go

Questions about this guide, or about how OliApp handles data: privacy@oliapp.co

A candidate asking to be removed from the whole platform: send them to Your Data Request

Contractual detail: Terms of Use, Data Processing Agreement

What we do with data, in full: Privacy Policy