Security
How OTOMATE keeps your data secure
Each company's data is kept apart inside the database itself, with Postgres row-level security forced on more than 80 tables. Sign-in takes a password stored only as a salted scrypt hash and, with two-step sign-in, a 6-digit code from an authenticator app. Bank, Aadhaar, PAN, UAN, PF and ESI numbers are encrypted with AES-256-GCM, masked by default, and every full reveal is logged.
Backups are encrypted and checked for tampering before any restore. Every API route has a request limit, uploads are checked by what they really contain, and the console runs under a strict Content-Security-Policy. Fingerprint and face templates never leave your machines. Below is exactly how each part works, with the real numbers.
80+ tableswith forced row-level security
AES-256-GCMon bank, ID and PF/ESI numbers
30-second codestwo-step sign-in with an authenticator app
0 known vulnerabilitiesin production dependencies (npm audit, 7 November 2026)
At a glance
The main controls, and how they are built.
| Area | What protects it | Detail |
|---|---|---|
| Company data | Postgres row-level security | Forced on more than 80 tables, set per transaction |
| Access inside a company | Roles and data scopes | 47 permissions, custom roles, branch, department or team scope |
| Passwords | scrypt | N = 32,768, r = 8, p = 1, 16-byte random salt |
| Two-step sign-in | Authenticator app codes (TOTP) | RFC 6238, 6 digits every 30 seconds, 10 recovery codes; owners can require it |
| New devices | Sign-in alert email | Time, device, browser and IP, with a sign-out-everywhere link |
| Sessions | Short tokens, rotating refresh | 15-minute access token, single-use refresh token |
| Bank, Aadhaar, PAN, UAN, PF, ESI | AES-256-GCM field encryption | Masked by default, every full reveal logged |
| Biometrics | Never requested | Templates sent anyway are discarded |
| Audit trail | Server-side log | 100+ action types, with who, what, when and IP |
| Request limits | Limits on every API route | 300 a minute per address by default; far lower for reports, exports, imports and public forms |
| Uploads | Checked by content | PDF, JPEG, PNG and HEIC only; photo metadata and GPS stripped |
| Exports | Formula neutralising | Every CSV and Excel file |
| Console | Nonce-based Content-Security-Policy | 'strict-dynamic', frame-ancestors 'none', object-src 'none' |
| Transport | HTTPS with HSTS | One year; includeSubDomains on the console |
| Backups | AES-256 with an HMAC-SHA256 check | Nightly; 7 daily and 4 weekly database copies; photos and documents included |
| Dependencies | npm audit, pinned versions | 0 known vulnerabilities in production dependencies (7 November 2026) |
Tenant isolation
How your data is kept apart
Many companies use OTOMATE. Their records sit in one database, separated by the database itself, not only by our code.
Between companies
- Row-level security
- Postgres row-level security is enabled and forced on more than 80 tables. Each row carries its company's id, and the policy only lets a request see or write rows of its own company.
- Set per transaction
- Your company's id is set for one database transaction at a time, so it can't carry over to the next request on a shared connection. It must be a valid UUID.
- Nothing by default
- If no company is set, the database returns no rows at all. Writing a row into another company is refused by Postgres. Automated tests check both.
- Two database roles
- The API's request role is marked
NOBYPASSRLS: it can't switch the rules off. Password hashes sit in a table this role can't read at all. - Membership check
- Before any data is touched, the API checks that you are an active member of the company you are asking about, and that your role has the permission the action needs.
- Second wall
- Sign-in, the machine gateway and background jobs use a separate system role. For them the API's own checks are the guard, and row-level security is the second wall for everything a signed-in person does.
Inside your company
- 47 permissions
- Fine-grained permissions, with separate switches for salary, bank numbers, PAN, Aadhaar and ID document files.
- 8 built-in roles
- Owner, admin, HR, manager, front desk, teacher, employee and gym member.
- Custom roles
- Build your own role from the permission list (Enterprise plan). Nobody can grant a permission they don't hold themselves.
- Data scopes
- Limit a person to all staff, chosen branches, chosen departments, their own team (down the reporting line) or only themselves. The scope is applied to lists, reports and exports.
- Enforced on the server
- The API enforces every permission. The console and app only hide what you can't use.
Accounts
Passwords and sign-in
Sign in with your email and a password, plus a code from your phone if two-step sign-in is on. Here is what happens to that password, and to the session that follows.
How passwords are stored
- scrypt hashing
- Passwords are hashed with scrypt (N = 32,768, r = 8, p = 1), a random 16-byte salt and a 32-byte key. The cost is stored with each hash, so it can be raised later.
- Never kept in plain text
- Only the hash is stored. It is never logged and never sent back by the API.
- Constant-time check
- Hashes are compared in constant time, and a damaged or edited hash never matches.
- Decoy check
- If no account exists for an email, the password is still checked against a decoy hash. The error message is the same either way and the check takes about as long, so sign-in can't be used to find out who has an account.
Password rules
- 8 to 128 characters
- Not one repeated character, and not a simple run such as 12345678 or abcdefgh
- Not on a list of over 250 common passwords
- Not your own email address or name
Limits on guessing
| What is counted | Limit | Window |
|---|---|---|
| Wrong passwords for one account | 10 | 15 minutes |
| Failed sign-ins from one network address | 50 | 15 minutes |
| Wrong two-step codes for one account | 5 | 15 minutes |
| Wrong two-step codes from one network address | 30 | 15 minutes |
| Wrong current password when changing it | 5 | 15 minutes |
Past a limit, the API answers HTTP 429 with a Retry-After time. It is a short pause, not a permanent lockout, so nobody can lock a colleague out on purpose.
Sessions and tokens
- Access token
- A JWT that lasts 15 minutes. Its issuer, audience and algorithm are checked on every request, and only HS256 is accepted.
- Live revocation
- Each request also checks that the session hasn't been signed out. A revoked session stops working within 30 seconds.
- Refresh token
- 32 random bytes, valid for 30 days. The database keeps only an HMAC-SHA256 of it with a server-side secret, so a copy of the database alone can't be used to sign in.
- Single use
- Each refresh token works once and is replaced. If an old one is used again (after a 30-second grace for two tabs refreshing together), the whole session is shut down.
- Cookie
- In the browser the refresh token sits in an
httpOnly,Secure,SameSite=Strictcookie, limited to the sign-in path and never cached. - In memory only
- The console keeps the access token in memory, never in local storage, where scripts could read it.
- On phones
- The Android app keeps its token in the phone's secure storage (Android Keystore). An optional App Lock asks for the phone's fingerprint, face or screen lock.
- Your sessions
- See every device you are signed in on, and sign out one or all the others. Both are written to the audit trail.
- Password change
- Changing your password signs out every other session.
- Temporary passwords
- An owner or admin can set one, and it must be changed at the next sign-in. Until then the account can do nothing else. You can't reset someone with more access than you, or someone who belongs to another company.
Two-step sign-in
Two-step sign-in and new-device alerts
With two-step sign-in on, a stolen password is not enough. After the password, OTOMATE asks for a 6-digit code from an authenticator app on your phone, such as Google Authenticator, Microsoft Authenticator or Authy.
| Part | How it works |
|---|---|
| Codes | Time-based one-time passwords to RFC 6238: 6 digits, a new one every 30 seconds, from any standard authenticator app. |
| Secret | The authenticator secret is stored encrypted with AES-256-GCM. |
| No reuse | The time step of each accepted code is saved atomically, so the same code can't be used twice. |
| Recovery codes | 10 single-use codes for a lost phone, stored only as keyed hashes. |
| Sign-in step | A correct password opens a code challenge that is valid for 5 minutes and can be used once. |
| Guessing limit | 5 wrong codes per account, or 30 per network address, in 15 minutes, then a pause. |
| Password reset | Resetting a forgotten password still asks for the code, so access to an email inbox alone can't take over the account. |
| Turning it off | Needs your password and a code. |
| Logged and emailed | Every change is written to the audit trail, and you get an email when two-step sign-in is turned on or off. |
| Where | The web console and the Android app. |
- Company rule
- An owner can require two-step sign-in for every owner and admin in the company, so the accounts with the most access are always covered.
- OTOMATE's own staff
- OTOMATE's internal owner panel can't be opened without two-step sign-in.
New-device sign-in alerts
- Alert email
- When your account signs in on a device it hasn't seen before, you get an email with the time (IST), the device and browser, and the network address.
- One link to act
- The email has a link to sign out of all sessions, for the moment it wasn't you.
- How devices are recognised
- By a long-lived
httpOnlycookie in the browser, or the app's device id. Either one is stored only as a keyed hash.
Field encryption
Sensitive numbers
The numbers that could hurt someone if leaked are encrypted one by one, on top of the access rules.
| Encrypted field | Where it is kept |
|---|---|
| Bank account number | Payroll (salary bank details) |
| PAN | Payroll profiles |
| UAN | Payroll profiles |
| PF number | Payroll profiles |
| ESI number | Payroll profiles |
| Aadhaar number | Staff documents |
| PAN | Staff documents |
| Bank account number | Staff documents (bank proof) |
| Authenticator secret | Two-step sign-in |
| Device password | Machine settings |
| WhatsApp access token and app secret | Notification settings |
- Masked everywhere
- Numbers are shown masked by default, with only the last 4 characters visible, in lists, profiles and documents alike.
- Reveal needs permission
- Showing a full number needs its own permission, and every reveal is written to the audit trail with who and when.
- Statutory files
- PF ECR and ESI files decrypt the numbers only at the moment you download them, and each download is logged.
- Bank files logged
- Downloading a salary bank file, or viewing a bank statement, is logged too.
Other records, such as names, attendance and uploaded files, are protected by the access rules above rather than by encryption.
Biometrics
Biometric data stays on your machines
Fingerprints and faces are enrolled and matched on the machine at your gate. OTOMATE never asks machines to upload fingerprint or face templates, and discards any that arrive. For each punch we keep who, when, which machine and how they verified. That's all we need to run your attendance, so it's all we keep.
Machines
- Never requested
- When an eSSL or ZKTeco machine connects, OTOMATE asks only for attendance logs, operation logs and the user list. The option that would pull fingerprint and face data is never switched on.
- Discarded if sent
- If firmware sends fingerprint, face, finger-vein or user-photo data anyway, it is acknowledged and thrown away. Realtime template data is ignored the same way.
- Hikvision
- Faces stay on the terminal. OTOMATE only sends the person and the dates they may enter.
- Per punch
- Person code, time, machine and verification method (finger, face, card and so on). Nothing more.
Selfie and GPS punches
- No face recognition
- Selfies are kept as photos for a manager to look at. They are never turned into face templates.
- Deleted on schedule
- Each company sets how long selfies are kept, from 7 to 730 days (90 by default). An hourly job deletes older selfie files. The punch itself stays.
- Metadata removed
- EXIF, XMP and IPTC data, including GPS and camera details, is stripped from every selfie before it is stored. The file must be a real JPEG, up to 150 KB.
- Checked by the server
- The server re-checks the geofence distance, GPS accuracy and shift window, refuses mock locations, and allows one punch a minute. Offline punches up to 72 hours old are accepted.
Accountability
Audit trail
Over 100 kinds of action are recorded with who did it, what changed, when, and from which network address.
- Accounts
- Sign-ins that worked and failed, password changes and resets, two-step sign-in turned on or off, sessions signed out.
- Team
- Members invited, joined or removed, role changes, invitation links created.
- Machines
- Machines added or removed, push addresses replaced, device credentials saved.
- People
- Staff added, edited, deleted or imported, and photo changes.
- Payroll
- Pay changes, payments, payslips published, bank, PF ECR and ESI files downloaded, bank statements viewed.
- Sensitive numbers
- Every reveal of a full bank, Aadhaar, PAN, UAN, PF or ESI number.
- Approvals
- Leave, attendance correction and expense decisions.
- Doors
- Unlocks are decided on the server against your access rules, and each decision is stored before the reply, including refusals.
- Settings
- Changes to company settings and access rules.
- Who can read it
- Anyone with the audit permission, in the console, with filters. OTOMATE doesn't delete audit entries.
Abuse protection
Request limits and abuse protection
Every route of the API has a request limit. A request over its limit is refused before its body is read and before any database work, with HTTP 429 and a Retry-After time.
| Kind of request | Limit |
|---|---|
| Most API requests | 300 a minute per network address, or per signed-in person. Signed-in offices that share one address get a higher ceiling. |
| Reports, PDFs and uploads | About 30 a minute per person |
| Bulk work: exports, bank and statutory files, imports | 10 a minute per person |
| Public forms: enquiries, sign-up, password reset, invitations | 20 at once, then 2 a minute per address |
| Wrong passwords | 10 per account and 50 per address in 15 minutes |
| Wrong two-step codes | 5 per account and 30 per address in 15 minutes |
| Biometric machine connection | Its own limits per address and per machine |
- Unknown machines are refused before their data is read.
- The network address is taken from our own web server, not from a header the client sets, so it can't be faked to dodge a limit.
- The web server refuses oversized requests and cuts off slow-request attacks (Apache
RequestReadTimeout). - Request bodies are capped at 256 KB, and file uploads have their own cap for each kind of file.
- Door unlocks have a per-person limit, and the website enquiry form has a hidden trap field for bots.
Files
Safe uploads and exports
Files people upload are checked for what they really are, cleaned, and sent back in a way browsers won't run. Files you download are safe to open in a spreadsheet.
| File | Largest size |
|---|---|
| Staff document | 10 MB |
| Profile photo | 5 MB |
| Expense receipt | 170 KB |
| Selfie punch | 150 KB |
- Checked by content
- A file's type is read from its first bytes (its magic bytes), not from its name. Only PDF, JPEG, PNG and HEIC are accepted.
- Risky types refused
- SVG, HTML and executable files are refused, even when renamed.
- Hidden metadata removed
- EXIF data in photos, including GPS location, is stripped before the file is stored.
- Safe downloads
- Files are sent back so that browsers can't run them, with content sniffing off and no caching.
- Private files
- Document scans and photos live outside the web root, with random names, readable only by the service. They are never public links: they are sent only through signed-in, permission-checked requests.
- Safe spreadsheets
- Every CSV and Excel export neutralises formula injection: a cell that starts with
=,+,-or@, such as=HYPERLINK(…), can't run when the file is opened.
Servers
Infrastructure and backups
How the servers behind app.otomateworld.com are set up, and how your data is backed up.
- HTTPS with HSTS
- The console, the mobile app's API and this website use HTTPS. Plain HTTP is redirected, and HSTS tells browsers to use HTTPS only for a year. On the console it covers its subdomains too (
includeSubDomains). - Locked-down API
- The API accepts browser requests with credentials only from the console's own address. Its responses carry headers that block framing and content sniffing.
- Bound to localhost
- The API, the console and the database listen only on 127.0.0.1. The web server in front is the only way in, and the machine gateway's own port is closed at the firewall.
- Containers
- Each service runs in its own container and is restarted automatically if it stops. OTOMATE's own services run as a non-root user.
- Resource limits
- Hard memory and CPU caps per container, for example 640 MB and 0.75 CPU for the API and 512 MB and 0.5 CPU for the database. Logs are capped at 10 MB a container.
- Root-only secrets
- Keys are generated on the server with
openssl randand kept in a root-only folder (0700, files 0600). Signing keys must be at least 32 characters, and the API refuses to start in production with a development key. - Separate database passwords
- The admin, request and system database roles each have their own password.
- Disk checks
- Free disk space is checked every hour, and an alert email goes out when it drops below 8 GB.
Backups
| Part | How it works |
|---|---|
| Database and settings | A full database dump and the server's configuration, every night |
| Photos and documents | A full archive every week, plus each day's new files |
| Encryption | Every file is encrypted with AES-256. The key is never stored in the backup folder or inside any backup. |
| Integrity | Each file carries an HMAC-SHA256 check, so a damaged or tampered backup is refused on restore. |
| Kept | 7 daily and 4 weekly copies of the database and settings; the last 2 weekly photo archives with their daily additions |
| Disk-space guard | If a backup would leave the disk too full, the photo archive is skipped and we get an alert email, so backups can't fill the disk the service needs. |
Backups are kept on the server itself today. A copy to a second location is built in but not yet switched on, so we don't claim off-site backups.
Attendance machines and port 80
Most biometric machines in use today can't do modern TLS, so they push punches over plain HTTP on port 80. HTTPS on port 443 is there for firmware that supports it. We keep the plain-HTTP path narrow:
- Only machines whose serial number a company has added are accepted. A serial can belong to one company only. Anything from an unknown serial gets HTTP 403 and its punches are not stored.
- No fingerprint or face templates travel this path, because OTOMATE never asks for them.
- Hikvision push uses a random 142-bit secret token in its address, kept out of our logs.
- The machine connection has its own request limits per network address and per machine, so a flood from one address or one machine is cut off.
Code
Engineering practices
Habits built into the code, so that security doesn't depend on remembering.
Content-Security-Policy on the console
The console sends a strict, nonce-based Content-Security-Policy with every page. Only scripts carrying that page's nonce, and the scripts they load, can run. Injected scripts and inline event handlers are blocked.
| Header | What it does |
|---|---|
| Content-Security-Policy | Nonce-based scripts, no plugins, no framing, forms and base URL kept to the console |
| X-Frame-Options: DENY | No other site can show the console in a frame (clickjacking) |
| X-Content-Type-Options: nosniff | Browsers can't guess a file is a script |
| Referrer-Policy | Full addresses aren't passed to other sites |
| Permissions-Policy | Camera, microphone and location are switched off for the console |
| Cross-Origin-Opener-Policy | Keeps the console's window apart from windows opened by other sites |
| Strict-Transport-Security | HTTPS only, for a year, including subdomains |
In the code
- Zero known vulnerabilities
npm auditreported no known vulnerabilities in our production dependencies on 7 November 2026.- Pinned dependencies
- Server packages are locked to exact versions with a lockfile and installed with
npm ci. - Every input validated
- Every request body is checked against a zod schema before the code uses it. Server settings are validated the same way at start-up.
- Parameterised SQL
- Queries are built with the Drizzle ORM and parameterised SQL templates. The few raw fragments only ever hold IDs that were already validated.
- Idempotency keys
- Punches and other create requests (13 in all) accept an idempotency key. A retried request can't create a second record, and a key reused with different data is refused.
- Clean errors
- Error messages don't reveal internal details. Stack traces stay in the server logs, and request logs record the method and path but not query strings.
- Signed webhooks
- WhatsApp webhooks are accepted only with a valid HMAC-SHA256 signature from Meta, checked in constant time.
- No internal reach
- By default in production, OTOMATE won't connect to private network addresses when it talks to a device, so it can't be pointed at internal services.
- Signed email
- Account emails are sent from our own mail server with DKIM signatures.
Straight answers
What we don't claim (yet)
Everything on this page is checked against our code. These are the things we don't claim today.
- Certifications and audits
- We are not ISO 27001 or SOC 2 certified yet, and we don't claim an independent penetration test.
- Single sign-on
- Single sign-on (SAML, Google, Microsoft) isn't available yet. Two-step sign-in works in the web console and the Android app; the iPhone app isn't out yet.
- Encryption at rest
- We encrypt the specific fields listed above, and the backups. We don't claim that the live database or uploaded files are encrypted at rest: they are protected by the access rules.
- Off-site backups
- Backups are encrypted, but they are kept on the same server today. We don't claim off-site backups yet.
- Uptime
- We don't offer an uptime SLA, and we don't claim high availability.
- Audit trail
- OTOMATE never deletes audit entries, but we don't call the log tamper-proof or immutable.
- Data location
- We don't promise that data stays in one country. Ask us and we will tell you where it is hosted.
If one of these matters for your purchase, tell us. It helps us decide what to build next.
Report a vulnerability
If you think you've found a security issue in OTOMATE, email hello@otomateworld.com with "Security" in the subject. Tell us what you found and how to reproduce it, and give us a fair chance to fix it before you share it. We will keep you posted while we work on it.
Our contact details are also in security.txt, in the standard format (RFC 9116).
Your data is yours
You decide who is in OTOMATE and why. We process their data only to run the service for you. We don't sell data or show ads. The details are in our privacy policy.
Questions people ask
Something else? Call +91 90536 35607 or write to hello@otomateworld.com.
Does OTOMATE store fingerprints or face data?
No fingerprint or face templates. OTOMATE never asks machines to upload them and discards any that arrive. If you use selfie punches, the selfie photo is kept for the period your company sets (90 days by default) and then deleted. Selfies are not used for face recognition.
How is one company's data kept apart from another's?
Inside the database. Postgres row-level security is forced on more than 80 tables, and each request sets your company's id for its own transaction only. With no company set, the database returns nothing.
How are passwords stored?
As scrypt hashes (N = 32,768, r = 8, p = 1) with a random 16-byte salt, in a table the API's request role can't read. Passwords are never logged or sent back.
Can I turn on two-step sign-in?
Yes, in the web console or the Android app. Link an authenticator app such as Google Authenticator, Microsoft Authenticator or Authy, and after your password OTOMATE asks for its 6-digit code. You get 10 single-use recovery codes, and an owner can require two-step sign-in for every owner and admin in the company.
Which data is encrypted?
Bank account, PAN, UAN, PF and ESI numbers in payroll, and Aadhaar, PAN and bank numbers on staff documents, are encrypted with AES-256-GCM and masked by default. So are authenticator secrets, device passwords and WhatsApp tokens. Backups are encrypted with AES-256, and the console, the app and this website use HTTPS. Other data, including uploaded files, is protected by access rules rather than encryption.
Are backups encrypted?
Yes. Every night the database and server settings are backed up, and photos and documents are archived weekly with daily additions. Each file is encrypted with AES-256 and carries an HMAC-SHA256 check, so a damaged or tampered backup is refused on restore. We keep 7 daily and 4 weekly copies of the database. The backups are on the same server today, not off-site.
Is OTOMATE ISO 27001 or SOC 2 certified?
Not yet. This page lists the controls in place today, each one checked against our code.
How do I report a security issue?
Email hello@otomateworld.com with Security in the subject. Our security.txt file is at otomateworld.com/.well-known/security.txt.
Have a security question?
Book a free demo and ask us anything on this page. We will show you two-step sign-in, the roles, the audit trail and the masked numbers in the console.