How much do you need to know about a specialist to make a good decision? A progressive professional data disclosure model

The GDPR requires personal data to be adequate, relevant and limited to what is necessary for the purposes for which it is processed. This is the data minimisation principle in Article 5(1)(c). [1]

Article 25(2) goes further by requiring that, by default, only personal data necessary for each specific purpose are processed. The provision expressly refers to the amount of data collected, the extent of processing, the storage period and accessibility. [1]

The European Commission explains the same rule in simpler terms: an organisation should collect and process only the personal data necessary to fulfil the defined purpose. [2]

This does not mean that the law requires a specialist platform to hide a name or photo until a specific moment. The model in this article is a practical interpretation of limiting data and access to it, not a formal obligation created by a single legal provision.

You cannot sensibly answer "which data are necessary?" until you know what the data are meant to achieve.

You need different information when you are:

• browsing hundreds of profiles,
• comparing two people on a shortlist,
• inviting someone to a conversation,
• checking a specific professional authorisation,
• agreeing service terms,
• entering into a contract,
• making a payment or meeting a legal obligation.

Data minimisation does not mean "always show the least possible". It means limiting data to what is adequate and necessary for a specific purpose. [1]

This distinction matters.

If a platform stores a specialist's full name but does not show it to a person viewing the profile, the platform is still processing that data. The GDPR defines processing broadly and includes collection, storage, retrieval, use and disclosure. [1]

Hiding information may reduce its accessibility to specific recipients, which is one of the dimensions named in Article 25(2). It is not the same as not processing the data. [1]

A sound privacy architecture should therefore answer three separate questions:

• what data the platform holds,
• who can access it,
• when and for what purpose it can be disclosed to another party.

Pseudonymisation and anonymisation are not the same.

The European Data Protection Board explains that pseudonymisation reduces the linkability of data to a specific person but does not remove that link completely. Pseudonymised data remain personal data when they can be reconnected to a person with additional information. [4]

That means a profile labelled "Specialist 184", while the true identity is stored separately, does not automatically become anonymous in the legal sense.

Pseudonymisation is a safeguard, not a way to take data outside the GDPR.

The GDPR contains an important nuance that is often oversimplified.

Recital 51 says that photographs should not systematically be treated as special-category data. A photograph falls within the relevant definition of biometric data when it is processed through specific technical means that allow the unique identification or authentication of a person. [1]

This does not mean an ordinary photograph cannot be personal data. It can. It means only that a photograph does not automatically become special-category biometric data merely because it depicts a person.

Research on anonymous job applications shows that limiting identity information can, in some circumstances, reduce discriminatory barriers during initial screening. At the same time, results are context-dependent, and anonymity may simply postpone discrimination or create unintended effects. [6]

So it is not accurate to say:

"hiding the name and photo removes bias."

A claim more consistent with the evidence is:

"limiting some identity information can help focus the first stage on professional criteria, but by itself it does not guarantee an unbiased or better decision."

The OECD describes skills-first approaches as shifting the primary assessment criterion toward skills a person can demonstrate, with qualifications and experience playing a complementary role. The OECD also stresses deliberate efforts to mitigate bias and the use of appropriate assessment methods. [5]

This does not mean the OECD recommends hiding specific profile fields on specialist platforms.

A cautious design conclusion is still possible:

if the purpose of the first stage is to assess the ability to perform specific work, information about skills and evidence of those skills may matter more than some identity information.

First define:

• the problem to solve,
• the tasks to perform,
• the skills that are essential,
• the work evidence that will matter,
• the time, budget and collaboration constraints.

At this stage you need no data about a specific specialist.

This matters methodologically too: the criteria are created before seeing the people who will be assessed against them.

For an initial profile assessment, information such as the following may be enough:

• required skills,
• context in which they were used,
• work samples or outcomes,
• description of actual contribution,
• level of responsibility,
• recency of experience,
• ability to verify part of the evidence.

If a name, photo or exact employment history does not help answer whether someone can perform the specific work, you can consider not using it at this stage.

That is a design decision, not a universal legal duty.

The next layer may contain information that is not evidence of skill but is necessary to see whether collaboration can work:

• availability,
• possible start date,
• service scope,
• pricing model and price,
• communication language where relevant,
• time zone or work location where genuinely relevant,
• organisational constraints.

Price is not evidence of competence, and location is not a measure of quality. They can still be relevant conditions for a specific collaboration.

After narrowing the choice, you do not need to reveal the entire profile automatically.

First identify what is still missing for the next decision.

It may be:

• clarification of a specific project,
• confirmation of the person's own contribution,
• an additional work sample,
• an answer to the same question asked of everyone on the shortlist,
• confirmation of a professional authorisation that is genuinely required.

Missing information should lead to a specific question, not automatically to a lower assessment.

The moment of identity disclosure does not have to be identical in every situation.

It may become necessary, for example, when the parties want to:

• move to direct conversation,
• verify claimed authorship or experience with a particular source,
• check a required authorisation attached to a person,
• prepare a formal engagement.

There is no universal legal rule saying that a name must be disclosed after a fixed number of stages.

A useful criterion is the appearance of a specific purpose that cannot reasonably be achieved without that information.

When the parties actually begin working together, the range of necessary information can increase.

