Security

Your people’s data stays in the UAE.

Dawmo is hosted on AWS in the UAE. Every company is walled off at the database, identity numbers and bank details are encrypted, and managers never see individual salaries. Here is exactly how it works.

Book a security walkthrough

Hosted on AWS in the UAE
Isolated per company
IDs and IBANs encrypted
Salaries hidden from managers

How your data moves

From a phone to the UAE, and out only when you say so.

Every connection is encrypted. Everything is stored in the UAE. Nothing leaves it unless you run the action that sends it, such as paying salaries or notifying a person.

Phone app and browserSign-in tokens live in secure cookies that page scripts cannot read.

Attendance terminalsEach device is registered, and can be locked to your own IP addresses.

Encrypted

AWS UAE (me-central-1)

Dawmo APIChecks who you are and what you may see on every request.

DatabaseEach company fenced off by row-level security.

DocumentsScanned on upload, opened only through links that expire in minutes.

Encryption keysIdentity numbers and IBANs encrypted, keys held in a key management service.

Your action

Your bankThe WPS salary file, when you run payroll.

Email and pushNotices and payslip alerts to your people.

What is true today

The controls in force

Each of these is something you could verify in a technical session rather than take on trust.

Isolation

Every company’s rows are fenced off by the database itself, not by application code remembering a filter.
The fence fails closed: a request with no company attached sees nothing at all.
Cross-company isolation tests run on every change before it ships.

Encryption

All traffic between your people and Dawmo is encrypted in transit.
Passport numbers, Emirates IDs and IBANs are encrypted with AES-256-GCM, and shown masked by default.
Passwords are stored with Argon2, never in a form that can be read back.

Who sees what

Roles and data scopes decide what each person can see: their own record, their team, a department, a branch or the company.
Managers see their team’s leave, attendance and requests, never an individual salary.
Duties are split: finance approves the payroll run, and cannot run it.

Sign-in and sessions

Two-step sign-in with an authenticator app is available to every user.
Revealing a full ID number asks for the password again, and is logged.
Sessions renew with rotating tokens, and a stolen one is revoked the moment it is reused. Repeated wrong passwords lock the account.

Audit trail

Every change to an employee record is logged with who made it, when, and what changed.
Revealing an ID number and exporting a bank file are logged too.
Values in the log are masked, so the log itself never becomes a copy of the data.

Files and monitoring

Uploads are checked for malware and disguised file types before anyone can open them.
Documents live in a private store and open only through links that expire within minutes.
Error reports are stripped of names, salaries, IDs and bank details before they leave the platform.

The life of your data

Collected once, kept in the UAE, handed back when you leave.

Five stages, and at each one the rules above apply.

1
Collect
Entered once by HR or by the employee, over an encrypted connection.
2
Store
In the UAE, fenced off per company, with sensitive fields encrypted.
3
Use
Seen only by the roles allowed to see it, with changes logged.
4
Export
Your data is yours: exported in full on request, in standard formats.
5
Delete
Removed when your contract ends and you ask, on the schedule in the privacy policy.

Retention periods and your rights are set out in full in our privacy policy

20 minute demo, with a person

Put your security questions to an engineer.

Bring your questionnaire to the demo. We will answer it line by line, on the product rather than on slides.

Book a demo

In the call

Your own payroll or roster, run live on screen
Your country's labour and WPS rules in force
Every question answered by someone who builds it

No slides and no obligation. Book a time that suits you.