HR data security software

Control who signs in and sees what

Choose sign-in methods, require 2FA for everyone, open each role down to single fields, and give every integration and AI client a narrow way in.

HR data security settings in Skailer: sign-in methods, required 2FA and password rules

HR data security you can show your auditor

01
Sign-in you setPassword, Google or Microsoft sign-in, and 2FA for everyone.
02
Access down to the fieldEach role views or edits specific fields, for specific people.
03
Answers for your auditorNotifications sent, role changes and who sees whose data, exported from settings.
04
One account per integrationThe API works only through service users with their own roles.
The problem

A security review shouldn't stall the rollout

The questionnaire arrives: sign-in, access, logging, integrations, AI, hosting. Meanwhile salary sheets are shared by link, and people who left can still sign in.

Sign-in and identity

Decide how people sign in and require 2FA for all

Admins choose which sign-in methods are on: password, Google or Microsoft Entra ID. Google sign-in can be limited to your Workspace domains and Microsoft to your tenants. 2FA can be required for everyone.

01
Three sign-in methodspassword, Google and Microsoft Entra ID; the admin picks which
02
Limited to your domainsGoogle for your Workspace domains, Microsoft for your tenants
03
Required 2FAan authenticator app for everyone; admins reset it on lockout
04
Password and email rulespassword length and expiry, and work emails from your domains
Access control

Open each role to the fields and people it needs

Every role sets view or edit rights down to single fields and modules, and decides whose data it reaches: own record, reports, teams, a location or a legal entity. New custom fields stay hidden until granted.

01
Field-level rightsno access, view or edit for each field, including custom ones
02
Scoped by structurereports, teams, departments, locations or legal entities
03
Hidden by defaultnew custom fields and tables stay invisible until a role gets them
04
Reversible lockoutdisable someone's sign-in without changing their records
Role-based access control for HR data protection: field permissions in Skailer
Audit and accountability

Keep a record of who did what and answer an auditor from the product

Log in as is a separate, time-limited permission with restricted actions, and every session goes to the audit log. Position, pay and leave changes keep who and when.

Audit reports in settings answer an auditor without the vendor: every notification Skailer sent with its text, who gained or lost each role and why, what each role allows, and who can see a given employee's data. Each report exports to a file.

01
Log in as with limitsits own permission, time-limited, with restricted actions
02
Audit reportsnotifications sent, role changes, role permissions and who sees whom; the full log also through the API
03
Change historyposition, compensation and leave changes keep who and when
04
Signed documentseach signature keeps a report of who signed and when
Log in as banner and audit log in Skailer, secure HR software for admins
Integrations and AI

Give each integration and AI tool a narrow way in

The API works only through service users, each with its own role and expiring tokens. Webhooks are signed. AI clients via MCP act with one person's permissions, and the assistant changes nothing without confirmation.

01
Service user per integrationits own account and role, never an employee's login
02
Scoped responsesthe service user's role decides which fields come back
03
Signed webhooksyour systems verify the sender, and the secret can be rotated
04
AI within permissionsoff until enabled, asks before changes, read-only unless allowed
Privacy

Collect consent and set how long candidate data stays

Recruiting runs consent management under GDPR: candidates get a consent request with your privacy policy and can ask to edit or delete their data. Anonymous survey results stay hidden until 3 people answer.

01
Consent under GDPRconsent status shown on every candidate profile in the ATS
02
Retention periodyou set how long candidate data is kept, and extend it per person
03
Candidate requestsedit or delete requests straight from the consent email
04
Survey anonymityresults, exports and AI summaries need at least 3 answers
Hosting and data residency

Keep HR data in the EU, from storage to backups

Skailer runs on Amazon Web Services in Frankfurt, Germany (eu-central-1). The database, files and backups stay in that region, and support and administration work from the EU. Email delivery and error monitoring also run in Germany, and AI features use models inside our AWS account in the EU.

  • Hosted in FrankfurtAWS eu-central-1 for the database, files and backups
  • No transfer outside the EUcustomer data is processed and supported within the EU
  • Short list of subprocessorsAWS, Cloudflare, SendGrid and Sentry, listed in the DPA
  • 30 days' noticebefore any subprocessor is added or replaced
Encryption and resilience

Encrypt everything, back it up and test the restore

