DonkeyHR

Data Processing Agreement

How we process your employees' personal data on your instructions, as section 8(2) of the Digital Personal Data Protection Act, 2023 requires. This agreement applies automatically from the moment you create an account.

Last updated: 9 September 2026

Draft — awaiting review by counsel. This Data Processing Agreement is published so that customers can read the terms we will sign, but it has not yet been reviewed by an Indian advocate. Terms still to be settled are highlighted in the text below. If you are evaluating DonkeyHR through procurement, write to thynkblox@gmail.com and we will tell you exactly where each one stands.

Version 1.0 — effective [To be completed: DPA effective date]

This Data Processing Agreement (“DPA”) forms part of, and is incorporated by reference into, the DonkeyHR terms of service or such other written agreement for the DonkeyHR platform between the parties (the “Principal Agreement”). It records the terms on which Thynkblox processes personal data on the Customer's behalf, and is entered into to satisfy section 8(2) of the Digital Personal Data Protection Act, 2023.

Where this DPA conflicts with the Principal Agreement in respect of the processing of personal data, this DPA prevails.

1. Parties

(1) Thynkblox AI Private Limited, a private limited company incorporated under the Companies Act, 2013, bearing Corporate Identity Number U62099MP2026PTC084823, having its registered office at Kanadia Road, Indore, Madhya Pradesh, India (“Thynkblox”, “we”, “us”, “our”), operating the DonkeyHR platform at https://hrapp.thynkblox.com; and

(2) The Customer identified in the Principal Agreement or the applicable order form (the “Customer”, “you”, “your”).

Each a “Party” and together the “Parties”.

2. Definitions

Terms defined in the DPDP Act have the meaning given there. In this DPA:

  • “Aadhaar” means an Aadhaar number as defined in the Aadhaar (Targeted Delivery of Financial and Other Subsidies, Benefits and Services) Act, 2016.
  • “Applicable Data Protection Law” means the Digital Personal Data Protection Act, 2023 and the rules made under it (including the Digital Personal Data Protection Rules, 2025), the Information Technology Act, 2000 (in particular sections 43A and 72A) and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, the directions issued by the Indian Computer Emergency Response Team on 28 April 2022 under section 70B(6) of the Information Technology Act, 2000, and any other law applicable to the processing of personal data under this DPA, in each case as amended, replaced or brought into force from time to time.
  • “Board” means the Data Protection Board of India constituted under the DPDP Act.
  • “CERT-In” means the Indian Computer Emergency Response Team.
  • “Customer Personal Data” means personal data contained in Customer Data that Thynkblox processes on the Customer's behalf under the Principal Agreement.
  • “Data Fiduciary”, “Data Principal”, “Data Processor”, “personal data”, “personal data breach” and “processing” have the meanings given in section 2 of the DPDP Act.
  • “DPDP Act” means the Digital Personal Data Protection Act, 2023.
  • “Personal Data Breach” means any unauthorised processing of personal data, or accidental disclosure, acquisition, sharing, use, alteration, destruction of or loss of access to personal data, that compromises its confidentiality, integrity or availability.
  • “Sub-Processor” means any third party engaged by Thynkblox to process Customer Personal Data on Thynkblox's behalf in connection with the DonkeyHR platform.

3. Roles of the Parties

3.1 In respect of Customer Personal Data, the Customer is the Data Fiduciary and Thynkblox is the Data Processor. The Customer determines the purposes and means of the processing; Thynkblox processes only on the Customer's documented instructions.

3.2 Thynkblox is the Data Fiduciary in respect of personal data it determines the purposes and means for, including account-holder registration data, billing contacts, prospect and enquiry data, and data processed for Thynkblox's own security, fraud-prevention, legal-compliance and service-operation purposes. That processing is governed by the DonkeyHR privacy policy and not by this DPA.

3.3 Each Party is independently responsible for its compliance with Applicable Data Protection Law in respect of the processing for which it is the Data Fiduciary.

3.4 Thynkblox does not sell Customer Personal Data, does not disclose it for consideration, and does not use it to train machine-learning or artificial-intelligence models.

4. Subject matter, duration, nature and purpose of the processing

