Security
Your people data, kept safe.
Salaries, leave records and health information are the most sensitive data your company holds. This is how MambaHR protects it.
Encrypted
AES-256 when stored, and TLS 1.2 or higher when it moves.
Access by role
Each person sees only what their role allows.
Every change logged
Who did what, when and why, in a log no one can edit.
Never used to train AI
Your people data never trains any AI model.
These commitments are in our Data Processing Addendum, provided with the order form.
Access
Your logins, your rules
Accounts left open after someone leaves are a common way in for attackers. Sign-in and account setup run through WorkOS, Okta, or Microsoft Entra, and access follows your org chart. When someone leaves, they are locked out the same minute.
- Your team signs in with the accounts they already use
- Permissions follow each person’s role automatically
- When someone leaves, their access ends. No forgotten accounts.
You stay in charge
A person on the big calls
MambaHR works within the policy you set. Offers above your pay range, terminations, and big pay changes always wait for a person to sign off, with the reasons attached.
- You decide which actions need a person
- Nothing high-stakes happens without a named approver
- Every approval and every decline is logged
For your security review
Answers for your security review.
The questions IT and legal teams ask, answered. Forward this page to them.
Who hosts our data?
Your records are hosted on AWS. The AI models that do the work run with data retention and training switched off. Every company that processes your data is listed in our Data Processing Addendum, provided with the order form.
How is it encrypted?
AES-256 when stored and TLS 1.2 or higher in transit, for the database, documents, and every backup.
Who at MambaHR can see it?
Only people whose job requires it, with the least access they need. Production access is restricted, logged, and reviewed.
What about backups and recovery?
Encrypted automatic backups on AWS, and the database can be restored to an earlier point in time.
What if we leave?
Your data is yours. Export all of it in standard formats whenever you ask. After you cancel, you have 30 days to export, and then it is deleted within 60 days.
Who are your subprocessors?
AWS for hosting, OpenRouter for AI with zero data retention (OpenRouter sends each request to a model host under its own account: Amazon Bedrock or Google Vertex AI for Anthropic models, Microsoft Azure for OpenAI models), Temporal Cloud to keep multi-step tasks running, WorkOS for sign-in, Cloudflare for DNS and bot protection on public forms, Stripe for billing, and Deel only if you choose Deel-managed payroll. Background checks are coming soon, and signing is built into MambaHR. The full list is in our Data Processing Addendum, provided with the order form, and we tell you before it changes.
What happens if there is an incident?
We tell you without undue delay, explain exactly what was affected, and give you what you need for your own notices. That commitment is in our Data Processing Addendum, provided with the order form.
Does any of it train AI?
No. Names, salaries, leave, and health information never train any model, ours or anyone else’s. That is written into our Data Processing Addendum, provided with the order form.
Something we didn’t cover? hello@mambahr.com.
Encrypted, logged, never used to train AI.
Join early access. Your security team can review everything on this page before your group opens.