Who this notice covers
This notice covers visitors to the HumaRun website, people who create or use an account, and individuals whose workplace information is managed by an organization using HumaRun.
An organization normally decides why its workforce information is entered, who may access it, and what authority it has to manage that information. HumaRun processes the information to provide and protect the service. Website visitors and direct account holders may also share information with HumaRun directly.
Information we may process
Account and identity information
Names, work email addresses, login and verification state, assigned roles, organization membership, and information needed to authenticate and secure an account.
Organization and employment information
Company details, employee profiles and employment history, reporting relationships, documents, workplace records, and joining or leaving information entered by authorized people.
Work and attendance information
Time entries, attendance events, leave requests and balances, approvals, comments, and worklogs where that capability is available.
Payroll and compensation information
Compensation records, payroll preparation data, deductions or adjustments entered by authorized users, and generated payroll records. HumaRun does not currently hold or transfer customer payroll money.
Communications and support information
Demo requests, contact messages, support questions, invitations and verification communications where delivery is configured, and records needed to respond.
Billing information
Plan choices, subscription status, transaction references, invoices and payment status. Card and other payment details are entered in the checkout of Polar, the merchant of record, and are not stored in HumaRun application records.
Technical and usage information
IP addresses, browser or device information, timestamps, security and error records, requests, and cookies or session data needed for sign-in and service operation.
Information specific features use
Some features keep their own kinds of information, described below.
Company Chat messages, files and channels
Messages and replies, reactions, mentions, pinned and saved messages, the members of each conversation and channel, when people joined or left, and how far each person has read. When a message is edited, its earlier wording is kept. When a message is deleted, it is hidden from the conversation, but its text is kept unless a retention period or an erasure request later removes it. Files shared in chat are kept in protected storage.
Only the current members of a conversation can read it. A chat administrator does not read one-to-one or group conversations, except a message that a member reports to them. A role that manages Company Chat can manage the members of any channel, including adding itself, and each addition is recorded. A role that manages both Company Chat and the organization can export the messages one named person could read, after a fresh identity check; the export itself is not stored, only a record that it was made.
By default, all chat history is kept and nothing is removed automatically. Your organization may choose a retention period for one-to-one, group and channel conversations; the text of older messages is then replaced by a removal notice, and files attached to them are no longer available. A legal hold on a channel or on a person stops that removal while it lasts. HumaRun does not decide how long chat must or may be kept.
Calls, meetings, recordings and transcripts
For voice and video calls and meetings: who was invited, who joined and left and when, how long a call lasted, and each meeting's title, description, time, attendees and their replies. The sound and picture of a call are not stored unless the call is recorded. Messages that set up a call pass through HumaRun's server without being stored. Calls of up to four people run directly between browsers. Group calls of more than four people need HumaRun's media server, which is not set up yet, and calls between networks that cannot connect directly pass through a relay server.
Recording is off unless your organization allows it. Your organization also chooses who must agree before a recording starts. Either everyone in the call must agree first: nobody is recorded until all have agreed, someone who joins later is asked and the recording pauses until they answer, and a refusal stops it. Or the recording starts with a notice: everyone in the call is shown that it is being recorded, including people who join later, and HumaRun records each acknowledgement of that notice. HumaRun does not decide whether a recording is lawful where your organization works: your organization's own policy decides that. Recordings are kept in protected storage. Only people who were in the call and can still read its conversation can play a recording, and each playback is recorded. Your organization chooses how long recordings are kept, from 1 to 3,650 days, or keeps them until they are removed; a preservation hold on the conversation or on the file keeps them.
No speech-to-text provider is connected today, so no transcript or live captions are made. Once one is connected, a transcript or live captions are made only when your organization allows transcripts and every person in the call has agreed. The call's sound is then sent to that provider. Anyone who declines stops live captions at once.
Where this stands today:
- Calls of more than four people: Needs server setup: HumaRun's media server
- Call transcripts: Needs a connected speech-to-text provider
Electronic signatures
When people sign a document inside HumaRun: a SHA-256 fingerprint of the exact document sent; each signer's agreement to sign electronically and the version of the wording they accepted; their typed or drawn signature; when they viewed, agreed, signed or declined; a shortened network address, never the full IP address; and a general device description, such as the browser and operating system. This evidence cannot be changed once it is written. A completion certificate lists the signers with this evidence and the full event trail, and the signed copy is kept as a new version of the document.
It is a simple electronic signature inside HumaRun, not a qualified electronic signature.
Profile photos
A photo a person adds to their own profile, or that HR adds for someone within its access, in PNG or JPEG form and kept in protected storage. It can be seen by the person, by people whose role lets them read that profile, and by colleagues who can see the person in the directory. A person can hide their photo from the directory. When a photo is removed or replaced, its file is retired unless a hold keeps it.
Location and worksite checks when clocking in
Where your organization sets up location proof for a worksite, with a notice for employees, the browser reads the device's location once, when a person clocks in or out, and only after they agree to that notice. HumaRun keeps whether the check passed, the rounded distance from the worksite and how accurate the reading was, and a fingerprint of the notice that was shown. It never keeps the location itself and tracks nothing between punches. A worksite PIN or QR code is kept only in a one-way hashed form.
A shared kiosk records the device, the person, the time entry, the action and how the person identified themselves. Kiosk PINs and badges are kept only in a one-way hashed form, and no photo is taken at a kiosk.
Browser notifications
When a person turns on notifications in a browser: the address the browser's push service gave it, the keys used to encrypt messages to it, an optional device label, and when it was added, last used or turned off. Each notification is encrypted before it goes to the browser maker's push service, and it carries the notification's title and a link inside HumaRun, not its full text. Turning notifications off stops them, and so do signing out in that browser, another person turning notifications on in the same browser, and the push service reporting that the address no longer exists; the record that the subscription existed is kept.
Candidates on careers pages
When someone applies through an organization's careers page: their name, email address and optional phone number, their answers to the job's questions, a CV where the organization asks for one (checked for malware before it is accepted), the version of the organization's own privacy notice they agreed to and when, and a one-way fingerprint of their network address. The organization writes that notice and sets how many days applications are kept. After that, the contact details and answers on the application are cleared, and the candidate record made from it is marked as past its retention date for a person to review.
An interview self-scheduling link shows the organization, the job, the interview round, its length and place, and the open times. It stays open for the number of days the recruiter chooses, from 1 to 30 and never past the last time offered, and it closes after repeated failed attempts. Talent pool news carries an unsubscribe link: nothing changes until the person confirms on the page, and their choice is kept. A referral records the name and contact details the employee entered, their relationship, and the employee's confirmation that the person agreed.
The organization may set its own retention period for candidates, after which their records are listed for review or anonymized. There is no default period, and a candidate with an open application, a live offer or a legal hold is never anonymized. The organization can also export what it holds about a candidate.
Public certificate checks
Each learning certificate carries a verification code. Anyone holding the code can check the organization, the person's name, the course and its version, the certificate number, the issue and expiry dates and its current status, such as valid, expired or revoked, and nothing else. The number of checks is limited to prevent guessing.
Single sign-on and provisioning
When an organization connects its identity provider: the identifier the provider gives each person, together with the provider's own identity, the email address at the time the account was linked, and when the person last signed in this way. Through SCIM provisioning, the organization's directory can send a user name, an external identifier, given and family names, email addresses, whether the person is active, and group memberships, which give roles only where an administrator mapped them; deactivating someone suspends their membership and deletes nothing. Accounts are never created automatically at sign-in, and an organization's domains are verified through a DNS record.
Privacy requests and tools
Each member can download a package of their own record after a fresh identity check. It is encrypted, only they can download it, and it expires after seven days. A correction is made as a profile change request that HR approves. Your organization records the purposes it asks consent for, and each person's decision to give or withdraw consent is kept.
An erasure is prepared by one privacy reviewer and applied by a different one, and nobody can do either for their own record. It covers only the kinds of information for which your organization recorded its own retention rule, only after employment has ended and that period has passed, and never while a legal hold covers the person. Employment history, payroll results and payslips, attendance and leave records and the audit trail are kept, and the erasure lists them as kept with the reason. While a legal hold covers the person, an erasure request is refused and the reason is recorded.
For an organization in Germany, France, the Netherlands, Ireland, Spain, Italy, Poland, Austria or the United Kingdom, each privacy request shows its time limit from the GDPR or UK GDPR text, counted on the organization's own calendar: one month, which a reviewer other than you can extend once by two further months, with reasons you can see. Where HumaRun has not read the law of a country, no time limit is shown. Retention periods are the ones your organization records; where HumaRun has read a law's record-keeping period, such as for payroll records, it is shown beside them for information.
Why we use information
Information is used to create and secure accounts, provide organization workspaces, carry out authorized workplace actions, maintain approvals and records, and respond to support requests.
It may also be used to operate subscription and billing functions, send requested account or service communications, prevent abuse, investigate errors, maintain reliability, meet applicable obligations, and improve the service using appropriately limited information.
Who can see workplace information
Access depends on organization membership, assigned role, and reporting or approval responsibility. Employees, managers, attendance supervisors, HR teams, owners and platform administrators may have different permitted views.
Organizations should assign suitable roles and review access as responsibilities change. If access looks incorrect or excessive, tell your organization administrator or use the Contact page.
How we protect information
HumaRun uses administrative, technical and organizational safeguards intended to protect information against unauthorized access, misuse, alteration or loss. These include authenticated access, role-based permissions, password protection, and records of important security and workplace actions.
Protected files, such as documents, chat files, call recordings, profile photos and CVs, are encrypted at rest with AES-256-GCM once the server's storage key is set, and each one is checked by a malware scanner before it is served once a scanner is set up.
How long information is kept
Information is kept for as long as reasonably needed to provide the service, maintain required records, resolve disputes, protect the service and meet applicable obligations. Organizations may control parts of their active workplace data.
Some records may remain for legitimate security, billing, backup or legal reasons. We do not promise one deletion period for every type of information.
Where a feature has its own retention setting, such as chat messages, call recordings, candidate records and the retention rules used for erasure, your organization chooses the period. HumaRun sets no default period for them and does not decide what the law requires. The holds described above stop removal while they last.
Your choices and requests
You may ask to access or correct account information, update self-service fields where permitted, request account support, or ask about deletion, restriction or an activity you question where applicable.
For employment records, start with your organization administrator because the organization normally decides how those records are managed. Rights vary by location and circumstances, and we may need to verify a request before acting. If optional marketing messages are introduced, they will include an unsubscribe route.
Where your organization uses the privacy tools described above, you can also download a package of your own record and ask for a correction inside the workspace.
Using HumaRun across locations
HumaRun is designed for organizations operating across different locations. Depending on hosting and service-provider arrangements, information may be processed in a country different from your own.
Organizations remain responsible for evaluating their local employment, payroll and data requirements. HumaRun does not promise universal legal coverage or a particular data-residency location here.
Hosting region: HumaRun runs on a server of Contabo GmbH (Germany) in its European Union region, where HumaRun data is stored. Encrypted backups are also kept by the operator of HumaRun.
Who provides HumaRun
Questions about website, account and billing information go to the legal entity that provides HumaRun. For workplace records, the organization using HumaRun normally decides how they are used, as described above. The provider’s details are published here.
- Legal entity name: To be published
- Country of registration: To be published
- Company registration number: To be published
- Registered address: To be published
- Governing law: To be published
- Legal and privacy contact: To be published
- Legal and privacy contact email: To be published
- Person in charge of the protection of personal information: To be published
Cookies and storage on your device
HumaRun uses no advertising, analytics or tracking cookies and no cookies of other companies. It stores on your device only what a service you use needs, or a choice you make yourself, so the website shows no cookie banner.
Every item HumaRun stores on a device is listed under these headings, from the same record the code is checked against.
Needed for a service you asked for
Sign-in cookies keep you signed in for up to 8 hours and carry the second sign-in step and single sign-on. A security check of 5 minutes protects the contact, demo and careers forms. A booking receipt cookie lets you see your demo booking for 7 days. A shared attendance kiosk keeps a device cookie for one year, and the application remembers the security role you chose for 30 days.
humarun_session: Keeps a person signed in after they sign in. How long: 8 hours (the server session ends at the same time). Where: Application.humarun_mfa_pending: Carries a sign-in between the password and the second step. How long: Until the second sign-in step ends (minutes). Where: Application.humarun_sso_binding: Ties a single sign-on answer to the browser that started it. How long: Until the single sign-on round trip ends. Where: Application.humarun_social_txn: Ties a Google or Microsoft sign-in answer to the browser that started it. How long: 10 minutes (sent only to the Google or Microsoft sign-in return address). Where: Website and application.humarun_social_pending: Carries the name and email address Google or Microsoft confirmed into the sign-up the person continues. How long: 30 minutes, or until the sign-up finishes or is cancelled. Where: Website.humarun-view-role-<account>-<organization>: Remembers the security role a person chose to work in (a record of their own selection). How long: 30 days. Where: Application.humarun_security_challenge_<form>: A one-attempt security check on the public forms (contact, demo booking, sign-up, password reset, careers applications, CRM web forms and booking pages), against automated abuse. How long: 5 minutes. Where: Website.humarun_booking_receipt: Lets the person who booked a demo see their own booking receipt. How long: 7 days. Where: Website.humarun_kiosk_device: Identifies a shared attendance kiosk an administrator paired with a one-time code. It never identifies a person. How long: 1 year. Where: Application.humarun:chat-policy-reload: Stops the chat page from reloading itself more than once a minute while it switches on the microphone and camera policy for calls. How long: Until the browser tab is closed. Where: Application.Browser push subscription: Created only when the person turns on browser notifications. How long: Until the person turns notifications off. Where: Application.
Choices you make
When you choose a light or dark appearance, a website language or a navigation layout, or hide a notice, that choice is kept in your browser until you change it or clear this site's data in your browser. Nothing is stored before you choose.
humarun_trusted_device: Lets this browser skip the authenticator code when the same person signs in again, after they chose to trust the device on the code step. How long: 30 days, or until the person forgets the device or changes their password or authenticator. Where: Application.humarun-environment-notice: Remembers that the person hid the test-environment notice. How long: Until the browser closes. Where: Application.humarun-theme: Remembers the light, dark or system appearance the person chose. How long: Until the person changes or clears it. Where: Website and application.humarun-site-locale: Remembers the website language the person chose. How long: Until the person changes or clears it. Where: Website.humarun_site_country: Remembers the country the person picked for the salary and tax calculator. How long: 1 year, or until the person picks another country or clears it. Where: Website.humarun.public-chat.v1: Keeps the website assistant conversation the person started in this browser (the last 30 messages, without card numbers, ID numbers, passwords or security-check answers), so it is still there when they come back. How long: 30 days, or until the person chooses Clear chat. Where: Website.humarun-nav-collapsed: Remembers whether the person collapsed the navigation. How long: Until the person changes or clears it. Where: Application.humarun-nav-sections:v1:<account>:<organization>:<role>: Remembers which navigation sections the person opened or closed. How long: Until the person changes or clears it. Where: Application.humarun:closed-notices:v1: Remembers which information notices the person closed, so a closed notice stays closed. How long: Until the person clears it (the latest 300 closed notices are kept). Where: Application.humarun-install-prompt-hidden: Remembers that the person dismissed the install suggestion. How long: Until the person clears it. Where: Application.humarun.notifications.dismissed: Remembers which notifications the person dismissed in this browser. How long: Until the person clears it (the last 200 dismissed notification ids). Where: Application.timesheet-hidden-columns: Remembers which timesheet columns the person hid. How long: Until the person shows every column again or clears it. Where: Application.humarun.chat.listFilters.v1: Remembers which filters the person chose for their chat list. How long: Until the person changes or clears it. Where: Application.humarun:chat-sounds:v1: Remembers which chat sounds the person turned on or off on this device, and their volume. How long: Until the person changes or clears it. Where: Application.humarun.grid.<grid>: Remembers the columns, sort and view the person chose in a list. How long: Until the person changes or clears it. Where: Application.humarun:view-memory:v1: Remembers, in this browser tab only, the toggle, search text, page and open sections the person left on each page, so they find them again. How long: Until the browser closes. Where: Application.humarun:form-memory:v1: Keeps, in this browser tab only, what the person typed into a form in a dialog or side panel, so leaving the page and coming back finds it again; removed when the form is saved or cancelled. How long: Until the browser closes. Where: Application.
The installed application
Only signed-in application pages register HumaRun's service worker. It keeps the offline page, the app icons and public build files on your device, never a page, an answer or personal data. The public website does not register it. Browser notifications are set up only when you turn them on.
humarun-install-prompt-days: Counts the days the app was used on this device, so the install suggestion is never shown on a first visit. How long: Until the person clears it (the last three dates the app was opened). Where: Application.Service worker /sw.js: Makes the application installable and shows an honest offline page. Registered only on signed-in application pages. How long: Until the browser removes it. Where: Application.humarun-shell-<version>: The offline page, the manifest and the app icons. No personal data. How long: Until the next worker version replaces it. Where: Application.humarun-static-<version>: Public, content-hashed build files. No page, answer or personal data. How long: Until the next worker version replaces it. Where: Application.
Children’s privacy
HumaRun is a workplace service. It is not intended for children to create independent personal consumer accounts. If an organization manages information about a young worker, that organization must assess the requirements that apply to it.
Changes to this notice
This notice may change as HumaRun changes. We will revise the last-updated date, and material changes may be communicated through the service or another reasonable channel.
Questions about privacy or data?
Use the Contact page for privacy questions, account help, or a request about information. If your question concerns workplace records, your organization administrator may be the right first contact. You can also read our Terms of Use.