Privacy at a glance
For works councils, and anyone who wants to know which personal data HalloCrew keeps, where, and for how long. It describes the app as it is today, and grows with it.
Where the data is
- The data in the app stays in Frankfurt (Germany), in the EU: the database and signing in (Supabase), the app itself (Amazon Web Services), and the emails the app sends (Amazon SES, with Amazon SNS for bounces and complaints). Data can leave the EU only in the cases the privacy policy names: Supabase's and Amazon's staff elsewhere can reach it for support or a security incident, under the European Commission's standard contractual clauses; and notifications to a phone go through its push service, encrypted and without personal details.
- Each company’s data is kept apart from every other company’s, in the database itself.
- HalloCrew doesn’t share data with third parties, except what payments need (see Plan and billing), uses no analytics or tracking, and loads no fonts or scripts from other servers. A data processing agreement is available.
What’s kept about each person
- Name and username, and the language they chose, if any.
- Email address, if they have one (it’s optional for employees), whether it’s confirmed, and whether it can receive email.
- Mobile number, if they gave one.
- Roles and teams: which teams they’re in or lead, their role, and temporary handovers of a team lead’s rights.
- Hours a week (contract hours), if someone set them.
- Password: stored scrambled by the sign-in service. Nobody can read it, not even HalloCrew.
- A push address for each device where they turned notifications on. Signing out on that device removes it.
- For someone who left the company: their last working day, the reason from a fixed list (with no field to type in), and who recorded it.
An employee number field exists, but the app doesn’t use it for now.
Importing people from a file
Company admins and managers can import people from a CSV file. The file is read on their own computer and is never sent to HalloCrew or stored by it: only the rows they import are saved, with the details listed above. A username from the file is kept with the invite, as a suggestion for when the person joins.
Check-in screens
- For each tablet or computer at an entrance that shows the check-in code: its name, location and teams, who paired it and when, and when it was last heard from.
- The screen keeps a key of its own in its browser. HalloCrew keeps only the public half, which can check the screen’s codes but can’t make them.
- The screen shows no list of names, and never learns who checked in by scanning. A screen with PINs knows the first names of its teams’ people with a PIN (see below).
PINs for the check-in screen
For people who check in without a phone, by typing a PIN on the check-in screen.
- What’s kept about a person: a scrambled form of their PIN (a slow hash), never the PIN itself; who made it and when. Nobody can read the PIN back, not even HalloCrew: whoever makes it sees it once.
- On a check-in screen: the list of the people in its teams with a PIN, each with their first name, whether they’re checked in and since when (to the minute), and a code that only works on that screen, never the PIN; and the PINs typed while it had no connection, for at most 7 days, until they’re sent.
- On the server: each typed PIN’s number, for 7 days, so one that arrives twice counts once; and an old PIN’s scrambled form for 7 days after it was replaced or removed, to check a PIN typed without a connection.
- What your employer sees: that you have a PIN and who made it, that a check-in was "PIN on the screen", and on the day itself with PIN beside your name on Attendance, Today.
- After a PIN, the screen shows the first name and the time for a few seconds.
- No photo and no location, as with scanning.
Checking in and out
- Each check-in and check-out: the time, the location and check-in screen, and how it was recorded: by scanning; with a PIN on the screen; by hand, with who did it and the reason, from a fixed list without free text; or automatically when someone didn’t check out within 12 hours (the company’s setting).
- With each check-in, once the person checks out: the break that applied, whether breaks were paid, and the hours worked, so a later change to the schedule doesn’t change them. And the country of its location, which decides which working-time rules apply.
- Scans sent late: a scan that a phone sent later, because it had no connection, is marked "sent late", with when it arrived and who confirmed it. A late check-in that a team lead removed stays, with who removed it: it no longer counts, and it shows as removed in its history.
- The history of each check-in: every change keeps what it was, what it became, who changed it, when and why (from a fixed list, without free text), and the check-in as it was first recorded. Team leads, managers and company admins see it for the people whose attendance they see, with who made each change, also by number once that person’s personal data is deleted. The person sees what changed in their own attendance and their own download, never who.
- Entered late: when a check-in or check-out was entered more than 7 days after its day, or a change was made then, the record keeps that date, so the record says it was added afterwards.
- Forgot to check out: who confirmed or changed an automatic check-out. Each team lead’s choice of when they see who forgot. For the notifications about it, which team lead was told about which check-in, kept for a day so each goes once; the notification names the team, never the person.
- The camera only reads the code on the check-in screen. No photos or video are saved or sent, and the phone’s location isn’t used.
- Who sees it: the person themselves, their team lead, their manager and the company’s admins. Whoever stands in for their team lead through a handover sees the same while it runs. Colleagues don’t; the check-in screen only shows, for a few seconds, the first name of someone who just typed their PIN. After someone leaves, the company’s admins and the manager of their last team still see their past attendance in reports; team leads don’t.
- Downloads: team leads, managers and company admins can download the attendance of the people they see as a CSV file, one row per check-in. They can also make the working-time record of a month, per person, as a PDF or CSV, for example for an inspector. On Starter and up, company admins and managers can also download the hours export for payroll: a line per worker with the month’s days worked, time present, breaks and hours worked, and their hours a week. Each download, record and export made is in the audit log.
- Your own download: everyone can download their own data from their profile (Download my data): their details and every check-in of theirs, with the late check-ins a team lead removed, in the same columns, the changes to their check-ins, never who, their working-time record of every month, and what the audit log holds about them (see "The audit log" below). In My attendance they can also download a month’s record as a PDF or CSV, which never says who changed something. Each of these downloads is in the audit log too.
- How long: each check-in is kept with its history for the company’s retention setting (25 months unless the company changed it), and never shorter than the country of its location asks, with a margin: 25 months in Germany (the law asks 2 years from the end of the seventh day after the working day) and 13 months in the Netherlands (the law asks at least 52 weeks from the day it’s about). The months count from the end of the check-in’s month. The night after, it’s removed with its history; the audit log notes how many, never whose or which. Lines in the audit log that hold its times (set or changed by hand) keep them no longer either. People who left, and people whose personal data was deleted, are treated the same.
The schedule
- Each planned shift: the day, the team, the start and end, the break, and whether it’s one of the team’s working hours, custom hours or a day off; for custom hours, the note for the employee, if the planner wrote one. Who changed it last, and when.
- Who sees it: the people who plan the team: its team leads, deputies and whoever has a handover running, its manager and the company’s admins. A week is a draft until they publish it.
- The published version: a copy of each shift as it was when the week was last published; it changes only when someone publishes again. Each person sees their own published shifts, never anyone else’s and never the drafts; they’re also in their own download. A notification about a published week says only which week, never names or times. Deleting someone’s personal data keeps it under their number and removes the notes, as with the plan.
- Hours a week next to the plan: the people who plan a team see, for someone with hours a week, how many hours they have planned that week in all their teams: from other teams only the total, never which team or when.
- Working-time flags on the shifts: what the check found (the rule, and the hours or the number it’s about), with whose shift it is. The people who plan a team see them on its shifts; a flag caused by a shift in another team shows the rule, never that team or its shift’s details. They change whenever the plan changes, and go when the shift goes.
- How long: planned shifts are kept, so past weeks still show what was planned. Deleting someone’s personal data keeps their shifts under their number and removes the notes on them.
Days someone can’t work
From the Team plan, employees let their team lead know which days in the coming weeks they can’t work.
- What’s kept: the day, and whether it’s the whole day or from or until a time. Never a reason: there’s no field for one.
- Who sees it: the employee and whoever plans one of their teams: the team leads, deputies and whoever has a handover running, the team’s manager and the company’s admins. Never colleagues, and never on the printed week roster, on Today or in the coverage report.
- The audit log doesn’t record marking or removing a day: it isn’t a request. If someone plans a shift on such a day anyway, the audit log lists that shift with the other flagged shifts, as Can’t work, without the hours.
- How long: until the night after the day; then it’s removed. When someone leaves, the days after their last working day go at once, and when someone’s personal data is deleted, all of them go at once. Everyone’s own days are in Download my data.
Change requests
- Each request: whose shift, the team and the day, what was asked for (can’t work, start later, leave earlier, different hours) with the times, the shift as it was published, when it was sent, and where it stands (waiting, approved, declined, withdrawn, or closed because the shift changed, the person left the team or the shift passed).
- The decision: who decided and when, the times approved, and the message with a decline, if the person deciding wrote one. The employee sees it on their Home until they dismiss it; whoever may decide the team’s requests sees it under Handled for 30 days.
- The reason, if the employee gives one: seen only by the employee and whoever handles the request (the team’s leads, deputies, whoever has a handover running, the team’s manager; a company admin who decides it). Never in a notification, the audit log or a download other than the employee’s own.
- Today’s notices: running late or leaving early, with the time, for today’s shift. Whoever handles the team is told, and Today shows it next to the person’s status for the rest of the day, to whoever plans the team.
- Swaps: the colleague asked to swap sees who asked and both shifts, never the reason. Their answer (accepted or declined) and when are kept with the request; the audit log records it without the reason. The colleague never sees the team lead’s message, and finds the swaps they were asked for in their own Download my data.
- Notifications about requests and notices never contain names, days, times, reasons or messages.
- The audit log records that a request was sent, withdrawn, approved (as asked or with other times) or declined (who, the team, the day, the kind), never the reason or the message.
- How long: requests are kept with the shift, as the schedule is. Deleting someone’s personal data removes their reasons and the messages to them; the requests stay under their number. Each person’s own requests and notices are in their Download my data.
Time off and sick reports
- A request for time off: the type (vacation or other), the first and the last day, the reason if the person gave one, when it was sent, and where it stands (waiting, approved, declined, withdrawn, closed because nobody decided in time, approval undone, or cancelled on leaving). With a decision: who decided and when, and with a decline the message, if there is one.
- A sick report: only that someone is sick, from which day to which day, whether they reported it themselves or someone else did, and when. Never what’s wrong: there’s no field for a reason or any other text.
- On the schedule those days show as off with their type, for whoever plans the team. A shift on those days becomes an open shift; for each day the shift it was is kept, for the hours in the hours export.
- Who sees it: the type and the days are seen by the person and by whoever may check them in by hand: the team leads, the team’s manager and the company admins. Whoever stands in for their team lead through a handover sees the same while it runs. Only the person and whoever handles the request see the reason. Colleagues and the printed roster see only Off. Notifications never name a person, the type or the days.
- In the working-time record a day of vacation or other leave shows as "Vacation" or "Other leave"; a sick day isn’t there, like any day not worked. The hours export for payroll gives the days and the hours for each type, sick included.
- The audit log records that a request was sent, withdrawn, approved or declined, that someone was reported sick or recovered, and what happened to it when they left (the type and the days), never the reason or the message. Once a sick report’s time is up (see How long), its lines no longer say who was sick, that it was a sick report, who reported it or which days, also where the person reported it themselves. The same goes for a request for time off: once its time is up, its lines no longer say whose it was, its type or its days.
- How long: as long as the check-ins of that month: the company’s retention period (25 months unless the company changed it), and never shorter than a location’s country asks (25 months in Germany, 13 in the Netherlands), counted from the end of each day’s month. A sick report is health data, so it isn’t kept longer than the records that use it. The night after, HalloCrew removes those days; when no day of a request or sick report is left, it goes with its reason and message. On the schedule the day then shows as a plain Off, without the type. A sick report going on stays. The audit log notes how many, never whose. If someone’s personal data is deleted sooner, the reason and the message go at once; the days stay until then under their number. Everyone’s own requests and sick reports are in Download my data.
Plan and billing
This is about the company, not its people. Only the company admins see it.
- The billing details: the name on the invoice, the address, the VAT number with what VIES said about it, and the email address invoices go to. For a sole trader these can be personal data.
- The payment method: only its kind, and the last 4 digits of the account or the card’s brand. The account number or the card itself is with Mollie, not in HalloCrew.
- Payments, invoices and credit notes: when, how much, their status, and who changed or cancelled the plan. Invoices and payments are kept for 7 years, as the law requires, also after the company stops.
- Mollie, a Dutch payment service, handles the payments, as a controller of its own for the payment data. HalloCrew gives Mollie only the name on the invoice, the email address for invoices and an internal number for the company.
- VIES, the European Commission’s VAT register, gets only the VAT number, to check that it’s valid.
- HalloCrew itself sees each company’s plans and payments in its own admin pages, to help and to refund; no people, attendance or schedules.
Questions to HalloCrew
A company’s admins can ask HalloCrew a question in the app (Help, then Contact HalloCrew).
- What’s kept: the question’s kind, subject and messages, which of the company’s admins wrote each one, any screenshots added (they can show whatever was on the screen, so the form asks to show only what’s needed, preferably without the company’s people’s details), the page they came from and the app’s version.
- What HalloCrew does with it: the app removes a screenshot’s hidden details before it’s kept (such as where and with which camera a photo was taken), only the picture stays; and HalloCrew can make notes on a question that only HalloCrew sees, never the company. They’re deleted with the question.
- Who sees it: the company’s admins, and HalloCrew itself, which answers. Employees, team leads and managers don’t.
- How long: until 2 years after the question was closed; a question waiting for the company closes by itself 14 days after HalloCrew’s last reply. When the company stops, its questions are deleted.
- The admin who asked finds their own messages and the replies in Download my data; the company’s admins find all its questions in Download everything.
Kept briefly, for security
- Wrong passwords: the username and a random code for the device, counted for 15 minutes, to slow down guessing. Changing your password on your profile counts the tries for your account, for 15 minutes too.
- Internet addresses (IP): when someone asks for a password link or signs up a company, counted for an hour, to limit how many go out.
- Internet addresses (IP) when signing in: each try is counted with its internet address for 15 minutes, and each renewal of a session for 5 minutes, so nobody can try password after password from one address.
- Links in emails (password links, confirmations): removed a week after they’re used or expire.
- Addresses that can’t receive email: when someone asks for a new link to one, the address is counted, so it comes off the email service’s own list of such addresses at most once a month. It’s kept for 30 days.
- Scans: counted per person for a minute, at most 10, so nobody can try codes at random.
- Sessions: a signed-in device has a session; signing out ends it.
A clean-up runs every night and removes what’s past its time, so nothing here stays much longer than it says.
Cookies
Only what the app needs to work: whether you’re signed in, a random code for this device with the company it remembers, the language you chose, which of our websites sent you to the app, a sign-up in progress, whether you folded the setup checklist away, and on a device with notifications on, which push address is this device’s. No cookies for tracking or advertising.
On a phone without a connection, a scan waiting to be sent is kept in the browser’s own storage: the code it read, when, and whose it is, for 12 hours at most, until it’s sent. It’s only sent for that person, and signing out removes it.
Outside services
- Push notifications go through the push service of the person’s browser or phone (Apple, Google, Mozilla or Microsoft), encrypted and without personal details: the details load inside the app.
- Passwords from data breaches are refused. To check a new password, the sign-in service sends the first 5 characters of a scrambled version of it to the "Have I Been Pwned" service and compares the answer itself. The password, the username and the account never leave the sign-in service, and 5 characters of a scramble can’t be traced back to anyone.
- Emails go out from Frankfurt through Amazon SES. Opening an email loads one image, the header, from the app’s own address (app.hallocrew.eu): the same image for everyone, so it tracks nothing, though opening the email does contact HalloCrew’s server.
The audit log
Changes to people, their roles and teams, handovers, retiring and deleting are recorded, and so are checking people in and out by hand and confirming, changing or removing scans sent late: what changed, when and by whom. So is each download of attendance as a CSV file: who downloaded which days and teams, and how many rows, never what was in it. And each working-time record made as a PDF or CSV: who made it, for which month, which teams or which person, in which language and for how many people, never what was in it. And each hours export for payroll: who, which month and teams, and for how many people, never the hours. And each copy of someone’s own month: who, which month, PDF or CSV and the language. And each download of someone’s own data: who, and how many check-ins. And each download of the audit log itself: who, its filters (a person, a period, kinds of line) and how many lines, never what they say. And each change to someone’s hours a week: who, for whom and from which date, never the hours. And saving a shift with a working-time flag: who planned it, for whom, which days and which rules. And publishing a week or its changes: who, which team and week, and how many shifts or changes, never the shifts themselves. And each night’s removal of attendance past its time: how many check-ins and changes, never whose or which days. The log uses internal numbers for people, never names or email addresses, so deleting someone’s personal data leaves nothing about them in it.
Who reads it: company admins read every line of their company on the Audit log page, and managers the lines about the people and teams they manage, never lines about the whole company such as locations, check-in screens and the nightly removal. Team leads and employees have no page. The page looks up the names when it’s read; the log itself keeps only the numbers. Reading and checking the log aren’t recorded; downloading it is.
Hard to change unnoticed, and how far that goes: lines are written only by HalloCrew’s server and are never changed or removed. Each line holds a fingerprint (a SHA-256 hash) of its own content and of the line before it. Company admins can check the log from its page: a line that was changed or removed directly in the database after it was written shows up, with its number and day. What the check can’t show on its own: when the newest lines are removed, the lines before them still match; and someone with full access to the database could work out every fingerprint again after a change. A CSV or fingerprint kept from earlier shows both, because each CSV holds every line’s fingerprints.
Sick reports: the fact alone that someone was sick is health data. So what a sick report’s lines say is kept apart, and the log itself holds only a fingerprint of it (a SHA-256 hash with a random addition, so nobody can guess it). While the sick report is kept, the page shows those lines as usual, and the check also compares what they say with that fingerprint. When the sick report is removed after its time is up, what its lines said goes with it, also where the person reported it themselves: each line stays as "Removed after the retention period", by nobody, about nobody and without days, and the check still covers it. Lines about requests for time off keep their type and days.
Downloaded files: a file someone downloads, such as the audit log’s CSV, the hours export for payroll or a month’s working-time record, is the company’s own copy. It falls under the company’s own retention; HalloCrew can’t remove it.
Everyone’s own lines: the file from Download my data ends with what the audit log holds about that person: the lines about them, their requests, their shifts and their handovers, with when, what and the details, but never who did it and never another person’s name. A line about a team’s download or record names the teams, not who was in them, so it isn’t in anyone’s own copy.
When someone leaves
- Retiring: a company admin or manager records that someone left. From then on they can’t sign in or check in, they’re signed out everywhere, and their push addresses are removed. Their data is kept, because companies need their attendance records. Only those records go, once their time is up, as everyone’s do (see How long under Checking in and out). Requests for time off nobody decided and approved time off after their last working day are cancelled; a sick report ends on their last working day.
- Deleting personal data: a company admin can delete a retired person’s personal data, from the Retired tab, after typing their full name. That removes their name, username, email address, mobile number, language, hours a week and sign-in account. What stays: when and why they left, and their records under a number such as "Former employee 4821", so past reports still add up. It can’t be undone.
- Deleting a team removes its name; its history stays under a number such as "Former team 4821".
- Invoices and payments are kept for 7 years, as the law requires (see Plan and billing).
When the company stops
When the workspace is read-only, because the trial ended without payment details, payments failed or the company cancelled:
- everything is kept for 90 days. Everyone can still sign in, see everything and download their own data; the company admins can download everything of the company at once (Download everything). If the company carries on in that time, nothing is gone.
- the company admins get a reminder after 30, 60 and 83 days, with the day everything is deleted.
- HalloCrew closes the workspace after 90 days. A company admin can ask for that sooner; it then happens in the coming night, and until then a company admin can take it back. The company admins get a last email.
- Closing deletes: everyone with their data and accounts, the attendance with its history, the schedules, requests, time off and sick reports, the teams, locations and check-in screens, and the billing details. The audit log's lines stay as they are: internal numbers, days and kinds of event, never names; once the people, teams and locations are deleted, nobody can tell who or what the numbers stood for.
- What stays: the company’s name, its country, its plans and when they ran, the invoices and payments (7 years, the law), and counts without names (how many people, teams, locations, check-in screens, check-ins and shifts per month, and which features were used), for HalloCrew’s own figures. Nobody is in them any more.
- Backups of the database expire after a fixed period; until then the data is still in them.
- Closing can’t be undone. If the company wants to use HalloCrew again, it signs up again.
Questions
On your profile, What my employer can see shows what’s kept about you and who sees it, and Download my data gives you a copy. Ask your company admin about anything else. Your company decides what’s recorded about you in HalloCrew, and can delete it.