How Long Should an Offshore Recruitment Team Keep Applicant Data?

Research question

When a Philippines-based recruitment support team works inside a buyer's applicant tracking system, how long should it keep resumes, interview notes, messages, and related candidate records? A single answer such as "two years" is tempting, but it is rarely defensible across every record and jurisdiction. The useful question is narrower: which business or legal purpose still applies to each record, who owns that decision, and what event starts the disposal clock?

This matters to buyers because distributed recruiting creates copies easily. A sourcer exports a list for review. A coordinator downloads a resume to arrange an interview. A manager writes notes in a private document. The applicant tracking system may retain its own version. Deleting one visible profile does not remove those copies. A retention rule must therefore describe records, locations, owners, and disposal evidence, not just a number of months.

What the authorities establish

The Philippines Data Privacy Act requires personal information to be kept only as long as necessary for the purpose for which it was obtained, for legal claims, for legitimate business purposes, or as law otherwise provides. The National Privacy Commission's implementing rules also require a retention schedule and procedures for erasure or disposal. Its 2017 advisory opinion on applicant and former employee records does not prescribe one universal duration. It directs organizations back to necessity, purpose, legal claims, legitimate business needs, and applicable law.

That distinction is important. "We might recruit this person someday" is not the same as a documented active-talent-pool purpose with a defined review period and a way for the person to exercise privacy rights. A record needed to defend a current hiring decision may have a different retention basis from an old sourcing export. A buyer operating across borders also needs advice for the laws that apply to its entity and candidates. For example, the U.S. Equal Employment Opportunity Commission tells covered small businesses to retain applications and interview notes for at least one year, while other obligations can require different periods.

These sources support a method, not a universal legal conclusion. Offshore Resourcing readers should have their privacy or employment adviser approve the final schedule for their facts.

Start with a record map

List the records produced at each recruiting stage before assigning any period. A workable map separates at least these categories:

The map should record every approved copy. "Resume in ATS" and "resume attached to coordinator email" are two locations even when the content is identical. If a recruiting assistant needs a local working file, set a short operational expiry and a rule for moving the authoritative record back to the system of record. Shared drives should not become permanent shadow archives.

Assign purpose before duration

For each record, write a plain purpose statement. "Recruitment" is too broad. Better examples include: evaluate this application for requisition 482; preserve the hiring panel's recorded basis for its decision; schedule interviews for an active candidacy; or maintain an opted-in talent pool for a stated class of future roles.

Then test the purpose against four questions. Is the record still necessary? Is a statute, regulator, contract, or active claim relevant? Has the person been told how the data will be used? Can a less detailed record meet the same need? The answers may produce different rules for different fields within one candidate profile. A hiring outcome and requisition identifier may remain necessary while a duplicate attachment or free-form note does not.

Purpose also controls access. A scheduling coordinator may need a candidate's name, contact channel, availability, time zone, and accommodation routing instructions. That does not mean the coordinator needs background-check findings, compensation history, or every interviewer's private notes. Retention and least privilege reinforce each other: data that no longer exists cannot be exposed, and data that remains should be visible only to roles that still need it.

Use event-based clocks

Calendar rules such as "delete every file after 24 months" are hard to apply when nobody knows the starting event. Define the event beside the duration. Possible events include application closure, rejection notice, accepted offer, withdrawal, last candidate contact, end of a documented talent-pool period, or final resolution of a claim hold.

An event-based clock also handles reopened candidacies. If the candidate applies to a new requisition, create a new application relationship rather than silently extending every old record. Link what remains relevant and permitted. Do not reset a retention clock merely because a recruiter viewed the profile.

Legal holds need an explicit override. The ordinary disposal job should pause only the affected records, with an authorized owner, reason, start time, and release decision. Recruiters and offshore coordinators should not decide whether a dispute requires preservation. They should follow the hold instruction and escalate ambiguity.

Control working copies

Retention programs often fail outside the main platform. Review these locations during workflow design:

• exported candidate spreadsheets used for calibration or pipeline meetings;
• resumes in personal downloads folders;
• calendar descriptions and meeting recordings;
• interview notes in private documents;
• chat threads that contain candidate details;
• integration logs and automation error queues;
• backups governed by a separate recovery cycle.