4.1 Subject matter. The provision of the DonkeyHR human-resources and payroll platform to the Customer under the Principal Agreement.

4.2 Duration. From the effective date of the Principal Agreement until the later of (a) the termination or expiry of the Principal Agreement and (b) the completion of the deletion or return obligations in clause 10.

4.3 Nature of the processing. Collection, recording, organisation, structuring, storage, retrieval, computation, consultation, use, generation of documents and files, disclosure by transmission to the Customer and to recipients the Customer designates, restriction, erasure and destruction — in each case by automated means through the DonkeyHR platform and by Thynkblox personnel to the limited extent needed to support and operate it.

4.4 Purposes. Solely to provide, maintain, secure and support the DonkeyHR platform for the Customer, namely: employee record management; payroll computation including provident fund, employees' state insurance, professional tax and tax deducted at source; generation of payslips, payroll registers and bank advice files; leave and attendance management; employee self-service; income-tax declaration capture and computation; generation and storage of employment letters; document storage; notification and transactional email; audit logging; and technical support requested by the Customer.

5. Categories of personal data and Data Principals

5.1 Categories of Data Principal. The Customer's employees (current and former), workers, contractors and, where the Customer chooses to record them, job applicants and employees' nominated dependants and emergency contacts; and the Customer's authorised platform users.

5.2 Categories of Customer Personal Data.

CategoryExamples
Identity and contactName, employee code, date of birth, gender, personal and work email, telephone number, photograph, permanent, current and emergency addresses, emergency contact details
Statutory identifiersPermanent Account Number (PAN), Aadhaar, Universal Account Number (UAN), ESIC number, passport number, driving licence number
FinancialBank account number, IFSC, bank and branch name
EmploymentDesignation, department, joining and exit dates, employment type and status, reporting manager
CompensationSalary structure, salary components, salary revisions, payroll run records, payslip lines, statutory deductions
Time and absenceLeave requests, leave balances, daily attendance
TaxIncome-tax declarations, elected tax regime, uploaded investment proofs
DocumentsUploaded identity proofs, contracts, cancelled cheques, declaration proofs
Generated recordsOffer, appointment, relieving, experience and increment letters and their rendered snapshots
Platform account and operationalEmail address, password hash (scrypt), session token hash, session expiry, session IP address and user agent, multi-factor authentication secret (encrypted) and recovery code hashes, audit log entries recording actor, entity, action, change diff, timestamp, IP address and user agent, in-app feedback, notification records

5.3 Sensitive categories. The Parties acknowledge that Customer Personal Data includes financial information and passwords, which are sensitive personal data or information under the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011, and may include Aadhaar. The Customer will not instruct Thynkblox to process Aadhaar for any purpose other than the Customer's own statutory enrolment and record-keeping obligations, and acknowledges that Thynkblox does not use Aadhaar for authentication.

5.4 No special-category data by design. The DonkeyHR platform is not designed to hold health records, biometric templates, or trade-union or political-affiliation data. The Customer will not upload such data to free-text or document fields, and Thynkblox has no obligation in respect of data uploaded in breach of this clause beyond the security measures it applies generally.

6. Thynkblox's obligations as Data Processor

6.1 Processing on instructions only. Thynkblox will process Customer Personal Data only on the Customer's documented instructions, which comprise the Principal Agreement, this DPA, the Customer's configuration and use of the platform, and any further written instruction the Parties agree. Thynkblox will process outside those instructions only where required by law, in which case it will inform the Customer of the requirement before processing unless the law prohibits that notice. If Thynkblox considers an instruction to breach Applicable Data Protection Law it will inform the Customer without undue delay and may suspend that processing.

6.2 Confidentiality. Thynkblox will ensure that every person it authorises to process Customer Personal Data is subject to a written duty of confidentiality that survives the end of their engagement, is trained appropriately, and is granted access only to the extent needed to perform their role. Thynkblox operates access on a least-privilege basis and reviews access grants at least [To be completed: access review frequency (for example, quarterly)].

6.3 Security measures. Thynkblox will implement and maintain the technical and organisational measures set out in Annexure A, which describes the controls actually implemented in the platform as at the version date of this DPA. Thynkblox will not degrade those measures during the term. Thynkblox will keep those measures under review and update Annexure A on publication of a new version of this DPA.

