Refolk
FrameworkProcess, data, and compliance

The Saved-Profile Notice Read: First Message, Standalone, Exempt, or Purge

Grade any batch of saved profiles on six dimensions and assign one of four notice verdicts, with a dated deadline, the notice content, and the record to keep.

24 min readLast reviewed November 14, 2026Read as Markdown

Key takeaways

  • Under GDPR and UK GDPR Article 14(3), the notice deadline for a saved profile is the earliest of three dates: one month after saving, the first message, or the first disclosure to a client or hiring team.
  • An agency that submits a CV to a client on day 3 owes the candidate a privacy notice by day 3, not day 30, because Article 14(3)(c) moves the deadline to the first disclosure.
  • The disproportionate-effort exemption fails wherever a contact route is held: Poland's regulator fined a data company just over PLN 943,000 for emailing only about 680,000 of roughly 6 million people and relying on a website notice for the rest.
  • A Polish court held that disproportionate effort cannot be measured as financial or organisational cost, so an exemption memo that argues volume or price is not a valid assessment.
  • In Refolk's index, 455 UK sourcer profiles sit against 5 named privacy roles at UK staffing firms, which is why written per-batch rules beat legal review of each record (the ratio is indicative only).
  • California gives no grace period: if a notice at collection is required and was not given at or before collection, the business must not collect, though regulation 7012(h) removes the duty for indirect collection with no sale or sharing.

Every week sourcers save profiles they found on professional networks, code hosts and the open web. Someone in recruiting or revenue operations then has to decide what privacy notice each batch is owed before a legal deadline passes. This guide gives you a way to make that decision. You score a batch on six dimensions, assign one of four verdicts, and log the deadline date, the notice content, and the record that proves you did it. It covers EU and UK GDPR Article 14 and California's notice-at-collection rule. It is an operating standard, not legal advice. Where the law is unsettled I say so, and I name the question your counsel should answer once for all batches.

What does the saved-profile notice read decide?

For each saved record, it decides which of four things happens and by what date: a privacy notice inside the first outreach message, a standalone notice, a documented exemption, or deletion. The rest of this guide is there to make that assignment repeatable.

Two terms first. An Article 14 notice is the privacy information GDPR requires you to give people whose data you got from somewhere other than them. Every sourced profile falls into that group. A controller is the party that decides why and how the data is used. The UK ICO's draft recruitment guidance explicitly covers agencies, head-hunters and consultancies, and it says recruiters are "likely to act as controllers in most circumstances". So the duty to give notice is yours, not the duty of the platform where you found the profile.

VerdictUse whenDeadlineRecord to keep
First messageRoute held, contact dated before deadlineAt first message, before any submittalNotice version, send time
Standalone noticeRoute held, no contact before deadlineDay 30 or first submittal, if earlierNotice version, send time
ExemptNo route, non-cost reason, written assessmentAssessment signed before day 30Dated, signed assessment
PurgeEverything elseDay 30Deletion log, suppression entry

Grade each record separately, but run the read once per weekly batch so every record in the batch shares a review date and a reviewer. Expect most batches to split across several verdicts.

Which deadline applies to a saved profile?

Under GDPR and UK GDPR, the deadline is whichever of three triggers comes first: one month after you obtained the data, your first message to the person, or your first disclosure of the data to anyone else. Under California's rules, a notice at collection, where one is required, is due at or before collection. There is no grace period.

RegimeTriggerDeadline
GDPR / UK GDPR 14(3)(a)Data obtainedReasonable period, at most 1 month
GDPR / UK GDPR 14(3)(b)First communicationAt that message (cap still 1 month)
GDPR / UK GDPR 14(3)(c)First disclosureAt the disclosure (cap still 1 month)
CCPA reg. 7012(d)CollectionAt or before collection
CCPA reg. 7012(h)Indirect collection, no sale or sharingNo notice at collection required

Saving a profile starts the one-month clock. A first message moves the deadline earlier, to the moment of that message. A submittal also moves it earlier, to the moment of submittal. The deadline never moves later. The Article 29 Working Party's transparency guidelines (WP260) are explicit: "if the first communication with a data subject occurs more than one month after obtaining the personal data then Article 14.3(a) continues to apply." So a plan to contact someone in six weeks does not give you six weeks.

