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 you can show your auditor
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.
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.
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.

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.

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.
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.
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
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.
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
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.
SkailerHow much manual work the model takes off HR
COMPLIANCE CHECKS
OFFBOARDING
DOCUMENT APPROVAL
The questions reviewers ask, answered
| Question | Answer |
|---|---|
| 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 we work through your security review
See how teams use Skailer
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.
In 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. The subprocessors that help run the service are listed in Annex III of our Data Processing Agreement.
Yes, through Google sign-in limited to your Workspace domains, Microsoft Entra ID sign-in limited to your tenants, or your own OpenID Connect provider. Admins choose which methods are on. SAML and SCIM aren't supported today.
Yes. An admin turns on two-factor authentication for the whole organization, and everyone who hasn't set it up is asked to on their next sign-in. Admins can reset 2FA for someone who is locked out.
Admins have the access their role gives. Sensitive actions such as Log in as are separate permissions, Log in as is time-limited with restricted actions, and every session is recorded in the audit log. Audit reports show who holds each permission.
Recruiting runs consent management under GDPR: candidates get a consent request with your privacy policy, each profile shows its consent status, and you set how long candidate data is kept. Candidates can ask to edit or delete their data.
Integrations use service users with their own roles and expiring tokens, and webhooks are signed. AI clients connect through MCP as one person, read-only unless they allow changes. The built-in assistant is off until an admin enables it.
Yes. Skailer on-premise is the same HR platform installed on your infrastructure: your IT team runs it with our instructions and installs a new release every month. Pricing is on request. See Skailer on-premise.
A SOC 2 Type II audit covering security, availability and confidentiality is in progress. The application passed an independent Google CASA Tier 2 assessment by TAC Security, valid until November 2026. Skailer isn't ISO 27001 certified. We share the assessment results and our security documentation under NDA.
We notify the customer without undue delay and in any case within 72 hours of becoming aware of a personal data breach, with what happened, the data affected, its likely consequences and what we are doing about it, followed by updates and a root-cause report. Security reports can be sent to [email protected].