6.4 Assistance with Data Principal requests. Taking into account the nature of the processing, Thynkblox will assist the Customer by appropriate technical and organisational measures, insofar as possible, in fulfilling the Customer's obligation to respond to requests by Data Principals to exercise their rights under Chapter III of the DPDP Act (access, correction and completion, updating, erasure, grievance redressal, and nomination). Where Thynkblox receives such a request directly from a Data Principal in respect of Customer Personal Data, it will not respond substantively but will forward the request to the Customer within three working days and inform the requester that it has done so. Where the platform provides self-service or administrator functionality that satisfies the request, Thynkblox's assistance is discharged by that functionality; where it does not, Thynkblox will provide reasonable assistance and may charge its reasonable costs for assistance that is repetitive or manifestly excessive.

6.5 Personal Data Breach. Thynkblox will notify the Customer of a Personal Data Breach affecting Customer Personal Data without undue delay after becoming aware of it, and in any event within seventy-two hours. The notification will describe, to the extent then known: the nature of the breach, including where possible the categories and approximate number of Data Principals and records concerned; the likely consequences; the measures taken or proposed to address it and to mitigate its adverse effects; the broad facts and circumstances relating to how it occurred; and the name and contact details of the Thynkblox contact point. Where the information is not all available at once, Thynkblox will provide it in phases without undue further delay.

Thynkblox will provide the Customer with reasonable cooperation and information to enable the Customer to make its own intimation to the Board and to affected Data Principals within the periods Applicable Data Protection Law prescribes, and will not make any public statement identifying the Customer without the Customer's prior written consent, except where required by law or by a regulator.

Thynkblox will make its own report to CERT-In within six hours where the incident falls within the categories specified in the CERT-In directions of 28 April 2022, and will inform the Customer that it has done so.

6.6 Logs. Thynkblox will enable and securely maintain logs of the information and communications technology systems operating the platform for a rolling period of 180 days, and will make them available to CERT-In on a lawful order. Application audit records are retained for [To be completed: audit log retention period].

6.7 Assistance with security, breach and impact obligations. Thynkblox will provide the Customer with reasonable assistance in respect of the Customer's obligations to maintain reasonable security safeguards, to respond to a Personal Data Breach, and to respond to any enquiry, direction or proceeding of the Board or of CERT-In relating to Customer Personal Data.

6.8 Data Protection Officer. Thynkblox has appointed a Data Protection Officer whose business contact is published on its website and is: Data Protection Officer, Thynkblox AI Private Limited, Kanadia Road, Indore, Madhya Pradesh, India — thynkblox@gmail.com.

7. Sub-Processors

7.1 General authorisation. The Customer gives Thynkblox a general authorisation to engage Sub-Processors, subject to this clause 7.

7.2 Current Sub-Processors. As at the version date of this DPA, Thynkblox engages the following Sub-Processors.

Sub-ProcessorFunctionCustomer Personal Data involvedLocation of processing
Vercel Inc. (United States)Application hosting, serverless compute execution, scheduled jobs, edge routingAll Customer Personal Data in transit and in transient compute[To be completed: Vercel function execution region]
Vercel Inc. — Vercel Blob (United States)Private object storage for uploaded documents, identity proofs, investment proofs and rendered lettersUploaded documents and generated letter snapshots, at rest[To be completed: Vercel Blob storage region]
Neon Inc. (United States)Managed PostgreSQL databaseAll Customer Personal Data at rest[To be completed: Neon project region]
Google LLC (United States) — Gmail SMTPTransactional email delivery: invitations, payslip notifications, leave and declaration notifications, letter issuanceRecipient name and email address, and message content, which for payslip notifications includes a net-pay figureUnited States and such other regions as Google operates
Functional Software, Inc. (Sentry) — error monitoringApplication error and exception reporting from the server runtime. Sensitive values are excluded from reports by design.Error context, which may include an account email address and a request path[To be completed: region in which Sentry processes error reports]
PostHog Inc. (United States)Product analytics. Events are sent from the Thynkblox server runtime, not from any browser, and only when an analytics key is configured.The Customer's organisation identifier and the name of the event. No Data Principal identifiers, no payroll amounts, no free text.United States