Agencies most often miss the disclosure trigger. WP260 says that when data is "disclosed to another recipient (whether a third party or not)", the notice must be given "at the latest at the time of the first disclosure." The words in brackets matter. Sharing a profile with your own hiring manager is a disclosure, just as sending a CV to an agency client is. Agencies often submit a candidate before they contact them, so for an agency the binding deadline is usually the submittal date, not day 30.

In this guide, "day 30" is shorthand for one calendar month after the date the data was obtained. Log the actual calendar date. A month that starts in February is shorter than 30 days.

Where sources disagree on the clock

  • Does the one-month cap apply to triggers (b) and (c)? The European Banking Federation argued that WP29 "extends the one month time limit provided for Article 14.3(a) to Article 14.3(b) and Article 14.3(c)" further than the text supports. This guide follows WP260, because that is the reading regulators have published.
  • Is the month a retention period? Some recruiting-software guidance says to delete the record immediately if no email goes out within a month. Some compliance commentary treats the one-month window as the retention period itself. My view is that the month is a deadline for the notice, not an allowance for keeping data. If no notice has gone out by day 30, delete the record. Once a notice has gone out, you keep the data for the period, or by the criteria, that the notice states.

California works differently

California's exemption for job-applicant data stopped applying on 1 January 2023, after extensions in 2021 and 2022, so candidate data is now covered. Regulation 7012(d) is blunt: "If a business does not give the Notice at Collection to the consumer at or before the point of collection of their personal information, the business shall not collect personal information from the consumer." Regulation 7012(h), however, removes the duty for a business that "neither collects nor controls the collection of personal information directly from the consumer" if it "neither sells nor shares" that information.

How do you score a batch on the six dimensions?

Give every record one coded value on each of six dimensions. The codes produce the verdict, not anyone's view of the candidate. Two graders working from the same record and the same codes should reach the same verdict. If they do not, the dimension where they differ is the one missing evidence.

DimensionValuesWhat it provesWhen it lies
D1 JurisdictionEU, UK, CA, OtherWhich clock and content applyStale location; remote workers
D2 Contact intentDated in window, Dated later, NoneWhether first message beats day 30"Next quarter" logged as a plan
D3 Contact routeHeld, NoneWhether notice is possible at allPlatform messaging logged as "none"
D4 Onward disclosureNone, Planned (date), DoneWhether the deadline moves earlierHiring-team share called "internal"
D5 Automated rankingNone, Stored only, Feeds shortlistWhether notice must explain logic"A human decides" over a top-slice list
D6 Data beyond profileProfile only, Enriched, Personal socialCategories and sources to nameEnriched fields with no source URL

How to score each dimension:

  • D1 Jurisdiction. Tag the record from the location signals in the profile. If the signals conflict or are missing, grade the record as EU/UK, because the stricter clock is the safe default. A California resident who works for an EU employer gets both tags and both sets of rules. "Other" means this read does not cover the record, but you still capture its source and date.
  • D2 Contact intent. Only a calendar date counts. "When the req opens", "next quarter" and "talent map" all score None.
  • D3 Contact route. Held means the record includes an email address, a phone number, or a direct-message route such as InMail. A platform message button counts. None means you genuinely cannot reach the person.
  • D4 Onward disclosure. Record any planned share with a client, hiring manager or hiring team, with its date. Done means the share has already happened. If no notice went out before it, the record is a timing breach. Send the notice now rather than grading the record.
  • D5 Automated ranking. Feeds shortlist means a score decides, or in practice decides, which profiles a human looks at. A score that is stored but never used is Stored only. If nobody uses it, delete it.
  • D6 Data beyond the public profile. Profile only means fields copied from the profile you saved. Enriched means extra fields from other recruitment platforms or code hosts, each with its own source URL. Personal social means anything taken from personal social media.

From scores to verdict

Apply these rules in order:

  1. Clean D6. Remove any field taken from a personal social media profile. The ICO's draft guidance says "you should not search for candidates on their personal social media profiles, even when these are public-facing." Remove any enriched field that has no source URL, or find it again from a recorded source.
  2. Set the deadline. It is the earliest of day 30, the D2 date and the D4 date.
  3. California records. If counsel's position says 7012(h) does not cover this batch, the notice was due at or before collection. Purge any record saved without one.
  4. Route held, contact dated on or before the deadline: First message.
  5. Route held, any other contact plan: Standalone notice by the deadline. If no one will commit to sending it, Purge.
  6. No route held: Purge by default. Use Exempt only with a signed assessment that gives a reason other than cost or volume.
  7. Content additions, whatever the verdict. If D5 is Feeds shortlist, add the ranking-logic content to whichever notice goes out. If a UK record will be contacted by direct message, use a template that has passed PECR review.