The buyer can reduce sprawl by using links instead of attachments, disabling unnecessary exports, limiting bulk downloads, and providing an approved temporary workspace. A deletion workflow should cover failed jobs and disconnected integrations. If a system cannot delete a required field on schedule, document the limitation, restrict access, and decide whether the tool is appropriate for the process.

Backups require a truthful rule. Immediate selective deletion from an immutable backup may be impractical, but that does not justify restoring expired records into live use. Record the backup cycle, protect the media, prevent ordinary access, and make sure restored data passes through the current deletion rules before it returns to production.

Measure the routine, not just the policy

A policy can look complete while the queue quietly accumulates. The operating evidence should show which scheduled records were reviewed, deleted, anonymized, held, or escalated. Useful measures include overdue disposal items by system, unresolved ownership gaps, failed deletion jobs, unapproved exports found, and time from an approved privacy request to completion.

Sample the evidence. Select closed requisitions from different months and trace the candidate record across the ATS, mailbox, calendar, drive, and reporting layer. Confirm that retained fields still have a purpose and that disposed copies are absent from ordinary access. Do not copy personal data into the audit report. Use record identifiers, dates, system names, and status.

Aggregate reporting may remain useful after person-level detail expires. Proper aggregation or anonymization is more than hiding a name. Small groups, unusual roles, free-text comments, and combinations of attributes may still identify someone. The privacy owner should define when data is sufficiently de-identified for the intended report.

A buyer-owned implementation sequence

The buyer should first name the privacy decision owner and identify the jurisdictions, contracts, and claim periods that apply. Next, the recruiting operations owner maps records and systems. Legal or privacy reviewers approve purpose and duration. System administrators translate the schedule into platform rules. The offshore recruiting team receives task-level instructions: where to work, which copies are forbidden, when to delete temporary files, and where to escalate a request or hold.

Run the first disposal cycle on a bounded sample. Review failures before expanding automation. A bulk deletion should have an approved scope, recoverability decision, operator record, and exception report. Automation can execute a policy, but it cannot resolve an unclear purpose or ownership dispute.

For a new recruitment administration lane, include retention behavior in onboarding and sample review. Give the coordinator a fictional closed requisition with records in several locations. Ask them to identify the authoritative record, calculate triggers from the approved schedule, flag the legal-hold boundary, and prepare a disposal exception. This tests practical judgment without exposing real applicants.

Limitations and decision boundary

This analysis draws on privacy and employment guidance available on the checked date. It does not determine which jurisdiction governs a particular company, candidate, contract, or dispute. Statutory periods and regulator expectations can differ, and a buyer may have valid obligations that are not visible to its staffing provider.

The offshore team can maintain inventories, run approved reports, remove authorized working copies, and prepare exceptions. The buyer remains responsible for deciding purposes, legal bases, durations, holds, candidate notices, and responses to privacy rights. A responsible provider should refuse to invent a duration when the approved schedule is silent.

Conclusion

Applicant data retention works when each record has a stated purpose, an authoritative location, an event that starts its clock, and an owner who can approve disposal or a hold. The practical test is not whether the policy contains a number. It is whether the buyer can trace a closed application through every system and explain why each remaining field is still there.

Sources

Sources checked October 5, 2026.

1. Republic Act No. 10173, Data Privacy Act of 2012, Official Gazette
2. Implementing Rules and Regulations of the Data Privacy Act, National Privacy Commission
3. Advisory Opinion No. 2017-024 on retention periods, National Privacy Commission
4. Retention of Personal Data, National Privacy Commission
5. NIST Privacy Framework
6. NIST SP 800-53 Rev. 5, Security and Privacy Controls
7. Recruiting, hiring or promoting employees, U.S. Equal Employment Opportunity Commission
8. Best Practices of Private Sector Employers, U.S. Equal Employment Opportunity Commission
9. OECD Guidelines on the Protection of Privacy and Transborder Flows of Personal Data
10. 36 CFR Part 1226, Implementing Disposition, U.S. eCFR

FAQ

Can the recruiting coordinator choose a retention period?

No. The coordinator can apply an approved schedule and report gaps. The buyer's authorized privacy, legal, and records owners decide the rule.

Should an unsuccessful candidate's resume be kept for future roles?

Only when the buyer has an approved purpose and lawful process for that use, including a defined review or expiry point. A vague possibility of future interest is not an operational schedule.