7.3 Sub-Processor obligations. Thynkblox will impose on each Sub-Processor, by written contract, data-protection obligations no less protective than those in this DPA, and remains fully liable to the Customer for each Sub-Processor's performance of those obligations.

7.4 Change notice and objection. Thynkblox will give the Customer at least thirty days' prior notice of the addition or replacement of a Sub-Processor, by email to the Customer's notified administrative contact and by updating the published Sub-Processor list. The Customer may object on reasonable data-protection grounds within that period. The Parties will discuss the objection in good faith; if it cannot be resolved, the Customer may terminate the affected part of the Principal Agreement without penalty, with a pro-rata refund of pre-paid fees for the unexpired term.

8. Cross-border transfer

8.1 The Customer acknowledges and instructs that Customer Personal Data may be transferred to and processed in countries outside India by the Sub-Processors identified in clause 7.2, at the locations stated there.

8.2 Section 16 of the DPDP Act permits the transfer of personal data to any country or territory outside India other than one the Central Government restricts by notification. Thynkblox will not transfer Customer Personal Data to any country the Central Government has so restricted. If a restriction is notified in respect of a country where a Sub-Processor processes Customer Personal Data, Thynkblox will migrate that processing to a permitted location, or terminate the affected Sub-Processor engagement, in each case within the period the notification allows and, absent a stated period, without undue delay.

8.3 Where the Customer is subject to a sectoral direction requiring in-country storage — including any direction of the Reserve Bank of India or of another sectoral regulator applicable to the Customer — the Customer must notify Thynkblox before uploading data to which the direction applies. India-resident hosting: [To be completed: whether an India-resident hosting option is offered].

8.4 Thynkblox will maintain, for each transfer, contractual terms with the recipient requiring protection of the transferred data equivalent to that required under this DPA.

9. Customer obligations

9.1 Lawful basis and notice. The Customer warrants that it has a lawful basis under the DPDP Act for each processing operation it instructs, that it has given each Data Principal the notice section 5 of the DPDP Act requires, and that, where consent is the basis, it has obtained and records that consent.

9.2 Accuracy and completeness. The Customer is responsible for the accuracy, quality and legality of the Customer Personal Data it uploads, including salary structures, statutory identifiers, state of employment, attendance and leave, and for correcting them.

9.3 Access control. The Customer is responsible for assigning platform roles appropriately, for the acts and omissions of its authorised users, for promptly revoking access for people who leave, and for notifying Thynkblox immediately of any suspected unauthorised access.

9.4 Review of output. The Customer is responsible for reviewing payroll output before relying on it for a statutory filing or a payment. Thynkblox computes figures from the data and configuration the Customer supplies and provides a bank advice file that the Customer submits to its own bank; Thynkblox holds no payment mandate and does not move funds.

9.5 Data Principal requests and grievances. The Customer is responsible, as Data Fiduciary, for responding to Data Principal requests and grievances concerning Customer Personal Data, and for its own intimations to the Board and to Data Principals following a Personal Data Breach.

9.6 Prohibited data. The Customer will not upload personal data of individuals who are not its workers, contractors, applicants or their nominated dependants and emergency contacts, nor data for which it has no lawful basis.

10. Deletion or return on termination

10.1 On termination or expiry of the Principal Agreement, Thynkblox will, at the Customer's election, delete or return Customer Personal Data, and delete existing copies, save to the extent that Applicable Data Protection Law or another law requires continued storage.

10.2 The Customer may export Customer Personal Data through the platform at any time while the Principal Agreement is in force, and for thirty days after its termination or expiry Thynkblox will retain the data and provide read-only export access on request.

10.3 After that thirty-day window, Thynkblox will delete or anonymise Customer Personal Data within a further [To be completed: deletion window after the thirty-day export period (for example, 60 days)], except for data it is required to retain by law, which it will retain in accordance with the published retention schedule and process only for the purpose of that legal obligation.