Route and intent decide most verdicts

Contact dated before deadlineNo dated contact
Intent without a route
Find a route before the deadline or purge; a contact plan you cannot carry out is just a talent map
Ready to reach
Notice in the first message, sent before any submittal
Unreachable, no plan
Purge by day 30; exempt only with a signed assessment that gives a non-cost reason
Reachable, parked
Standalone notice by the deadline, or purge
No contact route heldContact route held
Holding a contact route rules out the exemption, so for reachable people the only question is whether the notice goes in a dated first message or on its own.

What must the notice contain for this batch?

Every notice needs the Article 14 core. The batch's scores then add content: the source of the data, any recipients from D4, the ranking logic when D5 is Feeds shortlist, and the California elements for California records. So the scores change what the notice says as well as when it goes out.

The core, from Article 14(1) and 14(2):

  • The identity and contact details of the controller and any representative, and the contact details of the data protection officer (DPO).
  • The purposes and the legal basis, plus the legitimate interests relied on where that is the basis.
  • The categories of data held.
  • The recipients, and any transfers to countries outside the UK or EU.
  • The retention period, or the criteria that set it.
  • The person's rights: access, correction, deletion, objection, withdrawing consent, and complaining to a regulator.
  • The source: "from which source the personal data originate, and if applicable, whether it came from publicly accessible sources."

Where Article 22 applies, Article 14(2)(g) adds "meaningful information about the logic involved, as well as the significance and the envisaged consequences of such processing." Whether a particular ranking tool falls under Article 22 is a legal question. This read includes the logic content for every Feeds shortlist record anyway. Including it costs a few sentences. Leaving it out when it was needed makes the notice defective for the whole pool.

A California notice at collection covers the categories of data, the purposes, whether each category is sold or shared, the retention period for each category, and a link to the privacy policy. The link must go directly to the relevant section. A link to the top of the policy does not meet the rule.

How a batch's scores widen the notice

  1. Jurisdiction overlay
    California elements and a link to the right policy section; PECR-cleared wording for UK direct messages
  2. Ranking logic
    The logic, its significance, and its consequences when a score feeds shortlisting (D5)
  3. Recipients
    The named client or hiring team when a submittal is planned (D4)
  4. Source statement
    Where each field came from and whether it was public (D6)
  5. Article 14 core
    Controller, DPO, purposes, legal basis, categories, retention, rights
Every notice carries the Article 14 core, each scored dimension adds a layer on top, and the outer layers are the ones most often missing.
First-message notice block (EU/UK)
How I found you, and what I hold
I am [name], [role] at [company], contactable at [email or postal address]. The data protection officer for [company] is reachable at [DPO email].
Source: I found your public profile on [source, e.g. a professional network or code host] at [profile URL] on [date obtained]. It came from a publicly accessible source.
What I hold: [categories, e.g. name, current title, employer, work history, public repositories].
Why: to consider you for [role type] roles. Legal basis: legitimate interests, namely [the interest, e.g. matching experienced engineers to open roles].
Recipients: [named client or hiring team], and only [after you agree / from date]. Transfers outside [UK/EEA]: [none / destination and safeguard].
How long: [period or criteria, e.g. deleted 30 days after this message if you do not reply].
Ranking: a tool ranks profiles using [factors]. A lower rank means [consequence, e.g. a recruiter may not review your profile for this role].
Your rights: reply to this message to ask for access, correction or deletion, to object to this use, or to withdraw consent where I relied on it. You can also complain to [supervisory authority].
Full notice: [link to the candidate section of the privacy notice]

Fill every bracket from the batch record. Delete the Recipients and Ranking lines only if D4 and D5 both score None.

Who makes this call, and how much privacy oversight is there?

In most staffing firms, ops makes the call, because there are very few named privacy specialists to pass a batch to. That is why written per-batch rules work better than legal review of each record.

In the index behind Refolk, professional profiles matching sourcer job titles far outnumber privacy roles at staffing firms. The data comes from two separate queries, so treat the comparison as a rough guide, not a ratio you can cite precisely.

