Contributor Terms

These terms apply to people who create an Adatacore contributor account, complete an assessment or participate in contributor project work. Project-specific instructions or written terms may add to these requirements.

1. Applications are selective

Creating an account or submitting an assessment does not guarantee approval, project access, task availability or any minimum amount of work. Applications may be approved, rejected, placed under review or returned for changes.

2. Accurate identity and account use

Use your own account and provide accurate profile and application information. Do not share credentials, allow another person to complete assessments or project work on your behalf, or use multiple accounts to bypass limits or eligibility rules.

3. Project eligibility

Project access can depend on language, skill track, assessment result, quality history, availability, equipment, security review and other project requirements. Approval for one track or project does not automatically qualify you for another.

4. Instructions and quality

You must follow the current instructions, scripts, guidelines, formatting rules, recording requirements, review criteria and task limits for the project. Work may be reviewed, returned for changes, rejected or escalated when it does not meet the required standard.

5. Original work

Unless a project explicitly allows otherwise, submit work you personally completed. Do not fabricate recordings, use another person's identity or voice without authorization, copy protected answers, or use prohibited automation to complete work.

6. Confidentiality and project data

Project materials may be confidential or restricted. Do not copy, publish, share or reuse project data, scripts, client information, recordings, guidelines, screenshots or outputs outside the authorized workflow unless you have permission.

7. Equipment and environment

Some projects require suitable equipment, browser capabilities, audio conditions or other setup. Where equipment information is requested, provide accurate details. Meeting an assessment requirement does not prevent a project from applying additional technical checks.

8. Payments

Rates, eligibility, units, approval requirements and payment timing can vary by project. Only the project-specific rate or written payment terms for the relevant work control. A submitted task may need to pass required review before it becomes payable.

9. Work availability

Task volume can increase, decrease or stop based on client demand, project inventory, quality, staffing or project closure. Adatacore does not promise continuous task availability or a minimum task volume unless a separate written agreement expressly says otherwise.

10. Trust & Safety

Adatacore may review account, session, device and network information when investigating suspected account sharing, unauthorized access or other security concerns. Security signals are reviewed in context and are not intended to be treated as automatic proof of misconduct.

11. Access changes

Project or platform access may be limited or removed for security concerns, repeated quality failures, violation of instructions, account misuse, project completion, inactivity or other legitimate operational reasons.

12. Support and appeals

Use authenticated Workspace support for account- or project-specific questions. Where a project provides an appeal or escalation path, follow that process rather than creating duplicate accounts or attempting to bypass a decision.

13. Relationship-specific terms

The legal or commercial relationship for a particular project may be defined by separate written terms. These Contributor Terms do not by themselves promise employment status, contractor status, benefits, exclusivity or minimum work.

14. Changes

These terms may change as the platform and contributor workflows evolve. The published dates above identify the current version.