DonkeyHR

Privacy policy

DonkeyHR is HR and payroll software. Almost everything in it is personal data about someone's employment. This page explains exactly what we hold, why, and what you can make us do about it.

Last updated: 3 November 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.

1. Who we are, and which hat we wear

Thynkblox AI Private Limited (“DonkeyHR”, “we”, “us”) operates DonkeyHR, a multi-tenant HR and payroll platform. Registered office: Kanadia Road, Indore, Madhya Pradesh, India. CIN: U62099MP2026PTC084823.

India's Digital Personal Data Protection Act, 2023 (DPDP Act) is the governing regime for this policy. The distinction below matters, because it decides who you should contact:

  • For employee data — the employer organisation that subscribes to DonkeyHR is the Data Fiduciary. They decide what employee data goes in and why. We are their Data Processor, acting on their instructions. If you are an employee of a DonkeyHR customer, your first point of contact is your own HR team.
  • For our own customers and prospects — the account holders who sign up, and people who fill in our demo form — we are the Data Fiduciary ourselves.

2. What personal data we process, and why

This list is derived from the actual database schema, not from a template. If it is not here, we do not store it.

Employee records, entered by your employer

DataWhy it exists
Name, date of birth, gender, personal and work email, phone, employee code, photoIdentifying an employee across payroll, leave and letters.
Permanent, current and emergency addressesStatutory records, professional-tax state determination, and emergency contact.
Statutory identifiers — PAN, Aadhaar, UAN, ESIC, passport, driving licenceMandatory for PF, ESI, professional tax and TDS filings. Aadhaar is only held where the employer requires it for statutory enrolment.
Bank account number, IFSC, bank and branch nameGenerating the bank advice file the employer uploads to their own banking portal. DonkeyHR does not move money — see Security.
Employment records — designation, department, joining and exit dates, employment type and status, reporting managerApproval routing, tenure calculations, letters.
Salary structure, components, revisions, payroll runs and payslip linesComputing and recording pay, PF, ESI, PT and TDS. Retained as the statutory payroll record.
Leave requests, balances and daily attendanceLeave entitlement, loss-of-pay calculation and payroll accuracy.
Income-tax declarations, chosen tax regime, and uploaded investment proofsComputing TDS correctly across the financial year.
Uploaded documents — ID proofs, contracts, declaration proofsEmployer record-keeping. Stored in private storage and served only through an authorised route that re-checks organisation and role on every single request.
Generated letters and their rendered snapshotsOffer, appointment, relieving, experience and increment letters must reproduce byte-for-byte later, so the rendered output is stored alongside the inputs.

Account and operational data

  • Sign-in identity — your email address and a one-way cryptographic hash of your password (scrypt). We hold these ourselves rather than through a third-party identity provider. The hash cannot be reversed to recover your password, and your password is never written to our database, our logs or our backups in a readable form.
  • Sessions — when you sign in we store a hash of your session token, its expiry, and the IP address and browser the session was created from. The IP and browser are kept as an evidentiary record only; they are never used to decide whether you are allowed in. Signing out, or changing your password, invalidates the session on our side and not merely in your browser.
  • Audit logs — for every sensitive change we record who acted, which record changed, what the change was, the timestamp, and where captured, the IP address and user agent. This exists precisely so a payroll or salary change can be reconstructed later, and it is not something you can opt out of while using the product.
  • In-app feedback — anything you submit through the feedback widget, plus the page you were on.
  • Notifications — the record of messages we generated for you (payslip ready, leave approved, declaration due).

Prospect data (our own marketing)

If you submit our demo form we store your name, work email, company, employee-count band, and optionally your current payroll tool, phone number, and message. We use it to contact you about DonkeyHR and to route you to the right sales motion — nothing else. It is not sold, and it is not shared with advertisers.

Marketing attribution cookies

