DonkeyHR

Security

Payroll data is among the most sensitive data a company holds. This page describes the controls that actually exist in the product today — and is equally explicit about the ones that do not.

Last updated: 9 September 2026

Draft pending legal review. This document describes how DonkeyHR is actually built and operated today, but it has not yet been reviewed by counsel. Items marked To be completed are genuinely undecided — we would rather say so than state something we cannot stand behind. If you are evaluating DonkeyHR through procurement, contact us and we will tell you exactly where each one stands.

What we do not claim

Start here, because it is the part most vendors bury. DonkeyHR does not hold SOC 2, ISO 27001, or any other third-party security certification or audit report. We are an early-stage company and we have not been through those audits. If a certification is a hard requirement in your procurement process, tell us now rather than at contract stage — we would rather lose the deal honestly than pass a questionnaire we cannot support.

We also have not yet completed an independent penetration test. To be completed: timing for a third-party test and for beginning a formal certification track are open decisions for the founding team.

Tenant isolation

DonkeyHR is multi-tenant. Every row of customer data carries the owning organisation's identifier, and application access to that data runs through one tenant-scoping layer that injects the organisation filter into every read, write, update and delete. This is a single chokepoint rather than a convention each query has to remember, which is what makes it dependable.

Cross-tenant reads are therefore not reachable through the application. The two exceptions are deliberate and hold no employee data: webhook delivery records used for idempotency, and inbound marketing leads — which by definition exist before a prospect has an organisation at all.

Authentication and access control

  • Authentication is first-party. Passwords are stored only as a salted scrypt hash — a deliberately slow, memory-hard function — so we cannot see or recover your password, and neither can anyone who obtains a copy of our database.
  • Sessions are server-side and opaque. Your browser holds a random token; we store only its hash, so a database disclosure yields no usable sessions. Because sessions live on our side rather than in a self-contained token, access can be revoked immediately — the moment an administrator removes someone, not whenever their token would have expired.
  • Account creation is invitation-, verification- or operator-gated. Joining an existing organisation requires an invitation issued by someone with HR or Owner rights there. A new workspace comes into existence one of two ways: self-serve creation (teams up to 50), which requires clicking a single-use, time-limited link we email to the address being registered; or provisioning by a DonkeyHR operator against a verified request. Self-serve creation is available only when this deployment can send that email — it is open today. In all cases nobody can create an account against your organisation, or overwrite an existing account's password, by merely knowing an email address.
  • Sign-in is rate limited per source address and per email address, and an account locks temporarily after repeated failures. Sign-in responses are deliberately identical whether or not an email is registered, so the form cannot be used to discover who our customers are.
  • Multi-factor authentication is available, optional per account and available to every role. It uses a time-based one-time code from a standard authenticator app — Google Authenticator, Microsoft Authenticator, 1Password, Authy or any other app that supports the same standard. Turn it on from Security in your account settings. When it is on, a password alone will not sign you in: the sign-in stops and asks for a code before any session is created. Enrolment also issues single-use recovery codes for a lost phone. We store the shared key encrypted, and the recovery codes only as hashes, so neither can be read back out of our database.
  • Every route outside the public marketing pages requires an authenticated session, enforced at the edge before a page renders.
  • Fine-grained authorisation uses five roles — Owner, HR Admin, Manager, Employee, Finance — checked server-side at the point of each action and each protected page, not in the browser. Hiding a button is not access control and we do not treat it as such.
  • Employees in the self-service portal can only reach their own records.

Encryption

  • In transit — all traffic is served over HTTPS/TLS. Connections to our database and to every sub-processor are encrypted in transit.
  • At rest — database and file storage are encrypted at rest by our infrastructure providers (Neon for Postgres, Vercel Blob for files).
  • Application-level field encryption — statutory identifiers (PAN, Aadhaar, UAN and ESIC number) and bank account numbers are additionally encrypted by the application with AES-256-GCM before they are stored, under a key held in the deployment environment and never in the database. A copy of the database on its own does not reveal them. Other identifier fields are protected by the provider's at-rest encryption and by our access controls; extending application-level encryption to them is a known hardening item.

Document storage

