SECURITY, IN PLAIN LANGUAGE

Your people’s details
deserve careful handling.

Practical controls for your account and workspace.
Clear information about what those controls mean.

01 / BUILT INTO PAYHR

Sign in with a passkey

Add a passkey to use your device or password manager for sign-in. Email codes remain available; protect access to your inbox.

02 / BUILT INTO PAYHR

Choose who can do what

Organisation workspaces use owner, admin, member and viewer roles. Review access regularly and give each person their own account.

03 / BUILT INTO PAYHR

Keep an eye on access

Review active sessions, revoke access from unfamiliar devices, and use account activity records to understand recent changes.

04 / BUILT INTO PAYHR

Keep card details separate

Stripe’s secure payment component collects payment-card details. PayHr stores billing references, rather than full card numbers.

A CLEAR PICTURE

Controls are a starting point.
Trust takes ongoing work.

PayHr does not claim SOC 2 certification, HIPAA compliance, or Canadian-only data residency. Independent reviews, operational policies and production infrastructure must be verified separately from application features.

Do not upload health records. Keep sensitive payroll information in the intended workspace fields and avoid sending it through ordinary email.

Read the privacy notice

REPORT A CONCERN

Something doesn’t look right?

Email our team with a description and the affected feature.
Do not include passwords, codes, employee data or bank details.

Contact PayHr