When you arrive on our marketing pages from an advertisement, a search result, a partner's link or another website, we set two first-party cookies (dh_ft and dh_lt) recording how that visit reached us. They hold only:

  • the campaign tags on the link you clicked (the utm_source, utm_medium, utm_campaign, utm_term and utm_content values we ourselves put there);
  • the domain name of the site you came from — for example google.co.in. We deliberately do not keep the full referring address, so the search terms you typed never reach us;
  • the path of the page you landed on, without its query string;
  • the date and time of the visit.

They contain no name, no email address, no identifier for you, and no browsing history. They are not readable by JavaScript, they are not sent to any other company, and they cannot follow you to another website. They expire after 90 days. If you later submit the demo form or create an account, the same two values are recorded against that lead or organisation so we can tell which of our own marketing efforts is worth continuing — the first visit and the most recent one. That is the entirety of the purpose. You can delete these cookies in your browser at any time; nothing on the site stops working if you do.

What we deliberately do not do

  • We do not write salary figures, PAN, Aadhaar or bank details to application logs. This is a standing engineering rule in this codebase, not an aspiration.
  • We do not sell personal data, and we do not use employee data to train machine-learning models.
  • We run no third-party advertising or cross-site tracking pixels on the application or on the marketing site.
  • We use Google Analytics on public pages only: the marketing site, the calculators, the blog, the legal pages and the sign-in page. It never loads once you are signed in. Without your consent, a cookieless measurement of visits and pages viewed is still sent to Google. It includes your IP address and browser details, and events such as scrolling to the end of a page. We remove the query string from the page addresses we send. Analytics cookies are set only after you choose Accept on the cookie banner. If you choose Decline, or make no choice, no analytics cookies are set. Your choice is saved in this browser. To change it, select Cookie settings at the bottom of the page. If you withdraw consent, the analytics cookies are removed and the cookieless measurement continues.
  • We do not build a profile of your browsing, and we do not track individual employees' use of the product for marketing purposes. Our own product analytics are counts per organisation — how many companies reached a first payroll run, and how long it took. An employee is a number in that data, never a name. These counts, and plan clicks on the pricing page, are sent from our servers to PostHog, listed in the sub-processor table below. Each message carries the event name, the organisation identifier and where in the product it happened, and never a name, email address or phone number. A plan click on the pricing page carries a random identifier made for that one click instead, which we do not keep and which is not linked to you. Your browser does not talk to PostHog and no cookie is set for it.

3. Legal basis

Where we act as a Data Processor for employee data, the lawful basis is the employer's, not ours. We process only on the employer's documented instructions, on the terms set out in our Data Processing Agreement.

Where we act as Data Fiduciary — for account holders and prospects — we rely on consent under section 6 of the DPDP Act, on the legitimate use in section 7 for data you give us voluntarily for a specified purpose, and on compliance with our own legal obligations.

4. Tenant isolation and who can see what

Every record that belongs to a customer carries that organisation's identifier, and all application access to that data goes through a single tenant-scoping layer that injects the organisation filter on every read and write. Two customers cannot see each other's data through the application.

Within an organisation, access is further limited by role — Owner, HR Admin, Manager, Employee and Finance. An employee sees their own records; a manager sees what they need to approve. See Security for detail.

5. Sub-processors

We use the following providers to run the service. Each processes personal data only to deliver its function.

Sub-processorFunctionData involved
VercelApplication hosting, serverless compute, scheduled jobs, and file storage (Vercel Blob)All application data in transit; uploaded documents at rest
NeonManaged PostgreSQL databaseAll application data at rest
Google (Gmail SMTP)Transactional email deliveryRecipient email address and message content (e.g. a payslip notification with a net-pay figure)
Google (Google Analytics)Measurement of visits and pages viewed on public pages.IP address, browser details and pages viewed. Cookies only after Accept. No employee or payroll data.
PostHog (United States)Product analytics. The event is sent from our servers, not from your browser, and only when an analytics key is configured.The organisation identifier and the name of the event. No employee data, no names, no amounts.

Where processing happens. Our application and database are hosted in [To be completed: Vercel function region and Neon project region]. Personal data is therefore processed outside India. Section 16 of the DPDP Act permits transfer to any country other than one the Central Government restricts by notification, and no such restriction currently applies to the countries listed above. We contract with each sub-processor on terms requiring equivalent protection, as clause 8 of our Data Processing Agreement records.

