IT recruiting agencies privacy

What should you check before sharing hiring data?

Start with the records you plan to send. A role description can explain the work without including a candidate's home address or private interview feedback. For an initial inquiry, share the skills needed, expected hours and hiring contact.

This site is an Opus-owned reference; recommendations are editorial.

Use this page as a checklist for reviewing a hiring partner's data practices. Request the privacy notice that applies to the website you visit and the service you intend to use. Match those documents to the company named in your agreement.

Before submitting a form, check its explanation of how your details will be used. Ask whether your inquiry will lead to marketing messages and how to stop them. Review cookie choices separately from permission to contact you about a role.

For a hiring discussion, talk to Opus about a role.

What records should your privacy review cover?

Review candidate records separately from documents requested during onboarding. Ask the provider to explain the purpose of each requested document and name its intended recipient.

For example, the IRS describes Form W-8 BEN as a certificate of foreign status for individuals for US tax withholding and reporting. Its instructions identify the withholding agent or payer as the recipient in the circumstances described. See the IRS explanation of Form W-8 BEN.

Before sending tax paperwork, confirm the correct recipient with your finance team. Keep it out of general interview folders.

Build a record list for the proposed engagement. Include resumes and interview notes, then add any assessments or recordings you intend to create. For each item, ask:

• What purpose does this record serve?
• Who can view or download it?
• How long will each recipient keep it?
• What happens to copies when the candidate withdraws or the engagement ends?

Use the answers to set access rules before the search starts. Avoid giving every interviewer access to every document.

How should privacy checks differ across nearshore hiring models?

For a recruiting agency engagement, focus on candidate sourcing and the handoff to your hiring team. Ask how candidates learn where their profiles will go. Confirm whether the agency keeps rejected candidates in a talent pool and how they can request removal.

For an employer of record engagement, extend the review to employment and payroll records. Ask which entity receives identity documents and bank details. Establish who answers worker requests and who retains records after employment ends.

For direct contractor hiring, assign someone on your team to manage document collection and access. Ask your finance team which payment records it needs before requesting them from the worker.

For an outsourced project, review access to your own systems as well. Ask whether subcontractors will see customer data or download files. Use a test environment for assessments, and approve production access through your normal security process.

For Latin American hiring, ask where data is stored and where the people handling it work. Include any cross-border data terms in the contract review.

What should you ask a provider before signing?

Request answers tied to your proposed service. A general statement about protecting privacy does not tell your team who can open an interview recording.

Ask for the privacy contact and a description of how requests are handled. Confirm the process for correcting a candidate record or requesting deletion. Ask which records must be retained and the reason for keeping them.

Review any tools used to record interviews, transcribe calls or score assessments. Ask whether those tools use submitted content to train models and whether you can disable that use.

Agree on an incident contact and notification process. Set out who will investigate an exposed file and who will communicate with affected people.

Finally, define the exit process. Specify who removes accounts, revokes shared links and confirms that agreed deletions are complete.

What should you confirm with Opus?

Opus states: "The client chooses the finalist and manages day-to-day work."

Use that division of work to assign data responsibilities before hiring. Decide who on your team can read candidate feedback and who approves the hire's access to company systems.

Request Opus's privacy notice and written data terms for the proposed engagement. Ask how candidate records move into onboarding and who handles payroll documents. Confirm retention and deletion terms before sending personal records.

Talk to Opus about a role.

<!-- File write skipped: the workspace is read-only. Risk: this buyer checklist does not establish the site's actual privacy practices. -->