Data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256 through AWS KMS. The database runs across availability zones, with daily snapshots and point-in-time recovery, and restores are tested. The application is assessed every year by an independent lab, and a SOC 2 Type II audit is under way.

01
EncryptionTLS 1.2+ in transit, AES-256 at rest with AWS KMS keys
02
Backups and recoverydaily snapshots and point-in-time recovery, restore tested
03
Independent assessmentGoogle CASA Tier 2, verified by TAC Security
04
SOC 2 Type IIaudit in progress for security, availability and confidentiality
AI and your data

Run AI inside the EU and never train on your data

AI features use models on Amazon Bedrock in our own AWS account in Frankfurt. Prompts and answers aren't stored by the model provider, and customer data is never used to train or fine-tune any model. AI is off until an admin enables it.

  • Models in the EUAmazon Bedrock in eu-central-1, inside our AWS account
  • No trainingcustomer data never trains or fine-tunes a model
  • Off by defaultan admin decides whether AI features are on
  • Within permissionsAI sees only what the user may see
One HR platform

Security settings that every module follows

Sign-in rules, roles and the audit log apply across Core HR, Recruiting, Performance and integrations, so reviewers check one access model, not one per module.

How does Skailer handle HR data security?

Skailer runs on AWS in Frankfurt, Germany: data, backups and support stay in the EU, encrypted in transit and at rest. Admins choose sign-in methods (password, Google, Microsoft Entra ID or your own OpenID Connect provider) and require 2FA for everyone. Roles set view or edit rights per field and module and limit them to reports, teams, locations or legal entities. Log in as is a separate, time-limited permission, and each session goes to the audit log. Audit reports show notifications sent, role changes, role permissions and who can see each employee's data. Integrations use service users, webhooks are signed, and AI runs in the EU within user permissions. SAML and SCIM aren't supported today.

Skailer
BY THE NUMBERS

How much manual work the model takes off HR

COMPLIANCE CHECKS

67%
less time monitoring mandatory processes, 12 → 4 h a month

OFFBOARDING

57%
less time on employee offboarding, 14 → 6 h a month

DOCUMENT APPROVAL

64%
less time on document approval, 14 → 5 h a month
For reviewers

The questions reviewers ask, answered

QuestionAnswer
Where is our data hosted?AWS Frankfurt, Germany; backups stay in the EU
Is data encrypted?TLS 1.2+ in transit, AES-256 at rest (AWS KMS)
Who processes our data?AWS, Cloudflare, SendGrid, Sentry; listed in the DPA
Certifications?Google CASA Tier 2; SOC 2 Type II audit in progress
How do users sign in?Password, Google, Microsoft Entra ID or your OIDC provider
Can we require 2FA?Yes, for the whole organization
SAML SSO or SCIM?Not today; Google, Entra ID and OIDC sign-in instead
Who can see salaries?Roles with compensation access, in their scope
Can admins act as users?Only with Log in as: time-limited and logged
Is there an audit log?Yes: reports on notifications, role changes, role permissions and who sees whom, plus the API
Can we see what Skailer sent to employees?Yes: each email, Slack and in-app message with its text and status
How do integrations connect?Service users with roles and expiring tokens
Are webhooks secured?Signed, with a secret you can rotate
What can AI see and change?What the user may see; changes need a confirm
What if someone leaves?Duties go to a successor; sign-in is disabled
How fast are breaches reported?Without undue delay, within 72 hours
Is our data used to train AI?No, never
How it works

How we work through your security review

01
Check the controls yourselfReview sign-in, roles, audit reports and integrations in a demo account before you decide.
02
Set up sign-inChoose sign-in methods, limit them to your domains and require 2FA before anyone is invited.
03
Build rolesOpen each role to the fields, modules and people it needs; new custom fields stay hidden.
04
Scope integrationsCreate a service user per integration and let people connect AI clients with their own access.
FAQ

Security at Skailer, answered

EU hosting and encryption, backups with tested restores, sign-in methods and required 2FA, role-based access down to single fields, Log in as limits and the audit log, service users and signed webhooks for integrations, AI within each user's permissions, and consent and retention for candidates.

Your demo

Send us your security questionnaire

We build your company in Skailer. You look around. Like it? Then we talk price.
[email protected]
Just show me the prices first