We will maintain this list and give customers at least thirty days' notice before adding or replacing a sub-processor that processes personal data. A customer that reasonably objects on data-protection grounds may terminate the affected service without penalty for the unexpired term.

6. Retention

Payroll and statutory records carry retention obligations under Indian law that outlive employment — income-tax, PF and ESI records in particular. We therefore retain employee payroll data for as long as the employer's subscription is active, and thereafter as needed to meet those obligations.

  • Erasing an employee record always removes their addresses, bank details, statutory identifiers, documents, letters, leave, attendance and declarations, and ends any login they had. If they have never been paid from a finalised payroll period, the record itself is deleted as well. If they have, the record is anonymised instead: their name, email, phone, date of birth and gender are overwritten, and what is left is the employee code, the employment dates and the payroll amounts we are required to keep. Nothing that identifies the person survives either way.
  • Deleting an organisation cascades to all of that organisation's data, including its audit logs.
  • Audit logs are immutable in normal operation. They are the record of who changed what, so they are not editable from the application by anyone, at any role.
  • Prospect data from the demo form is kept while it is commercially relevant and deleted on request.
  • Marketing attribution cookies expire after 90 days. The campaign values copied onto a lead or an organisation are kept for as long as that record is, because they are how we account for our own marketing spend.

Retention periods by category. Data held for an active subscription is retained for the subscription term. Beyond that:

CategoryRetention
Payroll registers, payslips and TDS recordsEight years from the end of the relevant financial year, to meet income-tax and PF/ESI record-keeping obligations
Attendance and leave recordsThree years
Audit logs[To be completed: audit log retention period]
Prospect dataTwenty-four months from last contact
Account data after terminationDeleted ninety days after termination, subject to the statutory categories above

7. Your rights under the DPDP Act

As a Data Principal you have the right to:

  • Access — a summary of the personal data we process about you and who it has been shared with.
  • Correction and completion — have inaccurate or incomplete data corrected. Employees can already self-edit parts of their profile in the self-service portal; the rest goes through HR.
  • Erasure — have data deleted where we are not required to retain it for a legal purpose. Statutory payroll records are the main case where we cannot comply immediately.
  • Portability — receive your data in a usable form. Payroll registers, bank advice and payslips already export from the product; for anything else, ask.
  • Grievance redressal — raise a complaint with us first, and escalate to the Data Protection Board of India if we do not resolve it.
  • Nominate another person to exercise these rights on your behalf in the event of death or incapacity.

If you are an employee of a DonkeyHR customer, send these requests to your employer's HR team first — they control the data and we act on their instructions. If they route it to us, we will act on it.

8. How to reach us

Privacy requests: hr@thynkblox.com. Security reports: hr@thynkblox.com. Post: Kanadia Road, Indore, Madhya Pradesh, India.

Grievance redressal and Data Protection Officer

We have appointed a Data Protection Officer as the point of contact for questions, requests and grievances about the personal data we process, and as our designated point of contact for the Indian Computer Emergency Response Team (CERT-In).

Data Protection Officer
Thynkblox AI Private Limited
Kanadia Road, Indore, Madhya Pradesh, India
Email: thynkblox@gmail.com

We acknowledge every request or grievance within three working days and give a substantive response within thirty days of receiving a verifiable request. If your request concerns data we hold on behalf of your employer, we forward it to your employer within three working days and tell you that we have done so.

If you are not satisfied with our response, you may complain to the Data Protection Board of India.

Thynkblox AI Private Limited

Corporate Identity Number: U62099MP2026PTC084823

Registered office: Kanadia Road, Indore, Madhya Pradesh, India

Operating the DonkeyHR platform at https://hrapp.thynkblox.com

Data Protection Officer: thynkblox@gmail.com

9. Changes to this policy

We will post material changes here and notify account holders by email. The “last updated” date at the top always reflects the current version.