Why Dexta · Security
Salaries, PANs and bank details deserve care. Here's how we take it.
Dexta holds the most private records your company keeps. This page says what protects them today, in plain words, and what we haven't done yet.
Sign-in
Only the right people get in, and leavers get out fast.
Strong passwords
Passwords of at least 12 characters. Common passwords and the person's own email name are refused. Sign-in attempts are limited per account, per address and per email.
Two-step sign-in you can make compulsory
A six-digit code from an authenticator app, with ten single-use recovery codes. Your org admin can require it for the whole company and reset it for someone who lost their phone.
Single-sign-on-only mode
With your Microsoft, Okta or Google Workspace sign-in, switch password sign-in off for everyone except one to five named break-glass admins.
Sign out everywhere
Ends every session on every device. A password change does the same.
Revoke access in about two minutes
Shut someone out and every app knows within about two minutes, whatever is left of their sign-in. The same goes for switching an app off.
Leavers see only their own papers
Former employees keep a read-only way in to their payslips and tax forms for a set number of days (400 by default), then lose access by themselves.
Access
Everyone sees what their job needs.
Access is set in one place, the Hub, and every app follows it. Nobody becomes an app's admin by signing in first.
- Nine ready-made access profiles: Employee, Manager, HR, Recruiter, Payroll admin, Finance, IT, Leadership and Org admin
- A question-by-question “who does what” wizard, with a preview before one save
- Access groups filled by hand, from a list, by a rule such as “department is Finance”, or from your Active Directory groups
- The effect of any change is shown before it's saved
- Per-person exceptions on top of profiles, for one app at a time
- Managers approve their own team without any set-up
Salary privacy
Pay figures stay with the people who run pay.
Knowing someone's salary is a payroll job, not an HR one. Dexta keeps it that way.
- Letters that show pay are issued only by people allowed to see salaries, in payroll or finance. HR never sees the figures.
- A switch decides whether Finance sees each person's salary or only totals
- Salary columns in HR's reports appear only for people allowed to see salaries
- Growth's audit log never records salary figures
- WhatsApp and SMS alerts never carry amounts, PAN or bank details
- Server logs never carry names, emails or salaries from database errors
Records and encryption
Who changed what, and data that's useless if stolen.
Audit logs
- An org-wide log of who changed what in set-up, people and sign-in, with a CSV export
- HR, Time, Growth, Desk and Cheer each keep their own log; Time's can't be edited
- Books' posted journals are hash-chained and its audit trail is sealed, as rule 3(1) of the Companies (Accounts) Rules asks
- Every look at clock-in locations or photos is logged, and people can see who viewed their record
- Every download of a company data export is logged
Encryption and separation
- Bank account numbers, PANs and stored sign-in and mail passwords are encrypted, with a separate key for each app
- Every backup is encrypted with AES-256, and only encrypted backups leave the server
- Books' document vault is stored encrypted
- Each app has its own database and its own database user, with rights on its own data only
- HTTPS on every page, with HSTS, a content security policy and frame protection
Backups are made daily, copied every six hours to an Indian region and kept 400 days. More on hosting and backups.
DPDP Act 2023
The privacy law's paperwork, built into the Hub.
Every person gets a privacy page with the notice, their consent choices, their requests and their nominee. Former employees keep it too. Your privacy team works the other side.
- A privacy notice in 23 languagesPublish your notice in English and the 22 Eighth Schedule languages (you supply the translations), with reminders to anyone who hasn't seen it.
- Consent registerYour purposes, each person's consent to each one, and a CSV of consents for your records.
- Five kinds of requestSee my data, correct, erase, nominee and complaint, worked as a numbered queue with notes, status, replies and a legal-hold check.
- A copy of “your data”Gathers a person's data from every app into one download. People can also see who viewed their record.
- Erasure across the appsOnce your privacy team decides, the person's data is erased in each app.
- Retention scheduleLegal keep-periods for 9 record types, a due-for-erasure report, and holds that stop erasure. Automatic clean-up is off until you switch it on, and runs as a dry run first.
- Breach registerLog an incident with its two clocks: 6 hours to report to CERT-In, and 72 hours for the full report to the Data Protection Board. Notify the people affected.
- Staff under 18Flags minors and records a guardian's consent.
- NomineesA person can name a nominee to act for them.
- Sub-processor listThe services Dexta uses and where data is stored, shown on every privacy page, with processing terms.
Your data, your exit
Take all of it, any time.
An org admin can export the company's data from every app as one zip. A second admin approves it first. The download link works once, and every download is logged. With the own-server option, the data never leaves your hands at all.
Not done yet
What we haven't done, said plainly.
Dexta has not yet had an outside security test, and it does not hold ISO 27001 or SOC 2. An outside security test is planned first, then ISO 27001. Until then we'll walk your IT team through how data is stored, encrypted and backed up, and you can run everything on your own server.
Try Dexta
Bring your IT head to the demo.
We'll show the access screens, the privacy pages and the audit logs on a sample company, and answer your security questions directly.
