Security and privacy

How Tanbu protects access, data and people

This page describes, in plain terms, how Tanbu controls access, keeps each organization’s data apart, protects people in results and limits what reaches the AI. It is written for the IT, security and procurement teams who review a platform before it is used.

Each statement describes what the product does today. The last section lists what Tanbu does not claim.

Access and roles

Roles
Tanbu works with three organization roles: HR admins manage the whole organization, managers work within the units they are responsible for, and employees use their own participation area.
A manager’s scope
Managers see only the data of the units they are responsible for and those units’ sub-units; a manager with no unit assignment sees nothing.
Where permissions apply
Permissions are enforced on the server rather than only hidden in the interface; a user reaches only the data their role and scope allow.

Sign-in and sessions

Corporate sign-in
For organizations whose identity provider supports OIDC, employees can be set up to sign in with their corporate accounts.
Setting it up
The HR admin sets up the organization’s OIDC connection from the settings screen; it cannot be switched on for everyone until the admin has completed a successful test sign-in with their own account.
Passwords and sessions
Account security includes a password policy and temporary lockout after failed sign-ins; signing out, resetting the password or deactivating the account ends all of that user’s sessions immediately.

Each organization’s data, kept apart

Separation
Tanbu is multi-tenant: each organization’s users, settings, surveys and reports are kept within its own tenant and are not visible to other organizations.
Where it runs
Tanbu is delivered as a hosted service on Tanbu Cloud; options for the organization’s own infrastructure are assessed separately.

Privacy in results

Small groups
Scores for very small groups are not shown; a minimum group size protects individuals, with a stricter threshold for sensitive breakdowns.
Anonymous surveys
In an anonymous survey, responses are stored without the respondent’s name or account; HR cannot see who answered, and scores appear only at group level.
A setting that stays fixed
Targeted anonymous surveys cannot be sent to very small audiences, and the anonymity setting cannot be changed once a survey is deployed.

Helia and your data

Group level
Helia is designed to interpret group-level findings and does not make decisions about individuals.
What reaches the AI
Open-text answers from anonymous surveys are never sent to AI-assisted analysis. Other open-text answers are used only once enough people have responded and direct identifiers such as email addresses and phone numbers have been masked; groups below the privacy threshold are kept out of the AI context.
Careful language
AI-written narratives are kept within what the data supports: a weakly evidenced finding is not stated in definitive language, and interpretation is withheld when data is insufficient.
If the AI is unavailable
If AI is unavailable, surveys, analytics, reports and action plans keep working; Helia’s interpretation and suggestion features are unavailable in the meantime.

Files and reports

Private storage
Reports, certificates and training files are kept in private storage and served only after an authorization check, through short-lived links.
Report versions
Every generated report is stored as a new version; authorized users can reach earlier versions from the report library.
Traceable figures
Every report carries a data lineage and verification summary, so the numbers in it can be traced back to the data state they came from.
Report access record
Report generation and downloads are written to the audit record; if the download record cannot be written, the report is not released.
Training uploads
Videos and documents uploaded as training content are validated and scanned for malware before they are published; if scanning is unavailable, the content is not published.

Stored secrets and the audit log

Connection secrets
The organization’s mail server credentials and corporate sign-in connection secret are stored encrypted in the database and are never shown back on screen.
Audit log
The HR admin can review the organization’s key administrative actions in an audit log screen; secrets such as passwords and keys are never written to the record.

What Tanbu does not claim

This list is kept on purpose. Someone reviewing a platform should know where it stops as clearly as what it does.

Security certification
Tanbu holds no independent security certification today and does not claim one.
Penetration testing
No independent penetration test report is published.
Data location
Tanbu does not promise that data is kept in a particular country.
Multi-factor sign-in
Tanbu has no multi-factor step of its own. When employees sign in through your identity provider (OIDC), that provider’s sign-in rules apply.
SAML and automatic user provisioning
Corporate sign-in is through OIDC. SAML connections and automatic user provisioning are not offered.
Uptime commitment
No uptime percentage or service level is published.
Regulatory status
Tanbu describes the controls it provides; it does not claim a KVKK or GDPR compliance status on your organization’s behalf.
Customer-held encryption keys
Organizations cannot bring their own encryption keys.

For how this website processes the data you send through the demo form, see the Privacy Notice.

In a demo, we can go through these controls with your IT and security team.