Trust & Security
Your identity is not a commodity. We treat it that way.
Access is limited by role, team, project, region, workflow state, and data sensitivity. Here is exactly how that works.
Secure account access
Session-based authentication with secure, httpOnly cookies. MFA and passkeys are on the roadmap for all internal admin roles before production launch.
KYC protection
Identity numbers are stored masked (last 4 digits) with full values in encrypted fields only. We never ask for full Aadhaar numbers; masked and offline routes only, always with consent.
Masked data for managers
Team leads and managers see verification status labels and masked identifiers, never raw PAN, Aadhaar, bank numbers, or documents. Finance sees payout records with masked identities.
Audit logs
Logins, role changes, KYC decisions, document views, payout approvals, and privacy requests all write permanent audit events with actor, action, reason, and risk level.
Role-based admin access
Access is limited by role, team, project, region, workflow state, and data sensitivity. Every server operation re-checks permissions; nothing trusts the browser.
Consent history
Every consent is versioned and stored with its exact text and timestamp. Withdrawing an optional consent takes one click in your Privacy Centre.
Worker Privacy Centre
A dedicated dashboard section to see what data we hold, request corrections or erasure, withdraw consents, raise grievances, and download an account summary.
No broad raw document access
Viewing an identity document requires the compliance-specific capability, an explicit stated reason, and creates a high-risk audit event. Directors approve; they do not browse.
Incident response
A security console tracks suspicious activity, failed logins, and incidents with owners and severity. Incident response runbooks are part of our production checklist.
What a manager sees vs what exists
When an operations manager opens your profile they see: your name, city, training status, quality score, and a label like "Verified" next to KYC. They see "A/C ****4821", not your account number. They see "PAN ******82F", not your PAN. The full values exist only in encrypted storage reachable by payment and verification systems, plus a small compliance team whose every document view is logged with a written reason.
Questions about how we protect your data?
Read the privacy policy, or write to our grievance officer. We answer.
Visit the Privacy Centre overview