Draft. This document is a working draft and has not yet been reviewed by a lawyer. It is not in force and must be replaced with approved text before launch.
Version 2026-11-draft
Data Processing Agreement
This agreement is part of the Terms of Service between ("Processor") and the company that subscribes ("Controller"). It applies to the personal data of candidates, employees, clients and other people that the Controller puts into the platform ("Customer Data"). Last updated: [date]. [Draft: have a lawyer finish and approve this before relying on it.]
What is processed, and why
- Subject matter: running the Controller's recruitment, onboarding, e-signature, employee records and exit processes on the platform.
- Duration: for as long as the subscription lasts, plus the period in which the Controller can export its data.
- Kinds of personal data: names, contact details, résumés and work history, application and interview records, onboarding forms and uploaded documents, signatures, licence and credential details, equal-opportunity answers where the Controller collects them, and records of who did what in the platform.
- Kinds of people: candidates, employees and former employees, referees, client contacts, and the Controller's own staff.
What the Processor promises
- To process Customer Data only on the Controller's documented instructions, which are the Terms of Service and what the Controller does in the platform, unless the law requires otherwise.
- To make sure everyone who can access Customer Data is bound to keep it confidential.
- To keep Customer Data secure with the measures described on our Trust and security page, including encryption of sensitive numbers, separation between companies, access controls, and an audit log.
- To use only the sub-processors on our published list, to bind them to the same duties, and to tell the Controller before adding one that handles Customer Data, so the Controller can object.
- To help the Controller answer requests from people about their data (access, correction, deletion, export) using the tools in the platform, and to tell the Controller if someone contacts us directly.
- To tell the Controller without undue delay [and within 72 hours] after becoming aware of a personal data breach affecting Customer Data, with the facts we have.
- To delete or return Customer Data when the subscription ends, as set out in the Terms of Service, and to delete remaining copies afterwards except where the law requires keeping them.
- To give the Controller the information needed to show that these duties are met, and to allow reasonable audits [on notice, once a year, at the Controller's cost], or to provide an independent report where one exists.
What the Controller is responsible for
- Having a lawful reason to collect and use the data it enters, and telling people about it (for example in its own privacy notice).
- Choosing who in its company can see what, using the roles in the platform.
- Using the platform's data-erasure and retention settings to fit the laws that apply to it.
Transfers
Customer Data is stored in [region]. [If data is moved outside the Controller's country, describe the safeguards, for example standard contractual clauses.]
Liability and changes
[Liability terms as in the Terms of Service.] If the law changes in a way that requires different terms, the parties will agree an update in good faith.
Contact
, . support@hireflux.tech.