Measure (Refolk's index)UKGermany
Profiles matching sourcer titles455177
"Talent Sourcer" in a sample of 252 (8%)7 (28%)
Clearly procurement titles in that sampleAt least 30
Top employers of sourcersDeloitte 3, HSBC 2Volkswagen Group Services 5, Siemens 3
DPO or privacy manager at staffing firms50
455 to 5
UK sourcer profiles against named privacy roles at UK staffing firms, in Refolk's index
That is roughly 91 sourcers per privacy profile, but treat it as a rough guide only, because the two queries used different filters.

Limits on reading this table:

  • The UK has 2.6 times as many sourcer-titled profiles as Germany, but the UK count includes some procurement sourcers.
  • Germany's zero privacy roles probably reflects the English-only search titles not matching German job titles. It does not mean German staffing firms have no DPOs.
  • The five UK privacy profiles are at Staffline, Michael Page, RiTem, Galago Group and ctrg.

The practical point: with numbers like these, legal review of every record is not realistic. What a firm can sustain is a written rubric, one counsel position for each open question, and a sample audit of each batch. Build the judgement into the codes once, so that the person grading on a busy afternoon is applying rules rather than interpreting law. If you are setting up an escalation path, it helps to see how peer agencies staff the privacy role. Refolk can show you who holds it from a single plain-English question.

When does the disproportionate-effort exemption apply?

For commercial sourcing, almost never. Article 14 includes an exemption for cases where giving notice would take disproportionate effort. It fits cases where giving notice is genuinely impossible, not merely expensive. Polish courts have read it narrowly enough that holding any contact route rules it out.

The leading case is the Polish data protection authority's (UODO's) first GDPR fine, issued in March 2019 against a business-data company. The facts:

  • The company held data on about 6 million company owners.
  • It emailed only the roughly 680,000 people whose email addresses it held, and published a privacy notice on its website for everyone else.
  • It estimated that informing everyone would cost about PLN 30m, which was more than its turnover.
  • The fine was just over PLN 943,000.

The Warsaw Voivodeship Administrative Court held that "by merely publishing the information obligations required by the GDPR on its website, the company had not sufficiently complied". It also held that disproportionate effort "cannot be translated as a financial or organizational cost". The court upheld the decision for active and temporarily suspended sole traders. It annulled the decision for people who had run a business in the past, and annulled the amount of the fine. Public sources do not establish why past business owners were treated differently, so do not read anything into it. On 19 September 2023 the Supreme Administrative Court (NSA) dismissed the company's appeal in case III OSK 2538/21. It said the exemptions "should be interpreted restrictively and, as a rule, should be applied to the processing of data for public purposes."

The contrast case is a later UODO decision about a civic company-register portal. There the regulator accepted the exemption, citing "the civic nature of the processing and the lack of direct contact data for all data subjects." So the exemption was refused where contact data was held and cost was the argument. It was accepted where the processing served a civic purpose and contact data was missing. A commercial talent pool usually serves no civic purpose, and its members can usually be reached.

If you can message the person, you can notify them. Holding a contact route ends the exemption argument.

If you still grade a record Exempt, WP260 says "This assessment should be documented by the data controller in accordance with its accountability obligations." A valid assessment, signed before day 30, states:

  • Why the notice cannot be given, with a reason other than cost, volume or staff time.
  • Which contact routes were searched for, and the evidence that none exist.
  • Any public or civic purpose the processing serves.
  • What safeguards are in place instead, such as a public notice and keeping the fields to a minimum.
  • Who signed it, and the date.

How do you run the read on a weekly batch?

Run the eight steps below once per weekly batch. The sourcer provides the evidence at save time, and ops applies the codes and verdicts. Each step has a test for when it is done, so an auditor can check it without asking anyone what they meant.

