Security & privacy

Data privacy first.
AI no exception.

Payroll is the most sensitive data a company holds. We built HeyHR โ€” and Metis โ€” around protecting it.

  • Primary data stored in Singapore
  • Encrypted at rest and in transit
  • Access set by role and entity
  • Not used to train AI
Request our security pack

Access
control

Governance
& audit

Data
privacy

Deterministic
processing

[

Your payroll data

]

Built in. Not bolted on.

Four protections

Not added on.
Built in from the start.

Governed AI4 patents pending โ†’

Access control

  • Role- and attribute-based access, set by user, role, company and legal entity.
  • Secure sign-in and session management.
  • Production data reachable only through named, authorised engineer accounts, protected by MFA.

Data privacy

  • Each customer's data separated by company and legal entity.
  • Encrypted at rest and in transit.
  • Customer data stored in Singapore.

Governance & audit

  • Nothing changes until the user confirms it, and changes are recorded.
  • Payroll runs, approvals and changes recorded.
  • Payroll lineage: every number traceable to its inputs and rules.

Deterministic processing

  • Pay, contributions and tax are calculated by HeyHR's rules engine โ€” never generated by AI.
  • The same inputs give the same result, every time.
  • Metis explains and checks the numbers; it does not compute them.

AI & your data

Metis acts as you.
Never beyond you.

Every request to Metis is authenticated and stays within the userโ€™s own permissions, before any data reaches a model.

  1. 1Ask, as you

    In the web app, Slack or WhatsApp. Who is asking comes from the signed-in session, never from the prompt.

  2. 2Scoped to you

    The same permissions as the app: role, company and entity. Metis sees only what you may see.

  3. 3Identifiers kept out

    Employee NRIC, passport and bank numbers from your records are never sent to a model, and internal IDs and secrets are filtered out.

  4. 4You confirm, rules execute

    Any change waits for your confirmation. The rules engine carries it out, recorded with lineage.

Never used for training.

We don't use your data to train AI models.

Isolated per company.

Each company's data is kept separate and never shared across customers.

Conversations, protected.

Metis chats are kept under the same access controls as your HR records. Who can see them follows your company's settings.

Security operations

Watched continuously.
Checked on every change.

Continuous scanningEvery code change checked for vulnerabilities, risky dependencies and exposed secrets.
Edge protectionWeb application firewall, DDoS protection and rate limiting in front of every service.
MonitoringHosting, authentication and application logs, with telemetry on every service.
Security reviewsInternal reviews of authentication, access control, tenant isolation and AI governance โ€” tracked to remediation.
Incident responseContain, fix, verify, review โ€” and you hear from us without delay, with support for your PDPA obligations.
Backups & recoveryEncrypted backups kept in Singapore, with production isolated from development.

Your data, your exit

Yours while you're with us.
Yours when you leave.

  1. While you're a customer

    Export employee, payroll, CPF, general ledger and year-to-date data to Excel, and payslips to PDF, at any time.

  2. When you leave

    Export what you need to keep for statutory purposes, as set out in your agreement.

  3. After that

    Deleted or de-identified under our documented retention and backup procedures, unless the law requires otherwise.

Assurance

Certified infrastructure.
Controls built to standard.

HeyHR runs on infrastructure independently audited to SOC 2 Type II and ISO 27001, with our own controls aligned to the same frameworks. Your security team gets everything it needs to evaluate us.

  • Certified infrastructureHosting, sign-in, edge and AI providers independently audited to SOC 2 Type II, plus ISO 27001
  • Encrypted everywhereEncrypted at rest by our hosting providers, backups included. TLS in transit
  • PDPA-readyService providers disclosed, with breach notification support
  • Security review supportQuestionnaires answered and documentation shared during evaluation

Security questions

Where is HeyHR data stored?

Primary customer data โ€” the database, files such as payslips and calculation lineage, and backups โ€” is stored in Singapore. Some supporting services, such as AI and workflow providers, may process limited data in other jurisdictions under contractual safeguards.

Is our data used to train AI models?

No. We don't train AI models on your data, and neither do our AI providers.

What data does Metis send to the AI model?

The user's question and the records needed to answer it, within what that user is allowed to see. Employee NRIC, passport and bank numbers from your records are never sent, internal IDs and secrets are filtered out, and your data is not used to train AI models.

Can Metis see more than the user can?

No. Metis acts on behalf of the signed-in user, with identity taken from the server session rather than the prompt, and applies the same role- and attribute-based rules as the app.

Does AI calculate our payroll?

No. Pay, contributions and tax are calculated by HeyHR's deterministic rules engine. Metis explains and checks results, and any change it prepares needs your explicit confirmation.

How is our data kept separate from other customers?

HeyHR is multi-tenant. Each customer's data is logically separated by company and legal entity, every request is authenticated, and access is set by role and legal entity.

Is HeyHR SOC 2 or ISO 27001 certified?

HeyHR's controls meet SOC 2 standards, and we run on infrastructure independently certified to SOC 2 Type II and ISO 27001. Our own certification is in preparation. We share the security and privacy information your team needs during evaluation.

What happens to our data if we leave?

You can export your data, including records you must keep for statutory purposes, as set out in your agreement. It is then deleted or de-identified under our documented retention and backup procedures, unless the law requires otherwise.

Questions from your security team?

Request our security pack