Skip to content
Essentiq

Guides

GDPR when sourcing candidates in Sweden: a practical guide

How to source passive candidates in Sweden within GDPR: legitimate interest, informing candidates, data minimisation, retention and their rights.

By EssentiqUpdated 7 min read

Short answer

You can contact passive candidates in Sweden under GDPR, usually on the basis of legitimate interest (Article 6.1(f)), as long as you only process relevant professional data, tell the person who you are and where you got their details no later than your first message, delete what you no longer need and respect objections at once. This guide is practical advice, not legal advice.

On this page

Sourcing means processing personal data about people who never applied to you. That is allowed under GDPR, but it comes with duties. This guide turns the rules into a routine you can actually follow as a recruiter in Sweden.

Who is responsible for what

GDPR separates the controller, who decides why and how personal data is processed, from the processor, who processes it on the controller's behalf.

When you search for candidates, save them to a project, add notes and contact them, you decide the purpose: filling your role. For that processing, you (or your employer, or the agency you work for) are a controller. Essentiq's own privacy policy says Essentiq AB acts as a data controller for the professional profile data it collects and makes searchable. Essentiq's terms also say plainly that the customer is responsible for making sure its own use of candidate data complies with data protection law.

In practice that means two layers of responsibility:

  • Essentiq answers for how the profile data in the search index is collected and kept, and handles requests about that data at support@essentiq.io.
  • You answer for what you do with the people you pick out: why you save them, what you write in notes, how you contact them and how long you keep them.

Most sourcing relies on legitimate interest (Article 6.1(f)). Consent rarely works, because you can't ask for consent before the first contact, and the first contact is the processing.

Legitimate interest needs three things to hold:

  1. A real interest. Filling a specific role with a suitable person is a legitimate business interest.
  2. Necessity. The data you process has to be needed for that purpose. Work history and skills, yes. Family situation, no.
  3. Balance. Your interest must not override the person's rights. Professional data that people have chosen to publish, used for a professional purpose they can reasonably expect, usually passes. Scraping private details or chasing someone who said no does not.

Write this reasoning down in a short legitimate interest assessment (LIA). Half a page per type of processing is often enough. Essentiq does the same for its index: its privacy policy says it relies on legitimate interest for publicly available professional data and keeps a documented LIA that is available on request.

Tell people where you got their data

When you collect data about someone from somewhere other than the person, Article 14 requires you to inform them. If you use the data to contact the person, you must inform them at the latest at the first communication. Otherwise within a reasonable time, and no later than one month.

For sourcing, the practical rule is simple: your first message carries the information. It should say, briefly:

  • who you are and which company you represent (the controller)
  • why you are contacting them (a specific role)
  • where you found their details, in general terms
  • that they can say no, and that you will then delete their details
  • where to read more: a link to your own privacy notice

You don't need to paste a legal text into a LinkedIn message. A short, friendly line and a link does the job.

First message that informs the candidateLinkedIn or email · first contact

Hi {{candidate.first_name}},

I'm {{sender.first_name}} and I'm recruiting for a {{open_position.title}} role. I found your professional profile while searching for people with your background, and your experience looks like a close match.

Would you be open to hearing a bit more? If not, just say so and I'll delete your details and won't contact you again. You can read how we handle personal data here: [link to your privacy notice].

If your outreach is a sequence, put this information in the very first step that sends something to the person. Follow-ups don't need to repeat all of it, but keep the "just say no" option in every message. See writing outreach messages that get replies for the rest of the copy.

Collect less, keep it shorter

Data minimisation

Only save and note what you need for the role. A good test: would you be comfortable if the candidate asked for a copy of everything you hold and read it out loud? Notes like "strong on Python, open to Gothenburg, available from March" are fine. Guesses about health, family plans, religion, union membership or political views are not.

Sensitive data

Special categories of data under Article 9 (health, ethnic origin, religion, sexual orientation, political opinions, trade union membership, biometric data) need an explicit exception that ordinary sourcing doesn't have. Don't record them, and don't search on proxies for them. Essentiq's privacy policy states that it does not collect sensitive personal data in its index.

Retention and deletion

GDPR doesn't give a fixed number of months, but you need a rule and you need to follow it. A common approach:

  • people who never reply: delete after the process ends, or after a set period such as a few months
  • people who say no: delete right away, and keep at most a minimal record so you don't contact them again
  • people who say "maybe later": keep only with their agreement and note when they said it

Pick your periods, write them in your privacy notice and put a recurring reminder in your calendar to clean up projects.

Respect the candidate's rights

People you source have the same rights as any data subject. The ones you will meet most often:

  • Right of access. They can ask what you hold about them. Answer within one month.
  • Right to erasure. If there is no longer a reason to keep the data, delete it.
  • Right to object. When someone objects to processing based on legitimate interest, for example by saying "please don't contact me", stop. In sourcing there is rarely a compelling reason to continue.
  • Right to rectification. Correct details that are wrong.

Essentiq makes the "stop" part easier: when a person replies on LinkedIn or by email, every sequence to that person stops automatically, across your projects. If the reply is a no, delete them from your favorites.

Requests about the profile data in Essentiq's own index go to Essentiq at support@essentiq.io. The privacy policy says Essentiq may ask for proof of identity and responds within 30 days. See your data and privacy.

No automated decisions

Article 22 limits decisions based solely on automated processing that significantly affect people. AI search and ranking help you find and sort profiles; a person still decides who to contact and who to hire. Essentiq's privacy policy says the same: it automates search and organisation of public data, does not make automated decisions with legal or similar effects, and recruitment decisions are made by people.

Keep it that way in your process. Don't reject candidates only because a score said so. Look at the profile.

GDPR principles in practice

PrincipleWhat it means for sourcingWhat to do
Lawfulness, fairness, transparencyA legal basis, and people know you process their dataRely on legitimate interest, write an LIA, inform in the first message
Purpose limitationData collected for one role isn't a free-for-allOne project per role; ask before reusing someone for another role
Data minimisationOnly what the role needsSave the right candidates, keep notes short and professional
AccuracyWrong data must be correctedFix or delete details the candidate tells you are wrong
Storage limitationDon't keep data foreverSet retention periods, clean up projects regularly
Integrity and confidentialityProtect the dataShare projects only with colleagues who need them; don't export lists to personal drives
AccountabilityYou must be able to show complianceKeep your LIA, privacy notice and retention rules in writing

A sourcing routine you can follow

  • You have a written LIA for sourcing, and a privacy notice you can link to
  • Each project is tied to a specific role
  • You only save candidates you actually consider for that role
  • Your first message says who you are, why you are writing, where you found them and how to say no
  • Notes are factual and professional; no sensitive data
  • A "no" or "don't contact me" means stop and delete
  • Access and deletion requests are answered within one month
  • Projects are cleaned up on a fixed schedule
  • Exports with contact details are stored as carefully as the app itself
  • Colleagues who share projects follow the same rules

The Swedish angle

GDPR applies the same way across the EU, but in Sweden the supervisory authority is IMY. It publishes guidance in Swedish and handles complaints. If a candidate complains, it goes to IMY, so being able to show your LIA, your first message and your deletion routine is your best protection.

Swedish candidates also tend to value directness and plain language. A short, honest message that tells them where you found them isn't just compliant; it is more likely to get a reply.

By Essentiq· Published

Put the guide to work

Describe the role, get a ranked shortlist and reach candidates safely, all in one tool.

Free plan · No card needed