Understand how your data is handled.
A practical overview of HumaRun’s controls, what it stores and the limits to understand before using it.
Practical controls, plainly described.
What HumaRun does to protect accounts and records.
Account passwords
Passwords are stored as salted scrypt hashes, never as readable text. Changing your password signs out every session, this one included.
Sessions and devices
Sign-in uses an HTTP-only cookie, and a session ends after eight hours or when you sign out. A session left unused for 30 minutes also ends, and you can sign out any of your other devices.
Multi-factor sign-in
Sign-in can ask for a code from an authenticator app, with recovery codes and a policy your organization sets. When it is on, invitations, bank detail changes, payroll payment approvals and exports of employee, report, payroll or audit data ask for a fresh code first.
Single sign-on and SCIM
Members on your verified domains sign in with SAML 2.0 or OpenID Connect, including Google Workspace and Microsoft Entra ID, once your administrator has tested the connection; no account is created at sign-in. SCIM provisioning and an SSO-required rule that keeps a break-glass owner come with it.
Secure email links
Password reset and email verification use a secure link sent to your address. The reset reply never says whether an account exists.
Stored records
Requests, contact messages, accounts and sessions are stored in the application’s private database, not for public download. Ordinary accounts see only their own linked requests.
Access that follows the role and the record.
How a workspace limits who sees and decides what.
Roles and scopes
Employees, managers, HR, payroll and finance work within their assigned records and actions. Approvers can delegate the approvals assigned to them, for set dates, to a colleague with the same authority.
Sensitive data on its own permission
Salary and payroll amounts, bank details, restricted HR notes and sensitive documents each need a permission of their own. National ID numbers and IBANs are also sealed with a data key before they are stored.
Organizations kept apart
Each organization’s records are separate from every other organization’s, and a person sees only their own organization’s workspace.
History of changes
Changes to records, approvals and payroll are kept with who made them and when, so a decision can be traced afterwards. The database itself refuses any edit or deletion of that history.
Approvals with a check
Approvers decide within their own scope. The person who prepares a payroll run or a payroll payment batch cannot approve it; where nobody else can approve, the sole approver’s decision is recorded in the audit history.
Privacy tools
A person’s data package can be prepared, corrections and consent recorded, and erasure applied only by a second reviewer under your organization’s own retention rules. HumaRun sets no statutory retention period.
Protected files
Uploaded files are encrypted in each organization’s own folder, and a file is served only after a clean malware scan.
HumaRun assistance within your access
HumaRun assistance works from rules, approved knowledge and the role you are working in; no external AI model is used. Every action waits for your confirmation, and it makes no hiring, pay or performance decision.
Know the limits, set it up with care.
HumaRun is not a certified HR records platform, and no independent audit or certification is claimed.
- Turn on multi-factor sign-in for administrators and payroll roles
- Give each person only the role they need
- Never send passwords through contact forms
Ask with the minimum detail needed.
Messages are reviewed by hand; nothing resets automatically.