Depending on the type of relationship, jurisdiction and obligations of the parties, data may be needed for:

• entering into or performing a contract,
• operational contact,
• billing and settlement,
• tax or accounting obligations,
• verification required by law or justified by the nature of the service.

Not every project requires the same data set. Regulated sectors or specific legal obligations may require much more.

This article does not replace legal analysis of a particular relationship.

Data minimisation does not end when data are collected.

Article 25(2) of the GDPR also connects data protection by default with the extent of processing, storage period and accessibility. [1]

After a stage ends, ask again:

• is this information still needed,
• who should still have access,
• is there a legal reason to retain it,
• can its visibility be reduced,
• when should it be deleted or reviewed again.

The fact that information was necessary yesterday does not automatically mean it should remain available indefinitely.

Before revealing another piece of information, use a simple five-question test:

1. What exactly is the purpose of this information?
2. Can the decision reasonably be made without it?
3. Would a less precise version of the information be enough?
4. Who genuinely needs to see it?
5. How long must it remain available?

Example: if you only need to know whether collaboration can happen during particular hours, a specialist's exact home address usually does not answer that question directly. A time zone or stated working hours may be enough.

This is not a legal test. It is a practical tool for checking proportionality between information and purpose.

Privacy should not reduce decision quality by replacing missing information with assumptions.

If you need a particular professional fact for assessment, you have three reasonable options:

• ask for it at the appropriate stage,
• use alternative evidence that answers the same question,
• conclude that you do not yet have enough basis to decide.

What is not sound is:

"I cannot see this information, so the result must be poor."

Missing data and negative evidence are different things.

Progressive disclosure has limited value if every internal system user can see all data from the start.

Article 25(2) of the GDPR expressly includes accessibility among the dimensions of data protection by default. [1] The European Data Protection Board's guidelines on data protection by design and by default discuss implementing these principles through appropriate technical and organisational measures. [3]

In practice, separate:

• data the platform needs to operate the account,
• data visible publicly,
• data visible only to a selected party,
• data available to staff or administrators only for a defined purpose.

Interface privacy without corresponding data access control is incomplete.

Suppose an organisation is looking for someone to assess the accessibility of a website.

Stage one
It compares skills, experience with similar audits, sample reports, scope of responsibility and knowledge of the required standards. A name and photo are not necessary to answer every one of those questions.

Stage two
It checks availability in the required period, price, communication language and whether the work can be delivered in the required model.

Stage three
For the shortlist, it asks for clarification of methodology and confirmation of selected experience.

Stage four
Before direct conversation or formal engagement, the parties disclose information needed for identification, contact and formalising the relationship.

This does not prove that this sequence is best in every situation. It simply shows that different decisions can require different layers of information.

1. You hide data from the client, but internally everyone can still access it.

2. You call a profile anonymous even though the platform can easily reconnect it to a specific person.

3. You hide information that is genuinely necessary for a safe or lawful decision.

4. You treat identity disclosure as a reward instead of a response to a specific process need.

5. You assume that hiding a name automatically removes bias.

6. You collect data "just in case" without a defined purpose.

7. You fail to distinguish data needed to assess competence from data needed for contracting or settlement.

8. After a stage ends, you never revisit whether the data still need to remain accessible.

1. What is the exact purpose of each piece of information?
2. Can that purpose be achieved without it?
3. Is a less detailed version sufficient?
4. Is the data needed to assess competence or only for later collaboration?
5. Who should see it at the current stage?
6. Is the profile genuinely anonymous or only pseudonymous?
7. Is missing information correctly distinguished from a negative result?
8. Are all specialists being compared using comparable criteria?
9. Is there a specific process reason to reveal identity?
10. Does a later stage require additional data for contractual, tax, security or legal reasons?
11. Is internal access restricted to people who genuinely need it?
12. Is it clear when the data will no longer be needed or when that need must be reviewed?

Data minimisation is not about making decisions without information.

It is about separating the questions:

what do I need to know now?
what can I verify later?
who needs to see it?
how long will this information be needed?

A practical specialist selection sequence may look like:

problem -> skills -> evidence -> collaboration conditions -> missing information -> identity -> data needed to formalise the relationship -> reassessment of access and retention.

Not every situation needs exactly this order.

The simpler principle is:

disclose and process data because it is necessary for a clearly defined purpose, not merely because the system can collect or display it.

[1] Regulation (EU) 2016/679 - GDPR, especially Articles 4, 5 and 25 and Recitals 39 and 51, EUR-Lex
Open source

[2] European Commission - What data can we process and under which conditions?
Open source

[3] European Data Protection Board - Guidelines 4/2019 on Article 25 Data Protection by Design and by Default, final version of 20 October 2020
Open source

[4] European Data Protection Board - Anonymisation / pseudonymisation
Open source

[5] OECD - A Skills-First Labour Market, Promoting skills-first hiring and talent management, 2026
Open source

[6] IZA World of Labour - Anonymous job applications and hiring discrimination
Open source

Methodology note: the sources cover different areas: data protection law, privacy design, labour markets and research on anonymous recruitment. This article does not claim that findings from recruitment research transfer directly to every specialist relationship. The progressive professional data disclosure model is a practical synthesis, not a formal standard issued by any of the institutions listed above.