A resume database is the store of candidate records a staffing or recruiting agency builds in its applicant tracking system (ATS). Each record holds the resume, contact details, skills and work history, and links to the jobs the candidate was submitted to, the interviews and the placements. The agency controls the database, but candidates keep privacy rights over their own information.
- A resume database is more than resumes: it links candidates to jobs, submissions, interviews and placements.
- California privacy law covers job applicants, so candidates can ask to see or delete their records.
- EEOC rules require keeping application records for one year; plan retention around that.
- Keep background check reports out of any export or reuse.
What is a resume database?
A resume database, also called a candidate database, is the collection of people a staffing or recruiting agency has sourced, screened or placed. Recruiters search it first when a client sends a new job, because a candidate already on file is faster to place than one found from scratch.
The same term is used for job-board products that let employers search posted resumes. This page is about the first kind: the agency's own records, built over years of recruiting.
A third term, resume dataset, usually means a file of resumes collected for research or for training software. That is a different thing from a working database, and the rules below explain why turning one into the other takes care.
What does an applicant tracking system store?
An applicant tracking system stores the resume and everything that happened to the candidate afterward. One staffing software vendor, Bullhorn, publishes its data model, and it shows the usual shape (Bullhorn entity reference). The names differ between systems, but the records are much the same.
| Record | How the vendor describes it | What it usually holds |
|---|---|---|
| Candidate | "Represents a person seeking a job." | Contact details, resume text, skills, work history, education, certifications, recruiter notes |
| Job order | "Represents an open job to be filled." | Client, title, description, pay or bill rate, status |
| Sendout | A candidate's information "is sent to a ClientCorporation to be evaluated for a particular job" | Which resume went to which client, and when |
| Job submission | "Represents a formal submission of a Candidate for a particular job." | Status history: submitted, interviewing, rejected, offered |
| Interview | An appointment whose type is "Interview" | Date, attendees, feedback notes |
| Placement | "Represents a successfully filled job" | Start date, rates, contract terms, end date |
| Client company and contact | "Represents a company that is a client of a company" | Hiring managers, agreements, fee terms |
The value for a recruiter is in the links between records: which candidates were sent for which jobs, who was interviewed, who was placed and how long the placement lasted.
Who owns the candidate data in a staffing agency database?
The agency controls the database it built, but "ownership" is the wrong frame for the personal information inside it. Three sets of rights sit on top of each other.
- The candidate: privacy law gives the person rights over their own information, whatever system it sits in. What the candidate was told when the resume was collected sets the limits of what the agency may do with it.
- The agency: it holds the compiled database, its notes and its placement history, and may protect them as confidential business information.
- The software vendor: the subscription agreement says who may access the data, how it can be exported and what happens when the contract ends. Read the data-return clause before you need it.
- Clients and job boards: client agreements often restrict what the agency may do with job details and rates, and resumes pulled from a job board stay subject to that board's terms of use.
What does privacy law say about reusing candidate data?
Three US rules matter most for a staffing agency. This page is general information, not legal advice.
California's privacy law covers candidates. The California Privacy Protection Agency says a consumer "includes California residents that are employees or job applicants" (CPPA), and the Attorney General confirms that the old exemption for employment-related personal information "expired on December 31, 2022" (California Attorney General). The law applies to for-profit businesses that meet one of its size thresholds, one of which is buying, selling or sharing the personal information of 100,000 or more California residents or households. Covered candidates have "the right to opt-out of the sale or sharing of their personal information" and can ask a business to delete what it collected.
Federal record-keeping rules pull the other way on retention. "Any personnel or employment record made or kept by an employer", including "application forms submitted by applicants and other records having to do with hiring", must be kept for one year, and where a discrimination charge has been filed the relevant records must be kept "until final disposition of the charge or the action" (29 CFR 1602.14). The EEOC's summary is short: its regulations "require that employers keep all personnel or employment records for one year" (EEOC).
Background checks are their own category. Under the Fair Credit Reporting Act a consumer reporting agency may furnish a report only for listed purposes "and no other", and for employment purposes "only if" the user has certified it followed the law's notice and authorization steps (15 U.S.C. 1681b). A report obtained to place one person in one job should not be reused for anything else. When the agency no longer needs it, the FTC's Disposal Rule requires "reasonable measures to protect against unauthorized access" during disposal (16 CFR 682.3).
| Rule | Who it protects | What it means for the database |
|---|---|---|
| CCPA, as amended by the CPRA | California applicants and candidates | Honor requests to know, delete and opt out of sale or sharing; say in the privacy notice what the data is used for |
| 29 CFR 1602.14 (EEOC) | Applicants and employees | Keep application and hiring records at least one year; longer while a charge is open |
| Fair Credit Reporting Act | Anyone with a background report on file | Use reports only for the purpose they were obtained for; dispose of them securely |
How to export a resume database: a worked example
Most systems offer three ways out: list exports from the user screens (usually CSV), an API, and a full data copy from the vendor on request. List exports are fine for a mailing list but drop the links between records. For a move to a new system, or a full archive before a sale or closure, ask for all the tables with their record IDs.
A fictional 25-person agency leaving its ATS asks the vendor for a full copy and receives the files below. The counts are made up.
| File | Rows | Key columns | Check before you rely on it |
|---|---|---|---|
| candidates.csv | 212,400 | candidate_id, date_added, status, skills, location, owner | Do counts match the system? Are deleted and opted-out candidates excluded? |
| resumes (folder) | 188,900 files | candidate_id in the file name | Original files as well as parsed text; watch for missing attachments |
| job_orders.csv | 9,300 | job_id, client_id, title, date_opened, status | Rates and client names are confidential under most client agreements |
| submissions.csv | 61,700 | submission_id, candidate_id, job_id, status, status_date | Every candidate_id and job_id should resolve to a row in the other files |
| placements.csv | 4,150 | placement_id, candidate_id, job_id, start_date, end_date | End dates are often blank; say so instead of guessing |
| notes.csv | 1,480,000 | note_id, candidate_id, author, date, text | Free text holds the most sensitive details; review before any reuse |
Keep the export under your retention schedule: see the data retention policy template. If the agency is winding down, export company records before closing covers the order to do it in.
Common mistakes with a candidate database
These are the habits that cause trouble when a database is moved, sold or reused.
- Exporting candidates only. Without submissions and placements the file is a contact list, not a hiring history.
- Losing record IDs, so resumes can no longer be matched to submissions.
- Keeping candidates who asked to be deleted, or who opted out, in an old export.
- Leaving background check reports, ID documents, I-9 forms or medical notes attached to candidate records.
- Treating resumes copied from a job board as the agency's own, when the board's terms limit reuse.
- Reading recruiter notes last. Free-text notes are where age, health, family and other protected details end up.
- Deleting application records before the one-year EEOC period has run.
A resume database as a data asset
AI data buyers have asked Origin for records from US recruiting agencies. The interest is less in resumes, which are easy to find, than in what only an agency has: which candidates were sent for which jobs, who got interviews, who was placed and how long they stayed.
Several things must come out or be checked first. Names, contact details, employer names that point to one person and free-text notes need removal or review: see how to de-identify company data before licensing. Background check reports and identity documents stay out entirely. Candidates who opted out or asked for deletion are excluded, and your privacy notice has to allow the use; data licensing under GDPR and CCPA explains the notice and opt-out points. Client agreements and job-board terms need a read for confidentiality and reuse limits.
Origin is an independent data partner that helps companies get their data bought. A buyer may pay Origin when a deal closes.
Does your company hold records like these? See what your data is worth.
Common questions
What is a resume database used for?
Recruiters search it to find candidates for new jobs before sourcing from outside. In a staffing agency it also records which candidates were submitted, interviewed and placed, which shows what worked for each client.
What is the difference between a resume database and a candidate database?
In practice they are the same thing. "Candidate database" stresses the full record in the applicant tracking system, with notes, submissions and placements, while "resume database" is also used for job-board products that sell resume search.
Does the CCPA apply to job applicants and candidates?
Yes, for businesses the law covers. California regulators say consumers include job applicants, and the exemption for employment-related information expired on December 31, 2022.
How long does a staffing agency have to keep resumes and applications?
EEOC rules require employers to keep personnel and employment records, including application forms and other hiring records, for one year, and until final disposition if a discrimination charge is filed. Other laws and contracts can require longer.
Can a staffing agency sell its candidate database?
It depends on what candidates were told, on privacy law where they live, and on client and job-board terms. Selling identifiable records of California candidates triggers opt-out rights. De-identified hiring history raises fewer issues but still needs review.
Is a resume dataset the same as a resume database?
No. A resume dataset is a file of resumes prepared for research or for training software. A resume database is a working recruiting system. Turning one into the other means removing identifiers and checking the rights of the people in it.
How do you export candidates from an applicant tracking system?
Use list exports for small jobs, the API for regular syncs, or ask the vendor for a full data copy. For a complete history, get candidates, jobs, submissions, interviews, placements and notes with their record IDs.
Sources and further reading
- Bullhorn REST API: entity reference (Candidate, JobOrder, JobSubmission, Sendout, Placement)
- California Privacy Protection Agency: frequently asked questions
- California Attorney General: California Consumer Privacy Act (CCPA)
- 29 CFR 1602.14: preservation of records made or kept (EEOC)
- EEOC: Recordkeeping requirements
- 15 U.S.C. 1681b: permissible purposes of consumer reports (Fair Credit Reporting Act)
- 16 CFR 682.3: proper disposal of consumer information (FTC Disposal Rule)
