Reusing resumes downloaded from job boards: what the terms allow

What do job board terms usually allow you to do with downloaded resumes?#

Job board terms usually allow a subscriber to search, view and download resumes to recruit the people in them, and little beyond that. The resume database is licensed to your firm as a working tool for filling roles, not handed over as an asset your firm then owns.

The restrictions that commonly surround that core permission are familiar once you look for them: no resale or redistribution, no sharing with other firms, no scraping or bulk export, no building a competing database, and limits on keeping downloaded material after access ends. Sourcing extensions and contact-enrichment tools often add their own clauses on how long their data may be stored and whether it may be combined with other sources.

Wording differs by vendor and changes over time, and an enterprise agreement negotiated by a larger firm may read very differently from the click-through terms a solo recruiter accepted. Read the version in force when the records were downloaded, and the current version, before deciding anything.

Why a downloaded resume is different from one a candidate sent you#

A downloaded resume is different because the candidate gave it to the job board, not to your firm, so the job board's terms sit between you and the record. A resume a candidate emailed to a recruiter, or submitted through your own career page under your privacy notice, arrives through a direct relationship that your firm documented.

That distinction matters most when a record is reused for something other than filling a specific role. ATS platforms such as Bullhorn typically keep a source field for each candidate, but recruiters often fill it inconsistently and bulk imports can overwrite it, so check the field's reliability before relying on it.

Which reuses are most likely to conflict with the terms?#

The reuses most likely to conflict with job board terms are the ones that move a resume outside the subscriber's own recruiting. Submitting a downloaded candidate to a client for an open role is usually the intended use; nearly everything else deserves a closer look.

AI use needs particular care. Some newer vendor terms address machine learning directly, while older terms say nothing about it, and silence is not permission. Where the wording is ambiguous, counsel should decide whether to ask the vendor in writing or simply exclude the records.

• 1Sharing resume files or profile data with affiliates, partner agencies or offshore sourcing teams not covered by your subscription.
• 2Transferring the candidate database to a buyer in a sale of the firm or its assets.
• 3Keeping downloaded resumes after the subscription lapses, or re-downloading in bulk before cancelling.
• 4Merging enrichment data such as personal emails and mobile numbers permanently into ATS records.
• 5Using resumes to build or train internal AI tools, or licensing records that contain them to third parties.
• 6Loading resumes into marketing lists for outreach unrelated to a specific role.

Vendor terms and privacy law are two separate tests#

Vendor terms and privacy law are two separate tests, and a resume has to pass both before it is reused. Vendor terms answer whether your firm may use the record that way; privacy law answers whether the person in the record may be processed that way.

Removing names does not settle either test. A de-identified resume is still a copy of material obtained under the vendor's terms, and work histories with rare titles, employers and dates can point back to one person even without a name.

How to tag third-party-sourced records before any reuse#

Tagging third-party-sourced records means marking every candidate record with where it came from and under which agreement, so any later reuse can filter it out in one step. Most of the work is cleaning up fields your ATS already has.

Firms that cannot reconstruct the source of older records should mark them unknown, and unknown should be handled exactly like restricted. Guessing a source in order to widen what can be reused creates a record that is hard to defend and harder to unwind once material has left the firm.

• 1List every job board, resume database, sourcing extension and enrichment tool the firm has paid for, including tools individual recruiters bought on a company card.
• 2File the agreement or terms version for each, with the subscription start and end dates.
• 3Convert the ATS source field into a fixed picklist and backfill it from parse logs, import batches and email headers where possible.
• 4Flag attachments separately from structured fields, because a downloaded resume file can sit on a profile the candidate later updated directly.
• 5Record whether the candidate later engaged directly, such as applying to a posting or acknowledging your privacy notice.
• 6Adopt a default rule: third-party-sourced with unclear terms means excluded from any reuse beyond recruiting.

Illustrative: an IT staffing firm sorts its database before a license review#

Illustrative: a fictional IT staffing firm runs Bullhorn, holds subscriptions to two resume databases and lets recruiters use a browser sourcing extension. Leadership wants to license de-identified job order and placement workflow records and asks the general counsel which candidate material could be part of the package.

The general counsel finds the source field blank on most older records and resume files from the databases saved straight onto candidate profiles. Rather than argue record by record, the firm decides that no resume text, attachment or enrichment field will enter the package. The package carries only job order requirements, stage timestamps and outcome codes, with candidates represented by tokens. The firm also locks its source picklist so new records are tagged on entry.

How SourceX treats third-party-sourced records#

SourceX treats records obtained under someone else's terms as out of scope unless the supplier can show those terms allow the proposed use. In the SourceX five-step transaction, that question is settled in the Rights step, before any Preparation work starts, and the supplier approves the final scope.

For each package that proceeds, the SourceX Evidence Packet records provenance and licensing rights alongside permitted use, the privacy record and release authorization. For a staffing firm, that usually means documenting that resume databases and sourcing tools were excluded and showing how the remaining records were created inside the firm's own workflow.