Questions about this agreement? Contact trust@hi-milly.eu.
Data Processing Agreement
This data processing agreement (the “Data Processing Agreement”) forms an integral part of the agreement between the Parties regarding the use of MILLY and applies from the date that agreement enters into force (the “Date of the Data Processing Agreement”).
Between
(1) BV WISEWORKS, a private limited company having its registered offices at Diamantstraat 8-343, 2200 Herentals and registered in the Crossroads Bank for Enterprises (CBE) with company number 0800.113.012 (the “Processor”);
(2) the customer that has entered into an agreement with the Processor for the use of MILLY, as identified in that agreement (the “Controller”).
The parties listed under (1) and (2) above will hereinafter be referred to as “Party”, individually, and as the “Parties”, collectively.
Whereas
(A) The Parties entered into an agreement regarding the use of MILLY, a cloud based multi-tenant SaaS platform (the “Agreement”). Under the Agreement, personal data will be processed. This Data Processing Agreement sets forth in writing the framework within which such processing will occur.
(B) For the purposes of the Data Processing Agreement, the customer is the Controller and BV Wiseworks is the Processor within the meaning of the General Data Protection Regulation (the “GDPR”).
(C) The Parties wish to handle the personal data processed in the performance of the Agreement with care and in accordance with the GDPR and Belgian applicable law.
(D) The Data Processing Agreement sets forth in writing the rights and obligations of the Parties and any data subjects.
(E) The Data Processing Agreement constitutes an implementation of Article 28.3 of the GDPR.
Parties agree as follows:
1. General principles
1.1The Data Processing Agreement applies to all processing of personal data that occurs under the Agreement.
1.2The Processor processes personal data exclusively by order of the Controller and based on its instructions. The Controller bears sole responsibility for the lawfulness of these instructions. The Controller also determines the purpose and means of processing. In Annex 1 to the Data Processing Agreement, the Controller specifies the processing operations that take place.
1.3If the Processor considers that any instruction given by the Controller infringes the GDPR or other applicable data protection provisions, it shall immediately notify the Controller thereof in writing and shall suspend the execution of such instruction until the Controller confirms or amends the instruction to ensure its compliance with applicable law.
1.4The Processor shall only process the personal data under the Agreement to the extent necessary for the performance of the Agreement and not for itself, third parties or commercial purposes, unless the Processor has a legal obligation to do so.
1.5The Data Processing Agreement is retroactively applicable to any processing that already took place under the instructions of the Controller prior to the Date of the Data Processing Agreement.
2. Assistance, audit and data subjects' rights
2.1The Parties shall assist and cooperate with each other in fulfilling the Parties' obligations under the GDPR and under Belgian law. Assistance shall be provided within the framework of and in accordance with the provisions of Articles 32-36 of the GDPR regarding security of processing, data breach notification, data protection impact assessment and in case of prior consultation for high-risk processing operations.
2.2The Controller shall always address a written request for assistance and cooperation to the Processor.
2.3The Processor shall provide all useful information to the Controller to allow verification of compliance with the Data Processing Agreement and the GDPR. The Controller has the right to carry out or have carried out an audit of the Processor when reasonably justified to ensure compliance. The Controller shall bear the costs of such an audit. Audits shall be conducted during normal business hours, with at least thirty (30) days prior written notice, and no more than once per calendar year, unless required by a supervisory authority.
2.4The data subjects whose personal data are processed by the Processor (see Annex 1) shall address the Controller in order to exercise their rights under the General Data Protection Regulation. The Controller shall report requests from data subjects in writing to the Processor, who shall take appropriate action on such requests within ten (10) working days or give a motivated notification that the request cannot be complied with. The Processor shall not respond to direct requests from data subjects.
3. Access and confidentiality
3.1The Processor shall grant access to the personal data made available by the Controller for the performance of the Agreement to the Processor’s employees and associates when they are in charge of the processing operations. The Processor shall inform these persons about the Data Processing Agreement and the obligation of confidentiality and shall ensure that they are bound by a similar obligation of confidentiality.
3.2The Processor restricts access to the personal data by third parties and recipients (Art. 4, 9° and 10° GDPR). This access is permitted only when it is necessary for the performance of the Agreement or if there is a legal obligation to do so.
3.3The Processor has the written authorization from the Controller to use a sub-processor. The Processor shall enter into a written agreement with this sub-processor that meets the conditions of Article 28.3 of the GDPR and contains the same obligations as the Processor has under the Data Processing Agreement. The Processor shall not be liable for acts or omissions of a sub-processor beyond the obligations imposed under Article 28 GDPR. The current list of sub-processors is published on the Sub-processors page of the MILLY Trust Center (https://trust.hi-milly.eu).
3.4The Parties shall treat the personal data provided under the Agreement confidentially, both during and after the expiration of the Agreement. Parties shall use this data only for the purposes listed in Annex 1. Parties will not disclose this data unless necessary for the performance of the Agreement or the Data Processing Agreement or unless a Party is legally obliged to do so.
3.5The Processor is permitted to back up the personal data it receives from the Controller in order to ensure a continuous service.
4. Security and personal data breach
4.1The Processor shall take appropriate technical and organizational measures to process the personal data at an adequate level of security and protect them from destruction, loss, falsification, alteration, unauthorized access or notification by mistake to third parties, as well as any other unauthorized processing of these data. The Processor shall implement the technical and organizational measures listed in Annex 2. This does not relieve the Controller of its obligation to take its own appropriate technical and organizational measures.
4.2In the event of a personal data breach, the Processor shall inform the Controller without unreasonable delay. Such notification shall, in any event, be made no later than twenty-four (24) hours after the Processor has become aware of the breach, unless duly motivated exceptional circumstances prevent this. The Processor shall inform the Controller of the measures it takes to limit the extent of the data breach. The Processor shall develop an internal procedure to undertake appropriate measures in case of a personal data breach.
4.3The Processor shall maintain an up-to-date Data Breach Register and shall, upon request, make this Register available to the Controller for inspection. The Processor shall fully assist the Controller in complying with its obligations under Articles 33 and 34 GDPR, including but not limited to the drafting of notifications to the supervisory authority and to the data subjects concerned.
4.4In the event the personal data breach is caused by the Processor’s negligence or willful misconduct and provided that such breach is exclusively attributable to the Processor’s negligence or willful misconduct, the Processor shall bear all direct costs reasonably incurred by the Controller for notifying the supervisory authority and the affected data subjects, as well as for mitigating any resulting damage.
5. Personal data transfers
5.1The Processor does not transfer personal data to third countries or international organizations without the prior notification of the Controller. Any such transfer shall be in compliance with articles 44-50 of the GDPR.
6. Liability
6.1The Processor undertakes to comply with the Data Processing Agreement and shall take measures so that its appointees entrusted with the performance of the Agreement also comply with the provisions of the Data Processing Agreement. The Processor shall only be liable for damage directly resulting from its proven breach of this Data Processing Agreement or of its obligations under applicable data protection law, and solely to the extent such breach is directly attributable to the Processor.
6.2The Processor can only be held liable for any shortcoming directly attributable to it and for events stipulated in the GDPR. The Processor shall in no event be liable for:
- indirect, incidental, punitive or consequential damages;
- loss of profit, loss of revenue, loss of business opportunity, loss of goodwill, loss of anticipated savings or reputational damage;
- loss or corruption of data, except where directly caused by the Processor and not recoverable through backups;
- administrative fines, penalties or sanctions imposed on the Controller by supervisory authorities, except to the extent such fines result exclusively from the Processor’s willful misconduct.
6.3The liability of the Processor shall be limited to foreseeable, direct, personal and certain damages to the Controller, excluding indirect damages, and capped at an amount equal to the total price due by the Controller under the Agreement, with an absolute maximum of EUR 25.000 (twenty-five thousand euros). The above limitations shall not apply in the event of willful misconduct or gross negligence of the Processor, as determined by a final decision of a competent court. In such case, liability shall be assessed in accordance with applicable mandatory law.
6.4The Controller shall indemnify and hold the Processor harmless against any justified third party claim directly resulting from the Controller’s breach of its obligations under this Data Processing Agreement or applicable data protection law, provided that such claim is not caused by the Processor’s own breach of this Data Processing Agreement, the GDPR, or any applicable data protection law.
7. Data retention
7.1The Processor shall retain the personal data and any copies thereof no longer than necessary for the purposes determined by the Controller for Processing, as specified in Annex 1. If the personal data are no longer necessary for the performance of the Agreement, the Processor shall, within thirty (30) calendar days following the Controller’s written request, either return all personal data (including any copies) to the Controller or securely destroy such data if they are stored in any computer system, unless the Processor is legally obliged to retain such data for a longer period under applicable law.
7.2This obligation explicitly extends to any back-ups or archived copies held by the Processor or its sub-processors. The Processor shall impose the same retention and deletion obligations on any sub-processor engaged under this Data Processing Agreement.
7.3Upon completion of the return or destruction process, the Processor shall provide the Controller with appropriate written evidence demonstrating that the personal data, including all back-ups and residual copies, have been securely and irrevocably deleted or returned in full.
7.4The Processor shall maintain appropriate records demonstrating its compliance with this Article 7 and shall make such records available to the Controller upon request.
8. Term and termination of the processing
8.1This Data Processing Agreement enters into force on the Date of this Data Processing Agreement and shall remain in effect for the term of the Agreement. Upon termination of the Agreement, this Data Processing Agreement shall automatically terminate as well.
8.2If the Controller so requests upon termination, regardless of the reason for termination, the Processor shall transfer all personal data, regardless of the carrier and including any copies, to the Controller or, if applicable, securely destroy such data if stored in any computer system, in accordance with the obligations set out in Article 7.
8.3Such transfer or destruction shall be carried out within one month of the Controller’s written request, or within a shorter period if reasonably required by the Controller due to the nature of the data or applicable deadlines.
8.4The Processor shall ensure that no copies or extracts of the personal data are retained, except as required by applicable law, and shall impose the same obligation on its sub-processors.
8.5The Controller shall bear any reasonable costs associated with this return or destruction, unless such costs result from the Processor’s failure to comply with its obligations under this Data Processing Agreement.
8.6Notwithstanding the termination of this Data Processing Agreement, the Processor’s obligations regarding confidentiality, the deletion or return of personal data, and the provision of evidence thereof as set out in Articles 3 and 7 shall survive and remain in full force and effect until fully performed.
8.7This Article shall prevail over any conflicting provision in the Agreement regarding the restitution or deletion of data.
9. Applicable law and jurisdiction
9.1The Data Processing Agreement shall be governed by and construed in accordance with Belgian law.
9.2In case of disputes regarding the Data Processing Agreement and its performance, the Parties shall make serious efforts to reach a reasonable amicable settlement. If, notwithstanding such efforts, no amicable settlement can be reached, any dispute arising from the Data Processing Agreement shall fall within the exclusive jurisdiction of the Courts and Tribunals of the judicial district where the Processor has its registered office.
Annex 1: Details of the processing of personal data
Account and identity data
- Data
- Name, email, phone, avatar
- Processing
- Collection, storage, updating, access control, authentication
- Purpose
- Provision of the platform; user management; access and security
- Data subjects
- Platform users (staff, consultants with portal access)
- Retention
- As long as the account is active and thereafter for a maximum of 2 years
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards (e.g. SCCs)
Consultant and personnel data
- Data
- Name, contact details, employment type, job function, start/end dates, emergency contact, bank/VAT where applicable, salary-related where applicable
- Processing
- Collection, storage, updating, disclosure to authorised users
- Purpose
- Talent and personnel management; contract and assignment management; HR administration
- Data subjects
- Consultants / personnel
- Retention
- 5 years after termination of employment (or as required by applicable law)
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Candidate data
- Data
- Name, contact details, CV, skills, work history, education, availability, notes
- Processing
- Collection, storage, updating, sharing within the organisation, deletion/archiving
- Purpose
- Recruitment; candidate pipeline and hiring
- Data subjects
- Candidates (prospective talent)
- Retention
- 2 years after last contact, unless consent or law requires longer
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Client and client contact data
- Data
- Name, email, phone, job title, department, role in relation to contracts/timesheets
- Processing
- Collection, storage, updating, disclosure to authorised users and (where relevant) to consultants for delivery
- Purpose
- Client and contract management; client portal access; timesheet and approval workflows
- Data subjects
- Client contacts (including client portal users)
- Retention
- As long as the client relationship exists and thereafter as needed for contract/legal obligations (e.g. 7 years where required)
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Time and attendance data
- Data
- Hours, dates, placement, entry type, absence type, descriptions
- Processing
- Collection, storage, aggregation, disclosure to approvers and (where applicable) clients
- Purpose
- Timesheet and leave management; billing and client reporting
- Data subjects
- Consultants / personnel
- Retention
- Aligned with HR/financial retention (e.g. 5 years after employment end; 7 years where required for legal/fiscal purposes)
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Leave and absence data
- Data
- Leave requests, dates, type, attachments
- Processing
- Collection, storage, approval workflow, disclosure to authorised users
- Purpose
- Leave management; HR and capacity planning
- Data subjects
- Consultants / personnel
- Retention
- Aligned with HR retention (e.g. 5 years after termination)
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Health-related absence data (Payroll hub only)
- Data
- Medical certificates and sickness absence periods. These are special categories of personal data within the meaning of Article 9 GDPR.
- Processing
- Collection, storage, disclosure to authorised users with a payroll or HR role and to the Controller’s organisation super administrators, who have access to all data of the Controller’s organisation
- Purpose
- Payroll processing; sickness absence administration; fulfilment of legal and social security obligations
- Data subjects
- Consultants / personnel
- Retention
- Aligned with HR and payroll retention obligations under applicable law
- Scope
- Only processed if the Controller activates the Payroll hub in MILLY
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Contract and document data
- Data
- Contracts, SOWs, signed documents, CVs, receipts, other attachments
- Processing
- Collection, storage, retrieval, disclosure to authorised users and (where relevant) to clients
- Purpose
- Contract and document management; compliance and audit
- Data subjects
- Consultants, personnel, candidates, client contacts (as applicable)
- Retention
- In line with contract and legal obligations (e.g. 7 years for financial/legal documents where required); HR documents as per HR retention
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Financial and invoicing data
- Data
- Data linked to timesheets, invoices, approvals, billing
- Processing
- Collection, storage, calculation, disclosure to authorised users and (where applicable) clients or external systems
- Purpose
- Invoicing; client approval workflows; fulfilment of legal/fiscal obligations
- Data subjects
- Consultants, personnel, client contacts (as applicable)
- Retention
- 7 years (or as required by applicable legal obligation)
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Log and technical data
- Data
- Access logs, audit trail, session/security-related data
- Processing
- Collection, storage, analysis (e.g. security and access control)
- Purpose
- Platform security; fraud prevention; incident response; legitimate interest
- Data subjects
- Platform users and (indirectly) other data subjects whose data is accessed
- Retention
- As long as necessary for security and legal obligations (e.g. typically up to a defined period, unless longer retention is required by law)
- Location
- Primarily inside EEA; if processed outside EEA, subject to appropriate safeguards
Names and contact details relating to the implementation of this agreement
Processor, Wiseworks: Marc De Krock.
Controller: the contact person designated by the Controller in the Agreement.
Nature of processing
Processing operations include:
- collection via manual input or API integrations;
- storage in structured databases;
- consultation and retrieval;
- alignment and synchronization across systems;
- reporting and dashboard visualization;
- restriction or deletion upon Controller instruction.
The Processor does not determine the purposes of the processing and acts solely on documented instructions of the Controller.
International transfers
Personal data is primarily hosted within the European Economic Area (EEA) via EU-based cloud infrastructure.
Where integrations or sub-processors involve processing outside the EEA, such transfers shall be subject to appropriate safeguards under Articles 44–50 GDPR, including Standard Contractual Clauses (SCCs) or an adequacy decision of the European Commission.
Annex 2: Technical and organisational measures
This Annex describes the technical and organizational measures implemented by the Processor to ensure the security of personal data, in accordance with Article 32 of the General Data Protection Regulation (GDPR).
Encryption in transit
All communications between the MILLY web application, client and consultant portals, and the backend are protected using HTTPS with TLS 1.2 or higher. API calls to the backend (database, authentication, storage and server functions) use TLS. Access is controlled via authentication tokens (JWT) so that only authorised users and services can access data.
Encryption at rest
Personal data is stored in a PostgreSQL database and file storage hosted on Amazon Web Services (AWS) in the EU. All database content and file storage are encrypted at rest using infrastructure-level encryption provided by the underlying cloud platform. No personal data is stored locally on user devices; processing takes place in the cloud.
User authentication and password policy
Access to the MILLY platform is via the platform’s authentication service. Supported methods include email/password. Two-factor authentication (2FA) is mandatory for all users. The platform enforces 2FA (e.g. TOTP) and supports an onboarding flow for 2FA setup. Password and account policies are enforced by the authentication service. Session and token handling follow the provider’s security practices.
Role-based access control (RBAC) and data isolation
Access to platform features and data is managed by the Data Controller via a role-based model (e.g. organisation admin, back office, management, sales, consultant, client portal user). Access is limited in line with the principle of least privilege and is assigned according to each user’s role and organisation. PostgreSQL Row Level Security (RLS) is used so that users only access data belonging to their organisation (multi-tenant isolation). Cross-tenant access is prevented at the database layer.
Logging and monitoring
The platform maintains an audit trail of important data and business events. A central audit_logs table (and related logs where applicable) records actions such as contract and placement changes, timesheet submissions and approvals, resets, and other critical operations, including user identifier, entity type, action, and where relevant old/new values. Contract and placement change logs (e.g. rate or term changes) are recorded with timestamp and user reference. The hosting platform provides platform-level logging and monitoring. The Processor can use these capabilities for security and operational purposes in line with the hosting provider’s offerings. Any limitations in logging (e.g. full “view-only” access logs) are mitigated by strict RBAC, mandatory 2FA, and personal login credentials.
Software maintenance and updates
The MILLY application is built on React, TypeScript and PostgreSQL, hosted on Amazon Web Services (AWS) in the EU. The front-end and backend are maintained by the Processor; the hosting platform and other third-party components are cloud-hosted and maintained by their vendors, including regular updates and security patches. The Processor keeps the application and its dependencies on supported and secure versions in line with its deployment and maintenance procedures.
Backups and data recovery
The hosting platform provides automated database backups. Backups are retained according to the hosting provider’s configuration and are encrypted. File storage is subject to the provider’s redundancy and backup features. No manual or local backups of personal data are maintained by default. Restoration relies on the built-in backup and recovery features of the cloud platform. The Processor can configure backup retention within the limits of the hosting plan.
Device and endpoint protection
Users access the platform via web browsers on their own devices (e.g. laptops, desktops). Processing takes place in the cloud; personal data is not stored on user devices. Staff are instructed not to store personal data on local drives. Endpoint protection (e.g. antivirus, device encryption) is the responsibility of the Controller and/or individual users; the Processor can recommend or require minimum standards where applicable.
Pseudonymization and anonymization
Pseudonymization or anonymization is not applied in the core processing, as identification of data subjects is necessary for the purposes of talent and personnel management, timesheet and leave management, contract and document management, invoicing, and compliance with the Controller’s legal obligations.
Clean desk policy
Personnel are instructed to ensure that physical documents and devices are not left unattended in shared or public environments.
Confidentiality and access management
All processor staff are bound by confidentiality agreements, either contractually or via internal policy. Access to systems is restricted based on roles and only granted where necessary.
Document handling
Printed materials (if any) are handled confidentially. Paper records are avoided. Where used, secure destruction (e.g. shredding) is applied. No documents are stored in unlocked or non-secured locations.
Staff awareness and training
Personnel are made aware of GDPR requirements and data protection principles through onboarding and operational procedures. Instructions are given on secure handling of data and platform-specific risks.
Incident response
Incidents, including suspected personal data breaches, are handled according to the Processor’s internal incident response procedure. This procedure covers detection, assessment and containment of the incident; notification of the Controller without undue delay and in any event within twenty-four (24) hours after the Processor has become aware of a personal data breach (Article 4.2); registration in the Data Breach Register (Article 4.3); and follow-up through root cause analysis and corrective measures. The Processor supports the Controller with investigation and reporting.
Data protection policies
A documented Data Protection Policy is in place covering system access, user authentication, data handling, and external communication. This policy is reviewed periodically.
These measures are appropriate to the risks involved in processing and aim to ensure the ongoing confidentiality, integrity, availability, and resilience of processing systems and services.