How to Use Public Profile Evidence Responsibly in Sourcing

Public professional profiles can help a team find work-related signals, but they are not verified candidate records. Responsible sourcing keeps discovery, evidence review, contact and decisions separate.

Public does not mean proven

Visibility does not prove that a statement is accurate, that an account belongs to the person you have in mind, or that the person consented to recruiting use. It does not prove availability, interest in a role, authorship of every item or unrestricted permission to reuse the material. Profiles may be incomplete, stale or misunderstood. Requirements vary by location, channel, source terms and organisational policy. This is general information, not legal advice: apply current policy and qualified local guidance.

A responsible evidence workflow

Approve the purpose and brief. Record the role, brief version, sourcing purpose, must-haves, nice-to-haves, boundaries and owner. Define what job-related evidence could answer each requirement before reviewing names. Do not collect information merely because it is visible.
Capture a trace. Save the source name, URL, page or section, capture date and source date when shown. Keep a relevant passage; do not copy an entire profile.
Test relevance. Explain which requirement the item relates to and why. A title, employer, keyword or project is a lead, not proof of scope, ability or fit.
Separate wording from interpretation. Store what the source says separately from your job-related reading. Mark the interpretation as candidate-stated, publicly demonstrated, adjacent or uncertain. Never turn "worked on" into "owned" without support.
Check context. Ask what the person owned, the project setting, any established outcome and how recent the evidence is. Compare dates and sources. When sources conflict, preserve both traces and label the criterion contradicted or unresolved until a human checks it.
Use unknown honestly. If the material does not answer a question, label it unknown, not negative or absent. Write one focused verification question and offer comparable candidates the same opportunity to answer.
Collect and share the minimum. Remove sensitive or protected traits, inferred demographics, personality, family, health and personal-life details. Exclude irrelevant proxies such as photos, postcode, accent, school prestige, employer brand or social popularity. Give named reviewers access through the approved channel and record changes.
Control contact records. Before a human chooses contact, check duplicate profiles, prior contact, contact status and do-not-contact or opt-out records. Record the channel, contact owner, decision, date and next action. Public visibility is not consent, and silence is not permission to continue or switch channels.
Correct visibly. Let a reviewer or candidate flag a wrong identity, source, interpretation or date. Keep the original, add the correction, reason, author and date, and revisit affected ranking or decisions.
Review retention and ownership. Set a retention or deletion review date, name who can delete or restrict access, and check controlled copies. A named human owns verification, contact, interview, correction and final decision.

Copyable evidence record

Use a record per material claim and keep it tied to the approved brief.

PUBLIC EVIDENCE RECORD
Role / purpose / brief version / decision owner:
Candidate ID / reviewer / review date:
Source name / exact URL / page or section:
Source date (if shown) / capture date:
Source wording or concise description:
Criterion and relevance to the role:
Context, ownership and recency established:
Interpretation (separate from source wording):
Status: supported / adjacent / unknown / contradicted / unresolved
Verification question / owner / due date:
Minimum data retained / permitted viewers / access review:
Duplicate, prior-contact and opt-out check / date:
Correction history / retention or deletion review date:
Human action / job-related reason / approver:

GitHub needs extra restraint

Repositories, commits, stars, activity graphs and language labels can identify work to inspect. They do not alone prove personal authorship, production ownership or current ability. GitHub explains that contribution credit depends on conditions such as account email, repository status and branch; language statistics are calculated by Linguist and can be affected by vendor or generated files. Read the contribution reference and repository language guidance, checked 19 August 2026, then ask what the person owned and can explain.

Check the repository licence and terms before reusing code, screenshots or text. GitHub's licensing guidance, checked 19 August 2026, notes that public visibility is not an unrestricted reuse right. Do not copy confidential material, credentials, personal-life data or unrelated content into a hiring record or assessment.

Keep the product boundary clear

Talent Summoner is our product for role-brief sourcing and ranking from LinkedIn, GitHub and other public professional sources across 200M+ profiles. Candidate sourcing returns a ranked shortlist with must-haves, nice-to-haves and plain-English reasoning; candidate ranking organises an existing CV set. Humans verify sources, choose whom to contact, interview and decide. It is not an ATS, sends outreach only after explicit user review and confirmation — never autonomously — and its output is not a fairness, privacy or compliance guarantee. See pricing for current options.

Wrong fit

Pause when the purpose, brief, source trace, identity, access owner, contact record or deletion review is unclear. This workflow is also wrong for broad personal profiling, automated rejection or treating public activity as a complete employment history.

FAQ

Does a public profile prove someone is interested in a job?

No. It may provide a job-related discovery signal, but does not prove consent, availability or interest. A human must apply approved contact process and let the person choose.

Is a quiet GitHub profile negative evidence?

No. People may work privately, contribute under another account or choose not to publish work. Mark the criterion unknown and use consistent verification when needed.

Should a contradiction automatically remove a candidate?

No. Preserve the competing sources, check dates and context, ask the named reviewer to resolve the issue and record the job-related decision.

Does Talent Summoner verify public profile claims?

No. Our product helps discover and rank against a role brief. Humans inspect sources, verify material claims, contact candidates, run interviews and decide.

For the next open role, approve one evidence question, complete one record and assign a human owner for verification and retention review. Then start a focused sourcing search with the unknowns visible.

Talent Summoner product facts read from our live candidate sourcing, candidate ranking and pricing pages, verified 19 August 2026. We re-verify this page quarterly — tell us if something changed.

Public does not mean proven

A responsible evidence workflow

Approve the purpose and brief. Record the role, brief version, sourcing purpose, must-haves, nice-to-haves, boundaries and owner. Define what job-related evidence could answer each requirement before reviewing names. Do not collect information merely because it is visible.

Capture a trace. Save the source name, URL, page or section, capture date and source date when shown. Keep a relevant passage; do not copy an entire profile.

Test relevance. Explain which requirement the item relates to and why. A title, employer, keyword or project is a lead, not proof of scope, ability or fit.

Separate wording from interpretation. Store what the source says separately from your job-related reading. Mark the interpretation as candidate-stated, publicly demonstrated, adjacent or uncertain. Never turn "worked on" into "owned" without support.

Check context. Ask what the person owned, the project setting, any established outcome and how recent the evidence is. Compare dates and sources. When sources conflict, preserve both traces and label the criterion contradicted or unresolved until a human checks it.

Use unknown honestly. If the material does not answer a question, label it unknown, not negative or absent. Write one focused verification question and offer comparable candidates the same opportunity to answer.

Collect and share the minimum. Remove sensitive or protected traits, inferred demographics, personality, family, health and personal-life details. Exclude irrelevant proxies such as photos, postcode, accent, school prestige, employer brand or social popularity. Give named reviewers access through the approved channel and record changes.

Control contact records. Before a human chooses contact, check duplicate profiles, prior contact, contact status and do-not-contact or opt-out records. Record the channel, contact owner, decision, date and next action. Public visibility is not consent, and silence is not permission to continue or switch channels.

Correct visibly. Let a reviewer or candidate flag a wrong identity, source, interpretation or date. Keep the original, add the correction, reason, author and date, and revisit affected ranking or decisions.

Review retention and ownership. Set a retention or deletion review date, name who can delete or restrict access, and check controlled copies. A named human owns verification, contact, interview, correction and final decision.