A buyer's guide to remote staffing privacy

What should you check before sharing hiring data?

Start with a role description that contains no personal records. Explain the work, required skills and expected hours. For a finance role, describe the reporting tasks without attaching a live payroll file. For an engineering role, describe the stack without sending credentials.

Before sending candidate or employee documents, ask the recipient to identify the secure upload channel and the people who can use it. Request the privacy notice that applies to that submission. Read it for the stated purpose, sharing arrangements and retention terms.

Treat this page as a hiring checklist. For information submitted through a website or form, review the notice attached to that service.

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

Talk to Opus about a role.

What do official instructions say about sharing records?

The IRS gives a specific instruction for Form W-8 BEN: a foreign beneficial owner of an amount subject to withholding gives the form to the withholding agent or payer. See the IRS instructions about Form W-8 BEN.

Use that recipient-specific approach when reviewing requests for hiring records. Before forwarding a tax or identity document, ask who needs it and for what purpose. Have your payroll team confirm which documents apply to the arrangement.

Keep document collection separate from interviews. A hiring manager can assess a work sample without receiving the candidate's bank details. Ask the provider to explain how its process keeps those records with the people handling payment or employment administration.

Review interview recordings as well as documents. Ask whether calls are recorded, who can replay them and whether a transcript goes into another tool. Confirm how candidates receive notice before a recording starts. Include recordings and transcripts when asking about retention and deletion.

How should you compare nearshore and Latin American hiring models?

Compare remote staffing agencies by the duties in the proposed contract. For each model, trace candidate records through hiring and decide who will control work accounts.

Apply the same review to remote staffing companies regardless of location. Ask for the actual storage locations and access rules. Avoid assuming that working nearby determines where records are held.

Walk through a specific handoff before signing. If a recruiter sends a finalist's resume to your hiring manager, decide where that copy belongs. Specify who may forward it and what happens when the role closes. Repeat the exercise for any documents passed to a payroll contact.

What should you ask a provider before granting access?

Send questions tied to the role. A developer with access to customer logs needs a different review from someone working only with public marketing copy.

Ask the provider:

• Which personal records do you collect, and what is each record used for?
• Which outside organizations receive those records?
• How long do you retain records for unsuccessful candidates and former workers?
• Who receives an incident report, and what notification timetable will the contract specify?
• Can workers download company files to personal devices?
• What rules govern entering company or candidate information into AI tools?
• Who confirms that access has ended when a worker leaves?

Give your own IT team a matching task: define the accounts and permissions the role needs. Record who approves access and who removes it. Use a sample task to check the planned setup before exposing customer information.

Plan for changes after onboarding. If a worker moves from public content to customer support, review access before assigning the new work. Keep a named owner for that review so permissions do not expand through informal requests.

Request written answers before signing. If a response is vague, ask for the relevant contract term or a demonstration of the process.

What should you confirm with Opus?

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

Build your privacy review around that daily work. Describe the systems the finalist would use and the kinds of records they would see. Ask how the proposed arrangement will handle candidate documents, employment records and incident reports.

Request written privacy terms alongside the service agreement. Have your team assign responsibility for account approval and removal before the start date. Keep the agreed access list with the hiring record so the manager and IT team can use the same instructions.

Before the hire starts, walk through an exit with your IT contact. Decide who will disable accounts and check shared folders. Ask the provider how it will confirm the return or deletion of company files, including copies held on a worker's device.

Talk to Opus about a role.

<!-- Not saved to disk: the workspace is read-only. Provider privacy controls were not audited. -->