Organization isolation
Hiring records are associated with an organization and API access resolves the authenticated organization context server-side.
TRUST CENTER
Hiring evidence deserves
deliberate protection.
Valases combines organization isolation, server-side secrets, controlled access, regional assignment, audit history, AI governance, and human review guardrails.
01 / ARCHITECTURE
Controls built into the operating model.
Security and privacy are treated as product behavior: who can see evidence, where it is assigned, what is recorded, and how decisions are reviewed.
Regional assignment
Customer organizations can be provisioned against approved Mumbai or Tokyo deployment foundations and the assignment source is recorded.
Role-based permissions
Administrative, recruiting, interviewing, payroll, viewing, and release responsibilities are separated by workflow permissions.
Server-side credentials
Database, storage, email, and payment secrets remain server-side and are never exposed through public browser variables.
Private document architecture
Candidate documents are designed for private object storage, organization-prefixed keys, short-lived access, scanning, and retention controls.
Actor-linked history
Workflow changes, evidence review, compliance checks, score adjustments, and offer actions retain actor and event context.
Advisory integrity signals
AI-assisted proctoring signals support human review and are not treated as an automatic rejection, hiring decision, or final finding.
Assistance with accountable review
AI can draft first-pass feedback, organize screening evidence, assist integrity review, and prepare offer language. Authorized people review outputs and remain responsible for decisions and release.
Customer-defined requirements
Candidate, attempt, proctoring, document, export, and audit retention requirements are agreed during implementation.
02 / CUSTOMER REVIEW
What we provide during due diligence.
Enterprise customers can request architecture details, data-flow review, subprocessor information, retention planning, access-role mapping, incident contacts, and deployment acceptance evidence.
Control availability can vary by deployment and implementation stage. The customer order form and implementation plan identify the exact region, retention, integrations, support, and security responsibilities for the rollout.