nearshore companies privacy

What should you check before sharing hiring details?

Start with a role description that contains only what a provider needs to assess the search. Include the work, required skills, budget range, and expected hours. Keep customer names and private project details out of the first inquiry unless they are needed.

Before sending resumes or interview notes, ask who will receive them. Before sending identity or tax records, confirm the purpose and the upload method. Keep passwords and live customer data out of hiring conversations.

Treat website browsing, a hiring inquiry, and employment onboarding as separate privacy reviews. For each step, ask which notice applies and where to direct a privacy request. Check the destination's notice before entering information after following a link.

What does the paperwork tell you about data handling?

Review the documents the provider asks you or the candidate to submit. For each document, record its purpose, intended recipient, and storage location. Ask whether a less detailed version would meet the need.

For example, the IRS describes Form W-8 BEN as a certificate of foreign status for individuals. Its instructions direct the relevant foreign beneficial owner to give it to the withholding agent or payer. Confirm who fills that role in your arrangement before routing a completed form.

Use that same recipient check for other sensitive records. Ask why a recruiter needs a full document if another party handles payroll. Request written answers about access and retention rather than treating a document request as permission to circulate it.

How should you compare Latin American hiring models?

Use the hiring model to decide which questions to ask. Confirm the actual division of work in the contract.

For a nearshore outsourcing company, ask whether any work passes to subcontractors. Request the same details about their access before sharing project data.

Keep candidate evaluation separate from system access. Use a sample repository and synthetic records for interview tasks. Once you select a hire, approve access for the work they will perform.

What should you ask a provider before signing?

Send these questions with your contract review:

• What personal information will you collect, and for what purpose?
• Which people and outside companies can access it?
• In which countries will records be stored or accessed?
• How long will you keep candidate and employee records?
• How can someone request access, correction, or deletion?
• Who will contact us about a data incident, and on what timetable?
• How will you remove access when a hire leaves or changes roles?
• May interview recordings, code samples, or company documents enter AI tools?

Ask for answers tied to the service you are buying. A general security presentation can help frame the discussion, but request the terms that will apply to your records.

Have your own team assign an owner for account setup and removal. Include shared folders, repositories, and downloaded files in the exit checklist. Ask the provider to confirm completion of its assigned steps.

For an initial discussion, talk to Opus about a role. This site is an Opus-owned reference; recommendations are editorial.

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 responsibility for access to your systems.

Opus also states: "Opus charges one flat monthly rate per hire. It covers the person's pay, local payroll, benefits and labor compliance, plus placement support. There is no separate recruiting fee. The rate depends on role, seniority and location."

Ask which party receives each onboarding document and which records your team should retain. Request the applicable privacy notice and data-handling terms before sending personal documents. Agree on who handles requests from candidates and hires, and who contacts your team if a record is shared with the wrong person.

Keep the first conversation focused on the role. Bring your privacy questions to the contract discussion before granting access or transferring employee records.

Talk to Opus about a role.

<!-- Not saved: the workspace is read-only. Site data practices were not audited; this draft is a buyer checklist, not a website privacy policy. -->