The weekly saved-profile notice read

  1. Capture source and date at save
    The sourcer records the source URL, the date obtained, location signals, and the fields taken for every profile when saving it. Done when every record has a source and a date.
  2. Tag jurisdiction for the batch
    Once per weekly batch, ops tags each record EU, UK, California, or Other, grading unclear records as EU/UK. Done when every record carries a tag.
  3. Record contact intent and route
    The sourcer gives a planned contact date as a calendar date and says whether a route is held, or writes None. Done when every record shows a date or None and a route or None.
  4. Check onward disclosure
    The recruiter flags any planned share with a client, hiring manager, or hiring team, with its date. Done when every planned submittal is scheduled after that record's notice.
  5. Check automated ranking
    Ops confirms whether any ranking score feeds shortlisting and codes each record. Done when every Feeds shortlist record is set to receive the ranking-logic content.
  6. Assign the verdict and deadline
    Ops applies the verdict rules in order and writes the deadline as a calendar date. Done when every record has one of four verdicts and every Exempt record has a signed assessment.
  7. Deliver and log the notice
    Send the notice in the first message or as a standalone notice, using a PECR-cleared template for UK direct messages. Done when each record holds the notice version and send timestamp.
  8. Run deletion and suppression at day 30
    Delete every Purge record, and any record whose notice did not go out by its deadline, and add each one to the suppression list. Done when the deletion log matches the purge list.

Step 1 is where batches usually fail, because a profile saved without its URL and date cannot be graded correctly later. The notice has to name the source, and the clock runs from the date obtained. If you source with Refolk, save the profile URL it returns into the source field when you save the profile, not afterwards. Reconstructing sources a week later is where the dates start to drift. The suppression list in step 8 stops the same person from being sourced again, which would quietly restart their clock.

Batch verdict record
BATCH
Batch ID:
Week of:
Graded by / second grader on sample:
Counsel position on CA 7012(h) (version, date):
PER RECORD
record_id | source_url | date_obtained | day30_date | D1_jurisdiction | D2_contact_date | D3_route | D4_submittal_date | D5_ranking | D6_data_scope | deadline | verdict | notice_version | sent_at | purge_due | purged_at
EXEMPTION ASSESSMENT (verdict = Exempt only)
Why notice cannot be given (not cost, not volume):
Contact routes searched and found absent:
Public or civic purpose served, if any:
Safeguards in place:
Signed by / date (must be before day30_date):

One header per batch and one line per record. Keep it with the batch for as long as any record in it survives.

How does the read go wrong?

Eight failure modes account for most breaches. Each one looks reasonable when it happens, and each has a check that takes seconds once the batch record exists. Run all eight checks on every batch, not only on batches that look risky.

  1. A website-only notice treated as the exemption. It looks like "our privacy page covers talent pools". It fails whenever contact data is held, which is the lesson of the Polish case. Check: does the record hold an email address, an InMail route or a phone number? If it does, there is no exemption.
  2. An exemption argued on cost or volume. It looks like an assessment saying "notifying 4,000 people a week is not feasible". The court held that cost is not effort. Check that the written assessment gives a reason other than money, headcount or volume.
  3. Submittal before notice. A client sees the CV on day 3 and the notice goes out on day 20. This is the most common agency breach, because the team is watching the one-month clock, not the disclosure clock. Check: compare the client-share timestamp with the notice timestamp for every submitted record.
  4. "Contact planned" with no date. Talent maps sit untouched until day 30 passes. Check: no planned date means the verdict is Purge or Standalone notice, never First message.
  5. A ranking score kept but not disclosed. The score quietly decides who reaches a human. Check whether the score feeds shortlisting. If it does, the notice needs the 14(2)(g) content on the logic, its significance and its consequences.
  6. A California record handled under GDPR timing. Someone assumes California also allows a month. It allows no time at all where a notice at collection is required. Check that the 7012(h) conditions are met (indirect collection, no sale or sharing), and cite counsel's written position, before relying on the carve-out.
  7. A UK direct message cleared under GDPR only. The ICO's draft says "direct messaging on social media constitutes direct marketing and electronic mail", which brings in PECR. Check that the template has passed PECR review, not only GDPR review.
  8. Personal social media scraped into an enriched record. An enrichment step pulls in fields from personal profiles that the ICO's draft says you should not search. Check each field's source URL against your list of approved recruitment platforms.

Two false positives are worth naming as well. A "no route" grade often hides a platform message button, which makes a record look eligible for exemption when it is not. A "just internal" share with a hiring manager looks like no disclosure, but WP260's "whether a third party or not" makes it one. Both errors push records towards a later deadline than they really have, so when graders disagree on D3 or D4, resolve it towards the earlier deadline.

How do you keep the read current?