10.4 Deletion of an employee record within the platform removes addresses, bank details, statutory identifiers, documents, letters, leave, attendance and declarations, and ends any login. Where the employee has been paid from a finalised payroll period, the record is pseudonymised rather than deleted: name, email, telephone, date of birth and gender are overwritten, and the employee code, employment dates and payroll amounts required for statutory record-keeping remain. The Customer, holding its own records, may still be able to link an employee code to an individual; Thynkblox cannot.

10.5 On written request Thynkblox will certify in writing that it has complied with this clause 10.

11. Audit and information rights

11.1 Thynkblox will make available to the Customer, on written request and no more than once in any twelve-month period (or more often following a Personal Data Breach affecting the Customer or where a regulator requires it), the information reasonably necessary to demonstrate compliance with this DPA. That information comprises the current Annexure A, the current Sub-Processor list, Thynkblox's responses to the Customer's reasonable written security questionnaire, and any third-party audit report or certification Thynkblox then holds.

11.2 Thynkblox does not currently hold a SOC 2 report, ISO/IEC 27001 certification or any other third-party security certification or audit report, and has not completed an independent penetration test. It will inform the Customer if that position changes.

11.3 Where the information provided under clause 11.1 does not reasonably satisfy the Customer, the Customer may, on thirty (30) days' written notice, conduct or appoint an independent auditor (not a competitor of Thynkblox, and bound by confidentiality) to conduct an audit of Thynkblox's processing of Customer Personal Data. Audits will take place during business hours, will not unreasonably disrupt Thynkblox's operations, will not extend to other customers' data or to Thynkblox's confidential commercial information, and will be at the Customer's cost unless the audit reveals a material breach of this DPA.

11.4 Thynkblox will not provide physical access to Sub-Processor facilities; in respect of Sub-Processors it will provide such audit information as it is contractually entitled to obtain.

12. Liability

12.1 Each Party's liability arising out of or in connection with this DPA is subject to the exclusions and limitations of liability set out in the Principal Agreement, and any reference in the Principal Agreement to a Party's liability means that Party's aggregate liability under the Principal Agreement and this DPA taken together.

12.2 Nothing in this DPA limits a Party's liability to a Data Principal, or its liability to the Board or to any other regulator, or any liability that cannot be limited or excluded under Applicable Data Protection Law.

13. Term, variation and general

13.1 Term. This DPA takes effect on the effective date of the Principal Agreement and continues until clause 10 is discharged.

13.2 Variation. Thynkblox may publish an updated version of this DPA to reflect a change in Applicable Data Protection Law, in the platform, or in its Sub-Processors. It will give the Customer at least thirty (30) days' notice of a material change. Where a change materially reduces the protection afforded to Customer Personal Data and the Customer reasonably objects, the Customer may terminate the affected part of the Principal Agreement without penalty.

13.3 Severability. If any provision of this DPA is held invalid or unenforceable, the remainder continues in force.

13.4 Notices. Notices under this DPA are given in writing to the Data Protection Officer at thynkblox@gmail.com (for Thynkblox) and to the Customer's notified administrative contact.

14. Governing law and jurisdiction

14.1 This DPA is governed by and construed in accordance with the laws of India.

14.2 The courts at Indore, Madhya Pradesh, India have exclusive jurisdiction over any dispute arising out of or in connection with this DPA, and each Party submits to that jurisdiction.

15. Signature

This DPA applies automatically from the moment you create an account. A countersigned copy for your records is available on request from our Data Protection Officer at thynkblox@gmail.com, signed for Thynkblox AI Private Limited by [To be completed: signatory name for Thynkblox AI Private Limited], [To be completed: signatory designation (for example, Director)], CIN U62099MP2026PTC084823, Kanadia Road, Indore, Madhya Pradesh, India.

Annexure A — Technical and organisational security measures

These are the controls implemented in the DonkeyHR platform as at the version date of this DPA. They are stated as facts, not aspirations. Where a control is not implemented, that is stated.

A.1 Tenant isolation. Every row of customer data carries the owning organisation's identifier. All application access passes through a single tenant-scoping layer that injects the organisation filter into every read, write, update and delete. Cross-tenant reads are not reachable through the application. Two deliberate exceptions hold no employee personal data: webhook delivery records used for idempotency, and inbound marketing leads, which exist before a prospect has an organisation.

