Security
Salary, visa and performance data sit at the top of any company's sensitivity list. Namya HR is built so permissions hold at the data layer, not just the interface.
Access is granted through a 6-digit one-time code sent to a verified company email domain. Codes expire quickly and no passwords are stored, so none can be leaked or reused.
Employee, line manager, department head, recruiter, HR admin and executive. Each role sees only the records and fields its job requires.
Row-level security policies live in PostgreSQL, so permissions apply to every query — even if the interface is bypassed entirely.
TLS everywhere with auto-renewed certificates, and encrypted storage for records and uploaded documents.
Sensitive actions are recorded, and every salary change keeps a full before-and-after trail with requester, approver, reason and effective date.
Daily database backups with point-in-time recovery, and one-click rollback of any application release.
| Category | Fields | Sensitivity |
|---|---|---|
| Identity | Name, work email, nationality, date of birth | Standard |
| Employment | Job title, department, manager, start date, contract type | Standard |
| Documents | Passport, visa, Emirates ID, contracts | Sensitive |
| Compensation | Basic salary, allowances, change history | Highly sensitive |
| Performance | Objectives, progress updates, review notes | Sensitive |
Documents — passports, visas, Emirates IDs and contracts — are stored on your own storage repository, such as Google Workspace, so they never leave the systems your organisation already controls. All other data is held on a secure, encrypted database with row-level access policies.
Data is held for the duration of employment and any statutory retention period that follows. Access is logged, and compensation data is restricted to HR admin and executive roles.