employer of record companies privacy

What should a busy buyer check before sharing data?

Before sending a candidate file, ask the provider to name the people and systems that will receive it. Give each requested document a purpose. A resume for an interview and a bank record for payroll should have separate access rules.

Keep your first hiring inquiry focused on the job. Describe the work, required skills and budget. Avoid attaching employee records or customer data to explain the role.

This site is an Opus-owned reference; recommendations are editorial. For any provider you consider, request the privacy notice and contract terms that apply to your engagement. Review website browsing, candidate screening and employment records as separate activities.

What does the paperwork tell you about data handling?

A document's purpose helps you decide who should receive it. For example, the IRS directs applicable foreign beneficial owners to give Form W-8 BEN to the withholding agent or payer. That instruction identifies a recipient for a specific tax form. IRS guidance.

Use the same question when reviewing a provider's document requests: who needs this record, and for which task? Have your tax adviser confirm which forms apply to the arrangement.

Ask for a sample onboarding checklist before collecting documents. Review each field with your HR or privacy owner. Check whether the provider needs a full document, a limited extract or confirmation that someone has reviewed it.

Keep the provider's answers with the signed agreement. A sales email saying that data is secure gives your team little detail about access or deletion.

How should privacy checks differ across nearshore hiring models?

Build your review around the work each party will perform. For a Latin American hire, ask where each handoff occurs and who keeps a copy afterward.

Review access to your own systems separately. Before granting access to a repository or customer database, define what the role needs. Assign someone on your team to approve access and remove it when the work ends.

Compare hiring models with Opus.

What should you ask a provider before signing?

Request written answers to these questions:

• What personal data will you collect at each hiring stage, and why?
• Which legal entities receive it, including subcontractors?
• Where will records be stored or accessed?
• How do you restrict access to identity and bank documents?
• Will interviews be recorded or assessments processed with AI tools?
• How long do you retain unsuccessful candidates' records?
• Who receives privacy requests from workers?
• How will you notify us of a suspected data incident?
• What happens to records when our contract ends?

Ask the provider to walk through one candidate's path from application to departure. Include copies in email, exported spreadsheets and recordings. This gives your reviewer specific systems and handoffs to assess.

For any retention period, ask what starts the clock and what exceptions apply. For deletion, ask whether the process covers backups and subcontractors. Avoid promising a worker a deletion date until the responsible party confirms it.

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 your internal accounts and access approvals.

Ask Opus to identify who handles privacy questions during screening and employment. Request the applicable terms before sending personal records. Have your reviewer check the named entities, permitted uses and retention periods against the work you are buying.

Include the exit process in that review. Agree who notifies your IT team when a placement ends and who handles requests concerning employment records. Keep the agreed contacts with your onboarding checklist so the hiring manager can find them.

Discuss your hiring model with Opus.

<!-- File not saved: workspace is read-only. Provider privacy practices were not audited; this page is a buyer checklist, not a verified site privacy policy. -->