A.2 Authentication. First-party authentication. Passwords are stored only as a salted scrypt hash. Sessions are server-side and opaque: the browser holds a random token and only its hash is stored, so a database disclosure yields no usable sessions, and access is revocable immediately. Account creation is invitation-, email-verification- or operator-gated. Sign-in is rate-limited per source address and per email address, with temporary account lockout after repeated failures, and sign-in responses are identical whether or not an email is registered.

A.3 Multi-factor authentication. Optional per account and available to every role, using time-based one-time codes from a standard authenticator application. The shared secret is stored encrypted; single-use recovery codes are stored only as hashes.

A.4 Authorisation. Five roles — Owner, HR Admin, Manager, Employee, Finance — enforced server-side at the point of each action and each protected page, not in the browser. Every route outside the public marketing pages requires an authenticated session, enforced before a page renders. Employees in the self-service portal can reach only their own records.

A.5 Encryption in transit. All traffic is served over HTTPS/TLS. Connections to the database and to every Sub-Processor are encrypted in transit.

A.6 Encryption at rest. The database and file storage are encrypted at rest by the infrastructure providers (Neon for PostgreSQL, Vercel Blob for files).

A.7 Application-level field encryption. Statutory identifiers (PAN, Aadhaar, UAN and ESIC number) and bank account numbers are additionally encrypted in the application with AES-256-GCM, under a key held in the deployment environment and never in the database, so that a database disclosure alone does not reveal them. Remaining identifier fields are protected by the provider's at-rest encryption and by the access controls above; the target date for extending application-level encryption to them is [To be completed: target date for application-level field encryption of the remaining statutory identifiers].

A.8 Document storage. Uploaded files are stored in 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 and capped at 10 MB. Every upload and deletion writes an audit entry. If file storage is not configured in a production deployment, uploads fail rather than falling back to local disk.

A.9 Audit logging. Sensitive changes write an 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, the IP address and user agent. Salary revisions, leave decisions, payroll finalisation, document uploads and exports are covered. Audit rows are organisation-scoped and are not editable or deletable through any application route at any role. They remain deletable by a database administrator; tamper-proof or write-once storage is not claimed.

A.10 Handling of sensitive values in logs. Salary figures, PAN, Aadhaar and bank details are not written to application logs. Document filenames are treated as sensitive because a filename alone can disclose what a document is. This is enforced as a codebase rule reviewed in changes touching these paths.

A.11 System logs. Logs of the systems operating the platform are enabled and securely maintained for a rolling 180 days in line with the CERT-In directions of 28 April 2022, and are produced to CERT-In on a lawful order. System clocks are synchronised to [To be completed: NTP source used to synchronise system clocks (NPL or NIC)]. Configured platform retention and jurisdiction: [To be completed: system log retention period and jurisdiction].

A.12 Payroll integrity. Payroll runs are idempotent and period-locked, so 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. Thynkblox does not move money: it generates a bank advice file the Customer's finance team uploads to the Customer's own corporate banking portal. Thynkblox holds no payment mandate and cannot initiate a transfer.

A.13 Resilience. The application runs on Vercel with a managed Neon PostgreSQL database. Backup, point-in-time recovery and high availability are provided by those platforms. Point-in-time recovery window: [To be completed: Neon point-in-time-recovery window on the current plan]. Documented restore test: [To be completed: whether a documented restore test has been performed, and its date]. No RTO or RPO commitment is published because none has been tested.

A.14 Personnel. Access to production data is limited to personnel who require it, on a least-privilege basis, each under a written confidentiality obligation. Access reviews are conducted [To be completed: access review frequency (for example, quarterly)].

A.15 Independent assurance — not held. No SOC 2 report, ISO/IEC 27001 certification or other third-party security certification or audit report is held, and no independent penetration test has been completed. Timing for a third-party test and for a certification track is [To be completed: penetration test and certification track target dates].

A.16 Vulnerability reporting. Reports are accepted at hr@thynkblox.com. Thynkblox acknowledges reports and keeps reporters updated. No paid bug-bounty programme is operated and formal acknowledgement and remediation service levels are not yet set.