Nobody looks at your payroll without leaving a name
Payroll data is the most sensitive data a small company holds. Our model is not “we promise” — it is that access is scoped by role, masked by default, and written to a log you own.
01Encryption
Encrypted at rest and in transitSalary, bank and statutory identifiers are encrypted at rest. All traffic is TLS 1.3. Backups are encrypted with separate keys.
02Access
Role-scoped access, defined by youRoles are tenant-created, not a fixed four. HR need never see payout totals; an accountant need never see personal addresses. The agent inherits exactly the role it runs as.
03Masking
Masked by defaultBank accounts and UANs render as •••• 3885 everywhere except the two screens that genuinely need them — the bank transfer file and the payroll run. Employees request corrections rather than editing their own bank details.
04Support
Support access is time-boxed and reasonedEmplora staff have no standing view into your employees’ salaries. Support access must be requested with a written reason, expires in 2, 8 or 24 hours, and is recorded in your audit log — you see who looked, when and why.
05Residency
Data residency in IndiaPrimary and backup storage are in Indian regions. No payroll data is processed outside India, including by the agent.
Your audit log
Excerpt
When
Actor
Action
04 Sep 11:42
Emplora support
Support access
04 Sep 10:18
Ananya Das
Employee — edit bank
31 Aug 18:05
Abhinav Jha
Payroll run — approve
31 Aug 17:52
Vikram Singh
Payslip — override
28 Aug 09:31
Ananya Das
Leave request — approve
Support access rows carry the reason, the requester and the expiry.