Skip to main content
Change country / language
Global English
HR, time, payroll and EOR. Live in 26 countries. See the countries

Trust & security

Payroll data deserves
deliberate controls.

Payrovia holds salaries, bank accounts and identity numbers for people in many countries. Multi-factor sign-in, scoped roles, maker-checker approvals, a tamper-evident audit log and field-level encryption protect them. This page sets out how each control works.

Settings · Access Maria Reyes
Payroll manager
Scope Philippines · Manila, Cebu, Davao entities
  • View employee recordsPhilippines · 3 companies
  • Salary & bank detailsVisible · masked in exports
  • Calculate payrollPH Semi-monthly
  • Approve own payroll runSecond approver required
  • Change bank file settingsNeeds a second person
Authenticator app required Session: 60 min

Product interface example · fictional people

AES-256-GCM Field-level encryption for bank and identity numbers
TOTP Multi-factor sign-in, required workspace-wide if you choose
13 roles Scoped to a workspace, company group, market or single company
Maker-checker The person who calculates a payroll can't approve it
Hash-chained Payroll audit entries that cannot be edited
London, UK DigitalOcean managed Kubernetes and PostgreSQL

Identity & sign-in

Every session starts
with proof of identity.

Sign-in protection applies to employees, managers, payroll teams and administrators alike.

Multi-factor authentication

Authenticator-app codes (TOTP), with the shared secret encrypted and recovery codes stored only as hashes.

  • Require 2FA for everyone in a workspace
  • Re-verify before sensitive actions
  • Recovery codes work once

Sessions you control

Set a session timeout for your workspace, from 15 minutes to 8 hours.

  • Refresh tokens rotate, and reuse is detected
  • Logout and password resets end active sessions
  • Cookies are Secure, HttpOnly and SameSite=Strict

Sign-in protection

Passwords are hashed with bcrypt. Sign-in and reset attempts are rate-limited by account and by network.

  • Alerts for unusual sign-ins
  • Optional IP allowlist per workspace
  • Permissions re-checked on every request

Access by role and company

Access that fits the job.
Nothing more.

Thirteen built-in roles, from employee and manager to payroll operator, payroll manager and auditor. Each role is granted for the whole workspace, a group of companies, a market or one company.

Role Own record Team records Salary & bank Run payroll Approve payroll Audit log
Employee Full access No access Own only No access No access No access
Manager Full access Full access No access No access No access No access
HR manager Full access Full access Masked No access No access Read only
Payroll operator Full access Full access Full access Full access No access No access
Payroll manager Full access Full access Full access Full access Approve, not their own run Read only
Auditor Full access Read only Masked No access No access Full access
  • Company and country boundaries

    A payroll operator for the Philippines works only with Philippine companies. Access is checked for each company on every request.

  • Sensitive fields, masked

    Visibility policies and masking rules control who sees salary, bank and identity fields, including in analytics.

  • Employees see their own data

    Self-service shows employees their own payslips, leave and documents, and never another person's.

  • EOR clients see what you allow

    Choose whether each EOR client can see salary detail for their assigned people.

Approvals & audit

A second pair of eyes.
A record of every change.

Payroll is approved by someone other than the person who prepared it, and every change records who made it and why.

Maker-checker payroll approval

The person who calculated a payroll run cannot approve it. Approval waits until the timekeeping period is locked and critical exceptions are cleared. Bank-file settings and payment confirmations need a second person.

Payroll · PH Semi-monthly 1–15 November run
Awaiting approval
  1. Timekeeping period locked1–15 November · 214 employees
  2. Calculated by Ana SantosPayroll operator · 16 Nov, 10:42
  3. Critical exceptions cleared0 open · 3 warnings reviewed
  4. ApprovalAna Santos can't approve her own run
Approver Maria Reyes · Payroll manager Approve run

Tamper-evident audit history

Payroll audit entries record the person, their role, the old and new values, the time and the reason. Entries are hash-chained, and the database blocks edits to them. HR field changes and sign-ins are logged too.

Audit log Payroll & employee changes
Hash-chained
  • Maria Reyes Payroll managerApproved run · PH Semi-monthly 1–15 NovReason: Reviewed variances
  • Ana Santos Payroll operatorCalculated run · Version 2 · 214 employeesReason: Late overtime added
  • Jun Dela Cruz HR managerChanged basic salary · ₱40,000 → ₱44,000Reason: Promotion, effective 1 Nov
  • Liza Tan ManagerApproved overtime · 8.0 h · OperationsReason: Peak-week cover

Product interface examples · fictional people and amounts

Data protection & hosting

Encrypted where it matters.
Hosted where you can see it.

Field-level encryption

Bank account numbers and government identifiers, such as tax and social-security numbers, are encrypted with AES-256-GCM, with a fresh initialisation vector for every write.

  • Authenticator secrets encrypted the same way
  • All traffic over HTTPS; HTTP redirects to HTTPS

Hosting in London

Payrovia runs on DigitalOcean managed Kubernetes in the London region, with managed PostgreSQL.

  • Deny-by-default network policies between services
  • Strict input validation and outbound-request guards

Documents & integrations

Employee documents sit in object storage and open through short-lived signed links.

  • API keys stored as hashes, with scopes and expiry
  • Webhooks signed with HMAC-SHA256

Operational safeguards

Controls for the rare moments
that matter most.

Privileged exports

Bulk exports of sensitive data can require approval before they run.

Support access

Vendor access is reviewed, and emergency "break-glass" access opens only for a set review window.

Privacy requests

Data-subject requests and security incidents are tracked as cases with an owner and a history.

Retention

Retention rules delete, anonymise or archive records when they are no longer needed.

Your security review

Questions security teams ask.

Where is our data hosted?

In DigitalOcean's London region in the United Kingdom, on managed Kubernetes with managed PostgreSQL. The privacy notice explains international transfers.

Can we require multi-factor authentication for everyone?

Yes. A workspace setting makes authenticator-app 2FA mandatory for every user, and sensitive actions ask users to verify again.

Can we limit access to one country or company?

Yes. Every role is granted at workspace, company-group, market or single-company level, and access is checked for each company on every request.

How are payroll approvals controlled?

The person who calculated a run cannot approve it. Approval waits for locked timekeeping and cleared critical exceptions, and every step appears in the audit log.

Who can see salary and bank details?

Only the roles you grant. Visibility and masking rules apply per field, and employees see only their own information.

Can auditors review payroll without changing it?

Yes. The auditor role reads records and the audit log without permission to edit or approve.

Will you complete our security questionnaire?

Yes. Send it with your demo request and we will go through it with your security team, alongside a live look at these controls.

Show us the work
you want to improve.

Bring your countries, worker types and pay cycles. We will tailor the demo to the way your teams work.

Book a demo ↗ Business details only. Please do not share employee, salary, bank or tax data.