Uploaded files — ID proofs, cancelled cheques, investment proofs — go to private storage with no publicly fetchable URL. Every read is served through an authorised application route that re-checks the requesting user's organisation and role on each request. Uploads are limited to PDF, PNG, JPEG and WEBP, capped at 10 MB, and every upload and deletion writes an audit entry.

If file storage is not configured in a production deployment, uploads fail loudly rather than silently falling back to local disk. A visible failure at upload time is far cheaper than discovering months later that ID proofs went somewhere they should not have.

Audit logging

Sensitive changes write an immutable audit record capturing the actor, the entity and record affected, the action (create, update, delete, login, export, finalise, lock), a diff of what changed, the timestamp, and where captured, IP address and user agent. Salary revisions, leave decisions, payroll finalisation, document uploads and exports are all covered.

Audit rows are organisation-scoped and are not editable or deletable from the application at any role.

Handling of sensitive values

Salary figures, PAN, Aadhaar and bank details are never written to application logs. Document filenames are treated as sensitive too, since a filename alone can disclose what a document is. This is enforced as a codebase rule and reviewed in changes that touch these paths.

Payroll integrity

Payroll runs are idempotent and period-locked: running the same period twice cannot double-pay. Finalisation locks the period and is recorded in the audit log. Money is stored as integer paise throughout — never as floating point — so rounding cannot drift.

DonkeyHR does not move money. We generate a bank advice file that your finance team uploads to your own corporate banking portal. We hold no payment mandate and cannot initiate a transfer, which removes an entire category of risk from the product.

Infrastructure

The application runs on Vercel with a managed Neon PostgreSQL database. Backup, point-in-time recovery and high availability are provided by those platforms. To be completed: our documented backup retention window, tested restore procedure, and any recovery-time or recovery-point commitment are not yet finalised. We will not quote an RTO/RPO we have not tested.

Reporting a vulnerability

Email hr@thynkblox.com with enough detail to reproduce the issue. We will acknowledge your report and keep you updated while we work on it. Please give us a reasonable window to fix before public disclosure, and please do not access, alter or exfiltrate other customers' data while testing.

To be completed: we do not currently run a paid bug-bounty programme, and our formal acknowledgement and remediation SLAs are not yet set.

Incident response and breach notification

We maintain an internal incident-response runbook with severity levels and a payroll-specific rule to mitigate customer impact before chasing root cause.

CERT-In. Thynkblox AI Private Limited is subject to the directions issued by the Indian Computer Emergency Response Team on 28 April 2022 under section 70B(6) of the Information Technology Act, 2000. We report the cyber incidents specified in those directions to CERT-In within six hours of noticing them or being notified of them, and we maintain a designated point of contact for CERT-In. Our point of contact is the Data Protection Officer, thynkblox@gmail.com.

DPDP. Under the Digital Personal Data Protection Act, 2023, a personal-data breach must be intimated to the Data Protection Board of India and to affected Data Principals. Where we act as Data Processor for a customer's employee data, that duty is the customer's; we notify the affected customer organisation without undue delay and in any event within seventy-two hours of becoming aware, with the categories of data and Data Principals affected, the likely consequences, the measures taken and a contact point, and we support them in making their own intimation. Where we are ourselves the Data Fiduciary — for account holders and prospects — we make the intimation directly. This commitment is mirrored in clause 6.5of our Data Processing Agreement.

Logs

We enable and securely maintain logs of the systems that operate the service for a rolling period of 180 days, as the CERT-In directions require, and make them available to CERT-In on a lawful order. Application audit records — described above — are retained separately and for longer, as the record of who changed what, for [To be completed: audit log retention period].

Two related points are not settled yet, and we would rather say so than imply otherwise. The CERT-In directions also require system clocks to be synchronised to the NPL or NIC time source: the source in use is [To be completed: NTP source used to synchronise system clocks (NPL or NIC)]. Whether these system logs are held in, or retrievable into, Indian jurisdiction is [To be completed: system log retention period and jurisdiction]. Both are recorded in Annexure A of our Data Processing Agreement and will be stated here as soon as they are confirmed.

For procurement reviewers

If you are running a security review for a 200+ employee deal, contact hr@thynkblox.com or book a demo and bring your reviewer. We will complete your questionnaire and answer directly on anything marked “To be completed” above, including where we simply have not built the control yet.

Related: privacy policy (data inventory, sub-processors, retention, data-subject rights) and terms of service.