Three things can change and should be re-checked on a fixed calendar schedule: the status of the ICO's recruitment guidance, California's open questions, and the EU Digital Omnibus. None of them, on the sources checked for this guide, changes a verdict. Each could change the content or the timing, so check them on that schedule rather than waiting to hear about a change.

  • ICO recruitment guidance. The ICO first issued its recruitment draft on 12 December 2023 and consulted on it until 5 March 2024. A later version is reported as dated 9 July 2025. At the last check it was still marked as a draft under review, so no final text is established. Check the ICO's recruitment and selection pages, and if the final text changes the advice on personal social media or direct messages, update rule 1 and the PECR step.
  • California. The Attorney General sent inquiry letters about HR data to employers, announced on 14 July 2023, so candidate data is being enforced. Consumer requests must be answered within 45 days. Ask counsel to look again at the two open questions (direct collection and sale) whenever the regulations text is amended, and give the position a new version number in the batch record.
  • The EU Digital Omnibus. It was published on 19 November 2025 as proposal COM(2025) 837 and is not law. The amendments found concern Article 13, for example dropping the notice where the person already has the information, plus a research exemption. Commentators note that "a nearly identical exception already exists in Article 14". Check the legislative status tracker before treating any of it as a planning input.

Each time you re-check, double-grade a sample of the latest batch. Two people should get the same verdicts. Where they do not, tighten the wording of the dimension they disagreed on.

Before you close a batch

  • Every record has a source URL and a date obtained, and day 30 is written as a calendar date.
  • Every record has a jurisdiction tag, and records with unclear signals are graded EU/UK.
  • Every deadline is the earliest of day 30, the planned contact date, and the planned submittal date.
  • No client or hiring-team share timestamp comes before its notice timestamp.
  • No record with a contact route held is graded Exempt.
  • Every Exempt record has an assessment, signed before day 30, that gives a reason other than cost or volume.
  • Every record whose ranking score feeds shortlisting received the ranking-logic content.
  • Every UK direct-message template has passed PECR review.
  • No field in the batch came from a personal social media profile.
  • Every California record cites counsel's versioned 7012(h) position, and every California notice link goes to the right policy section.
  • Every Purge record is deleted and on the suppression list by its date, and the deletion log matches.

Questions practitioners ask

How long can I keep sourced candidate data without contacting the person?

Without a privacy notice, no longer than one month, under GDPR and UK GDPR Article 14(3)(a). A plan to contact them later does not extend this, because WP260 says the one-month limit still applies if first contact comes after it. If no notice has gone out by day 30, delete the record. Once a notice has gone out, you can keep the data for the retention period or criteria that the notice states.

Can the privacy notice go in my first recruiter message?

Yes, as long as the message goes out within one month of saving the profile and before you share the profile with a client or hiring team. Article 14(3)(b) makes the first communication a deadline of its own. The message must carry the Article 14 content, including where the data came from and whether that source was public. In the UK, a direct message on social media also counts as direct marketing under PECR, so the template needs PECR review.

Does the disproportionate effort exemption cover a talent pool I don't plan to contact?

Almost never. In the case behind the Polish regulator's first GDPR fine, the court held that disproportionate effort cannot be measured as financial or organisational cost. It also held that a website-only notice was not enough where contact data was held. The Supreme Administrative Court later said the exemptions should be read restrictively and, as a rule, apply to processing for public purposes. If any contact route is held for a commercial talent pool, send a standalone notice or purge the record.

Do I need a CCPA notice at collection for sourced candidates?

Possibly not, but that depends on two unsettled questions. Regulation 7012(h) removes the duty for a business that does not collect directly from the consumer and does not sell or share their data. Public sources do not establish whether saving a public profile counts as direct collection, or whether a fee-bearing submittal counts as a sale. If the carve-out does not apply, the notice is due at or before collection with no grace period, so get a written position from counsel.

Does sharing a sourced profile with my own hiring manager start the notice clock?

Yes. WP260 says Article 14(3)(c) applies when data is disclosed to another recipient "whether a third party or not", and the notice must go out no later than that first disclosure. An internal share with a hiring team counts, and so does an agency submittal to a client. Log the share timestamp and check that it never comes before the notice timestamp.

Does the EU Digital Omnibus change notice rules for sourced candidates?

Not according to the sources checked for this guide. The Omnibus, published as proposal COM(2025) 837, is not law. The amendments found concern Article 13 notices, for example dropping the notice where the person already has the information. Commentators note that a nearly identical exception already exists in Article 14. Check the legislative status tracker before you treat any of it as a planning input.

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next