Second-Party Data: A Recruiter's Guide to Shared Data
Where shared candidate data comes from in recruiting, what to agree before it changes hands, and how to contact the people in it

Recruiters handle second-party data whenever a client or partner shares its own candidate records, even if no one calls it that. Examples include a client's finalists from last year's search, a partner agency's file for a split placement, and a career center's résumé book.
Second-party data is another organization's first-party data, shared directly with you under an agreement. The source knows the people in it, but those people gave their details to that organization for its own purpose. That's why the terms of the exchange, and how you first contact each person, matter as much as the records.
Key takeaways
- Second-party data is a partner's own records shared with you directly, so you can ask where each record came from.
- Clients, partner agencies, career centers, and event organizers are the main sources, and candidates an agency submits become the client's shared data.
- Agree the purpose, fields, notice to the people in the data, retention, opt-outs, security, onward sharing, and placement credit before records change hands.
- On first contact, say where you got someone's details and confirm what's current before you add them to your own records.
What is second-party data?
Second-party data is information one organization collected through its own relationships and then shares with a specific partner on agreed terms. It sits between the data you collect yourself and the data you buy. You didn't gather it, but you know who did and can ask them where a record came from or how old it is.
That direct relationship separates it from third-party data, which a broker collects from many places and sells to anyone who pays. In recruiting, it might be a client's silver medalists, a partner agency's notes for a joint search, or an association's member list. The data remains the partner's, and your agreement sets what you can do with it.
First-, second-, and third-party data compared
First-, second-, and third-party data differ mainly in who collected the information and how close that collector is to the people it describes. Zero-party data, a term from marketing, is the narrowest category. It covers what a person intentionally tells you, such as pay expectations or a start date. The table compares all four in recruiting terms.
| Type | Who collects it | Recruiting example | Main strength | Main limit |
|---|---|---|---|---|
| Zero-party | The candidate tells you directly | Pay expectations and start dates the candidate states | Comes straight from the person | Covers only what you thought to ask |
| First-party | You through your own systems and conversations | Applicant tracking system records and call notes | You know its origin and date | Limited to people who already engaged with you |
| Second-party | A client or partner sharing its own records | A client's finalists from a similar past search | You know the source and can agree terms | Collected for the partner's purpose |
| Third-party | A broker or aggregator with no direct relationship | Purchased contact lists | Broad coverage of people you've never met | Origin and consent can be unclear |
Your first-party data lives in your applicant tracking system (ATS), your candidate relationship management (CRM) system, your careers site, and your own conversations. Much of the value in candidate data comes from knowing when you collected it and what the person agreed to. With shared records, you only know if the partner tracked it, so it's worth asking early.
Where recruiters get second-party data
Shared data comes from the organizations recruiters already work with, though the exchange rarely gets labeled as a data arrangement.
- Clients: A client may share past applicants and silver medalists for a similar role, an org chart, or its hiring plan. The client's own employee referral program submissions can also point an agency recruiter to people the client's staff already know.
- Partner agencies: In a split placement, the agency representing the candidate shares that person's records with the agency that holds the job.
- Campus career centers: Résumé books from students who opted in are a familiar part of campus recruiting. The career center can tell you what students agreed to.
- Events and associations: Organizers sometimes share attendee or member lists that people agreed to pass on, for example to sponsors of a hiring event.
- The reverse flow: Every candidate an agency submits becomes second-party data for the client. Whatever you told that candidate about how their details would be used travels with that submission.
In-house recruiters encounter the reverse flow when agencies submit candidates, so it's reasonable to ask what each candidate agreed to. Agencies see it from both sides, so treating shared data as part of client relationships lets you set terms once rather than for every search.
Strengths and limits of shared candidate data
The main strength of shared candidate data is context. A client can tell you that a finalist interviewed in the spring and was strong on systems design, which a purchased list can't. You can also ask follow-up questions when a record looks incomplete.
The limits come from the same place: the partner collected the data for its own purpose, so the people in it may not expect to hear from you. An unexplained call can feel intrusive even when the role is a good fit. The records are only as clean as the partner keeps them, so duplicates and outdated job titles can come along too. Run the same CRM hygiene checks you'd apply to your own database before importing anything.
Coverage is narrow as well. A client's past applicants reflect who applied to that client, not the wider market, so shared data works best alongside your own sourcing. The terms may also limit the records to a single search, and everyone on your team who can open the file needs to know that.
When a partner offers a file, a few questions help you decide whether it's worth taking. How old are the records, and how were the people told their details might be shared? Does the partner's intended purpose match the search you're running? If the partner can't answer clearly, a smaller set of records with a known history may serve you better than a large file you can't explain.
What to agree before data changes hands
Before a client or partner sends anything, agree in writing what the data is for and how both sides will handle it. These terms protect the people in the records and keep the commercial side clear if a shared candidate is hired.
- Purpose: Name the specific search or use the data is for.
- Fields: List the fields being shared, limited to what that purpose needs.
- How people were told: Ask how people in the data learned their details might be shared, and whether they agreed.
- Retention: Set how long you'll keep the records and when you'll delete them, for example, when the search closes.
- Opt-outs and deletions: Agree how a request made to either side reaches the other, and how quickly.
- Security: Decide how the file moves between you and who on each side can open it.
- Onward sharing: Confirm the data won't be passed to anyone else, including your other clients.
- Placement credit: Agree who gets credit, and any fee, if a shared candidate is hired for this role or a later one.
Placement credit can be left out when privacy feels like the main concern, but without it, neither side knows who is owed a fee later. Your staffing agency contract is the natural home for fee and ownership clauses, with privacy terms in the same document or an addendum.
Legal points to check before you use shared data
Privacy law reaches candidate data in some states, and California's California Consumer Privacy Act (CCPA) speaks directly to sharing it. The state's privacy agency says the CCPA covers California residents who are employees or job applicants. Its exemption for employment-related information expired at the end of 2022. The law applies to covered businesses, not every recruiter.
The CCPA regulations, effective January 1, 2026, require an agreement when a business sells or shares personal information with a third party. The agreement must name the limited, specified purpose; limit the recipient to it; and require the same level of privacy protection the CCPA requires. It must also require the sharing business to take reasonable steps to prevent unauthorized use. A recipient without a compliant contract can't collect, use, or keep the data.
Whether an exchange counts as a sale or sharing, or as service-provider work for the other business, depends on the arrangement. That's a question for counsel. Other states have their own privacy laws, and the checklist above is sound practice either way.
Work from candidates who opted in
Book a demoHow to use second-party data well
When you first contact someone from a shared file, name the organization that shared their details and the context, such as an application they made there. People can take that approach, and it gives them a natural moment to opt out, which you then pass back to the partner.
Consider a client that gives an agency the finalists from last year's search for a similar role. Before calling, the recruiter checks with the client how those applicants were told their details might be shared. Each call opens by naming the client and the earlier application, and the recruiter records only what each person confirms about their current role and interest.
Record the source and the date in a dedicated field in your ATS or CRM. Anyone on the team can then see where a record came from. Keeping shared records apart from your main database until the person responds also makes it simpler to delete them when the agreed purpose ends.
Once someone confirms their details and agrees to stay in touch, that information becomes your own first-party data. Adding people to your talent pool at that point, rather than importing the partner's file, means every record reflects permission they gave you. From there, staying in touch works the same way it does with anyone you sourced yourself.
Agree the terms before you start outreach
Shared records are valuable because they come from organizations that know the people in them, and those people expected their details to stay with the partner. Written terms settle the open questions with the partner, and telling each person where you got their details settles them with the candidate. When the next file is offered, start by asking how the people in it were told their details might be shared.
Start searches from opted-in candidates
Book a demoFrequently asked questions
Is a résumé a candidate sends you second-party data?
No. Details a candidate gives you directly are your first-party data, and preferences they state on purpose are sometimes called zero-party data. The résumé becomes second-party data for a client only when you share it, for example by submitting the candidate to a client.
Can I share candidate data with a client without asking the candidate?
Tell candidates how their details will be used before you submit them, and get their agreement to each submission. Whether the law also requires specific notice or consent depends on where the candidate lives and whether privacy rules cover your business, so check with counsel.
About the author

Founder & CEO of Rotto, building tools that help tech recruiters source better candidates, faster.






