Your company’s data, kept apart and safe.
How OneKin protects the data a company trusts it with, in plain words: where it’s held, who can see it, and what happens if something goes wrong.
Companies evaluating OneKin can ask us for our security and privacy information. Ask about the company edition
What we hold, and why: Private by design. Last updated 20 October 2026.
Where your data is
What we do
- Our database is in the United Kingdom, and the app’s servers run there too. Our emails are sent from the European Union.
- Each company’s data is kept apart from every other company’s, on every request, and automated tests check that it stays that way.
- Encrypted in transit and at rest.
- Uploaded files are read without being kept, and work emails in the chart are held only in a form that can’t be read back.
Limits, stated plainly
- Some processing happens elsewhere: pages reach you through our hosting provider’s global network, which keeps its request logs on its own systems, and a scheduled job that deletes data past its time runs on servers in the United States, with a safeguard for each transfer.
- Our customers’ admins can see the current list of our sub-processors in the app, and anyone can ask us for it.
Members’ own records
What we do
- Ratings, notes, conversations and plans stay in the member’s browser, or, if they turn on their records on every device, are encrypted on their device first, with a key only they hold.
- Neither their company nor OneKin can read them. No role can: not an admin, not HR, not our staff.
- Help me recover is off unless a member turns it on. Then we hold a locked copy of their key, which we can open only for that member, after they sign in again and a 72-hour wait that every one of their devices is told about. Their company can’t turn it on or ask for it to be opened.
Limits, stated plainly
- As with any web app, the protection relies on the code the server sends.
- What’s kept in your browser is as safe as your device: use a device that’s locked and encrypted.
Signing in
What we do
- You’re emailed a six-digit code, which lasts 10 minutes and works once. There’s no password.
- Members can choose to sign in with their device’s screen lock instead, and a company can have its people sign in through its own sign-in, or require it.
- Codes and session secrets are never stored in a readable form, and sign-in attempts are limited.
- Sessions end 30 days after they were last used, and 90 days at most. Through a company’s own sign-in, a session lasts seven days at most and is checked with it every 8 hours.
- When someone’s membership ends, however it ends, their sessions end at once, on every device.
Limits, stated plainly
- A code by email isn’t multi-factor: anyone who can read the mailbox can sign in. The device’s screen lock, or the company’s own sign-in, is the stronger way.
Access controls and least privilege
What we do
- Each role sees only what it needs: a member, the chart and their own record; HR, the chart and its imports; an admin, who has joined, the chart and the audit log.
- No permission exists that could read another member’s records.
- Our systems and our staff have only the access they need.
- Our automated maintenance runs under an account of its own, limited to its tasks: it can’t read the contents of a company.
- Every change of the Admin or HR role is in the company’s audit log, which its admins can read.
Our staff’s access
What we do
- Our staff see inside a company only in a support session: opened with a reason, for 8 hours at most, with a banner on every page.
- Everything they do, and every part of the company they open, is in the company’s audit log, with the reason.
- A company can require its approval instead: then a session opens only once one of its admins approves it, for the time approved. In an emergency it opens for an hour at most, recorded as an emergency and shown to its admins until one of them acknowledges it.
- They can never sign in as a member, and never read a member’s own records.
- Our staff use strong authentication, and unusual patterns of staff access are flagged.
Audit logging
What we do
- Privileged actions and refusals are recorded in a tamper-evident audit log, kept for a year and readable by the company’s admins.
- It never holds an address, a name, a file’s name, a code or anything a member records.
Retention and deletion
What we do
- Data is deleted on fixed schedules by an automated process that records what it deleted.
- A company’s admins can download everything held about one person, or erase them, in the app. Members can download what’s held about them, and delete their own account, themselves.
- When a company leaves, everything of its is deleted: it can be restored for seven days, then every row goes. Copies in the database provider’s encrypted backups expire in the normal course.
- Before the end, a company can ask for a copy of its organisation chart and members.
If something goes wrong
What we do
- If a personal data breach affects a company’s data, we tell it without undue delay, and within 48 hours of becoming aware: one email to all its admins, recorded in its audit log.
- The notice says what happened, which of the company’s data it affected, what we’ve done and what we recommend.
- We keep a record of every breach, and of what we did about it.
Building it safely
What we do
- We review the service’s security regularly, and fix what we find in order of risk.
- Strict browser security policies stop the app’s pages sending data to other websites, and no third-party scripts, advertising or AI services run in it.
- Every change is checked by automated tests, and the software we depend on is pinned and checked for known vulnerabilities.
- We don’t sell personal data, and we never use customer data or anything you record to train AI.
Report a security problem
If you think you’ve found a security problem in OneKin, please tell us. We read every report.
Email security@onekin.app with what you found, where, and the steps to see it.
- Don’t access, change or delete data that isn’t yours, and stop as soon as you reach any.
- Don’t disrupt the service or anyone using it, and don’t test on a company’s people.
- Give us reasonable time to fix it before telling anyone else.
We’ll reply to say we have it, and tell you when it’s fixed. We don’t run a paid bug bounty.
The same details, for security tools: /.well-known/security.txt