Adatacore
Security & Trust

Trust is part of the workflow.

Adatacore is built around controlled access to contributor, project and review data. This page explains the safeguards currently implemented in the platform and how security-related signals are handled.

Account security

Identity and access are separated from project work.

Authentication and authorization are handled as distinct controls. Staff access is role-based, contributor access is scoped to the workflows they are eligible to use, and sensitive administrative areas have additional checks.

01

Verified authentication

New contributor onboarding is tied to an authenticated account and the platform supports email verification before the user proceeds through protected workflows.

02

Role-based administration

Super Admin, Project Manager, QA Manager, Finance and Support permissions are separated. Project-scoped roles are not intended to receive unrestricted platform-wide access.

03

Session visibility

Adatacore records retained authentication session metadata so contributors can review recent account activity and authorized administrators can investigate security concerns.

Data access

Sensitive information is not treated as ordinary page content.

Administrative tools use authenticated database functions and role checks for privileged operations. Sensitive Trust & Safety information is restricted more tightly than ordinary project information.

Controlled access

Administrative actions

  • Privileged actions are performed through authenticated server-side database functions.
  • Anonymous execution is removed from administrative and protected workflow functions where applicable.
  • Selected sensitive actions and profile views are written to the platform audit log.
Least exposure

Contributor-facing views

  • Contributors see their own project, application, quality and account information.
  • Exact cross-account network intelligence is not exposed to ordinary contributor profiles.
  • Security history shown to contributors uses a less sensitive presentation than the Super Admin Trust & Safety console.
Audio & file handling

Project media is handled through controlled storage paths.

Adatacore uses private storage for protected contributor assessment recordings and controlled access policies for transcription and project audio. Access depends on the workflow and user role rather than a public file URL.

A

Private assessment recordings

Voice-acting application recordings are stored in a private assessment bucket. Applicants can access their own submission and authorized reviewers can access it for evaluation.

T

Assessment audio isolation

Transcription applicants receive access to the specific assessment sample required for their application rather than general access to transcription storage.

S

Smart Split processing

Large Smart Split source audio can be processed locally in the browser before smaller chunks are uploaded, reducing the need to store the original large source as part of that workflow.

Trust & Safety

Security signals are context, not automatic accusations.

Authorized Super Admins can review retained sign-in, device, network and approximate IP-location information when investigating an account. Adatacore deliberately avoids treating one network match as proof of misconduct.

Signals that may be surfaced

  • New or frequently changing networks.
  • New browser/device signatures.
  • Several recently active networks.
  • Exact-IP reuse across multiple accounts.
  • Approximate IP-derived city, region, country, ISP and ASN when requested.

Important limitations

  • Shared Wi-Fi, offices, colleges and family networks can legitimately share an IP.
  • Mobile carriers and ISP gateways can make location appear far from the user.
  • VPNs can change network and location information.
  • IP geolocation is approximate and is not GPS location.
No automatic fraud conclusion: network, device and GeoIP information is treated as review context. Human judgment and the surrounding account history are required before taking an administrative action.
Operational transparency

What we make visible.

Adatacore maintains a public service-status page and separates contributor application decisions, project access, QA activity and support history so operational decisions can be reviewed in context.

Platform status

See current monitored platform availability and recent recorded incidents.

Open Status →

Help Center

Find guidance for accounts, applications, Voice Acting, Transcription, projects, payments and security.

Open Help Center →

Contributor support

Signed-in contributors can use the Workspace support experience for account- or project-specific issues.

Sign in →

Security or privacy concern

Tell us through the appropriate support channel.

If you are a contributor, sign in and use the Workspace support tools so the report can be tied securely to your account. For general product questions, use the Help Center first.

Help CenterSign in