Data processing agreement
This agreement between the customer (the controller) and Next Level Logic B.V., trading as HalloCrew (the processor, "we"), is part of the agreement under our general terms. It sets out how we process the personal data of the customer's people on the customer's behalf (Article 28 GDPR).
Released 17 November 2026.
1. Terms used
Words such as personal data, processing, controller, processor, sub-processor, data subject and personal data breach mean what they mean in the General Data Protection Regulation (GDPR).
2. What, why and for how long
2.1 We process personal data only to provide HalloCrew to the customer, as annex 1 describes: which data, about whom, for what, where and for how long.
2.2 This agreement runs as long as the customer uses HalloCrew, and after that until we have deleted the customer's personal data (article 9).
3. The customer's instructions
3.1 We process the personal data only on the customer's documented instructions: this agreement, the general terms, and what the customer's company admins and other users set and do in the app. That also goes for sending personal data to a country outside the European Economic Area (article 11).
3.2 If a law of the European Union or of a member state requires us to process the personal data in another way, we tell the customer before we do, unless that law forbids us to.
3.3 If we believe an instruction breaks the GDPR or other data protection law, we tell the customer at once.
3.4 We process the data for no purpose of our own, and we don't sell it or share it with others beyond the sub-processors in annex 2.
4. Confidentiality
Everyone who works for us and can reach the personal data is bound to keep it confidential. We give access only where it's needed for the work, and we never look at a customer's people or records without a reason the customer gave us, such as a support request.
5. Security
We take the technical and organisational measures of annex 3, and keep them up to date with the state of the art. We may improve them, as long as the level of protection doesn't go down.
6. Sub-processors
6.1 The customer gives us general permission to use sub-processors. Annex 2 lists the ones we use.
6.2 We announce a new or replaced sub-processor to the customer's company admins at least 30 days before it starts, in the app and by email. If the customer has a reasonable objection, it can tell us; if we can't meet it, the customer can end the agreement before the change.
6.3 We bind every sub-processor to the same data protection obligations as this agreement, and remain responsible for them towards the customer.
7. Helping the customer
7.1 Data subjects' rights. The app lets the customer answer most requests itself: everyone can see what their employer sees about them and download their own data, company admins can download all of the customer's data, and the customer can correct records and delete a person's data. Where that isn't enough, we help the customer, and we pass on any request we receive directly.
7.2 Other help. We help the customer, as far as can reasonably be asked, with a data protection impact assessment, prior consultation of a supervisory authority, the security of processing and reporting a personal data breach. What the app offers, and reasonable help by email, is included in the price. For work beyond that we may charge our reasonable costs, after telling the customer what they will be.
8. Personal data breaches
8.1 We tell the customer about a personal data breach without undue delay, and at the latest within 48 hours after we've become aware of it, with what we know: what happened, which data and people it concerns, what the likely consequences are, and what we've done and propose to do. What we don't know yet, we add as soon as we do.
8.2 We keep a record of every breach, and help the customer notify the supervisory authority and the people concerned where that's needed.
9. At the end
9.1 When the agreement ends, the customer's workspace becomes read-only for 90 days, during which the customer's company admins can download all of its data. Then we close the workspace, or sooner if a company admin asks: we delete the personal data of the customer's people as annex 1 describes. Backups expire within 7 days after that.
9.2 We keep what the law requires us to keep as our own records, such as invoices, and the counts without names described in annex 1.
10. Showing that we comply
10.1 We give the customer the information it needs to show that we meet this agreement. On request we describe our measures in more detail, and we pass on the audit reports and certificates our sub-processors make available to us.
10.2 If that information isn't enough, or after a personal data breach, or if a supervisory authority asks for it, the customer may have an audit carried out: by an independent auditor bound to confidentiality, announced at least 30 days ahead, during office hours, without disrupting our service and without access to other customers' data. The customer pays for its audit, and may have one at most once a year, unless a breach or a supervisory authority gives reason for another. If the audit shows that we fall short of this agreement in a serious way, we put it right at our own cost and pay the reasonable costs of the audit.
11. Outside the EU
11.1 We store and process the personal data in the EU, in Frankfurt.
11.2 Personal data can reach a country outside the European Economic Area only in these cases:
- push notifications pass through the push service of the person's own browser or phone, encrypted and without personal details;
- staff of a sub-processor outside the European Economic Area can reach the data in the cases its agreement with us allows, such as support we ask for or a security incident: Supabase from Singapore and the United States, Amazon Web Services from the United States. For this, the European Commission's standard contractual clauses apply between us and the sub-processor.
11.3 We make no other transfer outside the European Economic Area unless the GDPR allows it and we've announced it to the customer first, as we announce a new sub-processor (article 6.2).
12. Liability
The limits of liability in the general terms apply to this agreement, as far as the law allows.
13. Changes, and what prevails
13.1 We announce changes to this agreement the same way as changes to the general terms (at least 30 days ahead, in the app and by email). The new version applies from the day it takes effect, and the app asks a company admin to accept it, as article 12 of the general terms describes.
13.2 If this agreement and the general terms conflict, this agreement prevails on the protection of personal data.
13.3 Dutch law applies, and disputes go to the court named in the general terms.
13.4 This agreement is available in Dutch, German and English. If the versions differ, the Dutch version prevails.
Annex 1. The processing
The parties. The controller is the customer: the business that uses HalloCrew for its people. The processor is Next Level Logic B.V., trading as HalloCrew, Bergstraat 120, 5051 HE Goirle, Chamber of Commerce number 42216546.
What we do on the customer's behalf. We run HalloCrew for the customer:
- recording working time (check-ins and check-outs at a check-in screen, by QR code or PIN, or by hand) as the working-time record the customer's country requires, with its history;
- planning shifts, publishing schedules, and handling requests, swaps, open shifts and absences, including sick reports;
- showing each person their own data and their employer's view of it, and the monthly working-time record and exports for payroll;
- sending emails and push notifications about these;
- keeping an audit log of who changed what;
- deleting data when its retention is up, when the customer deletes a person's data, and when the customer's workspace closes;
- looking at data about the customer's people when a company admin shows it to us in a support request, only to answer that request.
Not on the customer's behalf (we're the controller, under our privacy policy): the customer's billing details, invoices and payments, which we keep as our own records; the support requests of the customer's company admins themselves (who asked, what they wrote and our answers); the customer's name, country, plan history and the terms it accepted; and our own staff accounts.
The people concerned. The customer's workers, team leads (and deputies), managers and company admins, as the customer adds them: employees, temporary staff and contractors.
The personal data.
| Category | What |
|---|---|
| Identity and contact | Name, username, email address (optional for workers), mobile number (optional), employee number, language; for someone who left, their last working day and the reason from a fixed list |
| Organisation | Roles, teams, locations (a name or address can point to a person), team leads' handovers, hours a week, invitations and sign-in links |
| Working time | Each check-in and check-out: time, location, check-in screen, how it was recorded; changes with their reason (from a fixed list) and who made them; minutes worked |
| Schedules and requests | Shifts with a note for the person; days someone can't work (no reason); change requests and swaps with an optional reason and a message |
| Absences | Holiday and other leave with an optional reason; sick reports: only the days and who reported them |
| Security | Password hashes (in the sign-in service), PIN hashes, sessions with their internet address and browser, the sign-in service's record of sign-ins, wrong-password and other limit counts, push addresses |
| The audit log | Who did what and when, by internal number, never names or addresses |
| Support requests | Whatever a company admin's message or screenshot shows about the customer's people |
Special categories. Health data: the fact that someone is sick, and on which days; never what they have (there's no field for it). It's kept as long as the working-time record of its months, then deleted, and the audit log's lines about it are sealed so they no longer say who or which days.
Where. In the EU: the database and sign-in in Frankfurt (Supabase), the app and its emails in Frankfurt (Amazon Web Services). The exceptions are in article 11.
How long.
| What | How long |
|---|---|
| People, roles, teams, locations | While the customer uses HalloCrew; a person's data until the customer deletes it |
| The working-time record and its history | The customer's setting (25 months unless changed), never shorter than the country of the location requires (Germany 25 months, the Netherlands 13 months), counted from the end of the month |
| Absences and sick reports | As the working-time record of their months |
| Schedules and requests | With the schedule; reasons and notes go when the person's data is deleted |
| Days someone can't work | Until the night after the day |
| The audit log | Kept; absence lines and by-hand time lines emptied with their retention |
| Security counts, links and tokens | A few minutes to 30 days |
| PINs typed at a check-in screen, and a replaced PIN's hash | 7 days |
| The sign-in service's record of sign-ins | 90 days; a closed workspace's at once |
| The sign-in service's and the database's own logs at Supabase | 7 days |
| An address our email service no longer sends to, because an email bounced or was marked as unwanted | Until it's taken off that list |
| Data about the customer's people in a support request | With the request: 2 years after it's closed, and deleted when the workspace closes |
| The app's error lines (without names or addresses) | 30 days |
| Backups | 7 days |
At the end. When the customer stops paying or cancels, its workspace becomes read-only for 90 days: everyone can still see and download their data, and the company admins can download everything at once. Its company admins are reminded at 30, 60 and 83 days. Then we close it (sooner if a company admin asks, in the coming night): we delete every person's data and account, the working-time records, schedules, requests, absences, teams, locations, check-in screens and support requests. The audit log's lines stay as they are: they hold internal numbers, days and kinds of event, never names, and once the people, teams and locations are deleted we can no longer tell who or what the numbers stood for. We keep the customer's name, country, plan history and dates, its invoices and payments (our own records, 7 years by law), and counts without names for our own figures. Closing can't be undone. The download offered for 90 days is how the customer gets its data back; after it, we delete.
Annex 2. Sub-processors
| Sub-processor | What it does | Where | Agreement |
|---|---|---|---|
| Supabase Pte. Ltd (Singapore); its affiliate Supabase, Inc. (United States) helps with support and operations | The database and the sign-in service, with their own logs | Frankfurt (AWS eu-central-1) | Supabase's data processing addendum, with the European Commission's standard contractual clauses (processor to processor) |
| Amazon Web Services EMEA SARL (Luxembourg) | Hosting the app (Lightsail), sending emails (SES), bounces (SNS) | Frankfurt (eu-central-1) | The AWS GDPR data processing addendum, with the European Commission's standard contractual clauses |
Each of them uses sub-processors of its own, which it lists on its website.
Not sub-processors:
- The push services of the person's browser or phone (Apple, Google, Mozilla, Microsoft): the person's own device chooses them; they carry encrypted messages without personal details, and know the device's push address.
- Mollie, for the customer's payments to us: a controller for payment data in its own right, under its own terms; it gets no data about the customer's people.
- The European Commission's VIES, which checks VAT numbers: only VAT numbers.
- Have I Been Pwned, which the sign-in service asks about a new password: only the first 5 characters of a hash, which identify nobody.
- Amazon Web Services' health checks in the United States (Route 53), which ask the app every 30 seconds whether it's working: they receive only the app's answer, no personal data.
- Proton Mail (Proton AG, Switzerland), which hosts our own mailboxes: email that people send us is our own correspondence, under our privacy policy.
Development tools (GitHub for the code, Google Drive for notes, Claude for development) never receive customer data.
Annex 3. Technical and organisational measures
Keeping customers apart. Every row of a customer's data carries its company's ID, and the database's row-level security lets each signed-in person reach only their own company's rows, and within it only what their role allows. Every rule has automated tests, including with another company's data. Billing records, the audit log and the check-in screens' keys can't be reached from a browser at all.
Signing in and access.
- Username and password; passwords of at least 8 characters with a capital letter, a small letter (in any alphabet) and a number, checked against known data breaches.
- Sign-in attempts limited per username and device, and per internet address; sessions end on signing out, when someone leaves, after 30 days without use and always after 180 days; HalloCrew's own admin's after 12 hours.
- Roles decide what each person sees: workers their own data, team leads their teams, managers their part of the organisation, company admins their company.
- Our own administrator signs in with a code from an authenticator app too, with recovery codes, and sees each company's plan and billing and the support requests its company admins send us, never its people or records.
- The database's keys are held by our owner, in the deployment pipeline's protected settings, never in the code; data is changed only by the app and by reviewed, tested database changes.
Encryption. All traffic over HTTPS. Passwords hashed by the sign-in service; PINs stored as slow hashes, never readable; push messages encrypted end to end and without personal details. Supabase encrypts the database and its backups where they are stored.
Integrity and accountability. The audit log is append-only and chained with SHA-256 hashes, so a change made directly in the database shows when a company admin checks it. The working-time record keeps every change with what it was, what it became, who and why; nothing is overwritten silently.
Minimisation. No GPS or location and no photos at check-in. Reasons from fixed lists where possible. No analytics or tracking, and no scripts or fonts from other servers. Emails and push messages carry no more than they need; push messages no personal details at all. The app's logs and error lines contain no names or addresses.
Retention and deletion. Automatic jobs remove working-time records, their history and absences past their retention, and short-lived security data within days. A company admin can delete a former employee's personal data. A closed workspace's personal data is deleted (annex 1).
The people's rights. Everyone can see what their employer sees about them and download their own data in the app; company admins can download everything; the customer deletes a person's data.
Availability. Daily backups kept 7 days, with a written and rehearsed procedure for restoring one. Health checks from outside the app every 30 seconds, with an alert when the app or one of its scheduled jobs stops. The app's own errors are kept 30 days and reported every morning when a new kind appears. New versions go out on weekday evenings, after an automated test of the daily flows, and can be rolled back.
Development. One codebase, with automated unit, database and sign-in tests on every change, and an end-to-end test of the daily flows before each release; libraries pinned to reviewed versions and checked for known vulnerabilities on every change; development on made-up data only. An external penetration test is planned for after the launch.
Incidents. The monitoring above helps us notice a breach. When there is one, we tell the customer's company admins by email within the time in article 8, with what article 8 lists, and we keep a record of the breach and what we did about it.