Security and data
Each company owns its data
Security is designed on a zero-trust model: no user, service or Sahman employee gets access by default, and every action is checked and logged.
Principles
Isolation by company
Every company has its own database and its own encryption keys. Only agreed aggregates reach the shared group layer.
Access by role
Single sign-on with two-factor checks, roles and row-level access. A school director sees only their school.
Access by request only
Sahman engineers reach client data only on request, for a limited time, with the session recorded.
Encryption
Encrypted in transit and at rest, including backups, with a separate key for every company.
An audit log
Who viewed or exported what, and when. The log is kept in the client’s country.
Backups in the same country
Daily copies on a second site inside the same country.
Boundaries for AI
- The language model never receives rows with personal data.
- Data sent to models through their API is not used to train them.
- Agents call data only through tools, with the user’s rights, never directly.
- Text from emails and websites is treated as data, never as instructions.
- Any outside action needs a person’s confirmation.
Where the data is stored
Each company’s data stays in a data centre in its own country. Only code and templates are shared across countries. The group layer receives only agreed aggregates without personal data.
Group layer
agreed aggregates only, no personal data
Azerbaijan
Uzbekistan
Kazakhstan
company data stays in the country
| Azerbaijan | There is no general rule to keep personal data in the country, but every system that holds it must be registered before processing starts. | A Tier III data centre in Azerbaijan | With consent, or to countries with an adequate level of protection |
|---|---|---|---|
| Uzbekistan | Biometric, genetic and telecom subscriber data must stay in the country. Other personal data may be stored abroad on approved terms. | A data centre in Uzbekistan | Mainly to the 49 countries on the government’s list. Azerbaijan and Kazakhstan are not on it. |
| Kazakhstan | All personal data must be stored in a database or system located in Kazakhstan. | A data centre or cloud region in Kazakhstan | To countries that ensure protection, or with consent |
This is a summary, not legal advice. The details and sources are in our articles on data laws, and every client project is checked with a local lawyer. All articles
In every contract
- A data processing agreement: where data is stored, who may access it, and when it is deleted
- A privacy check under the law of the client’s country
- Personal data of students and children used in analytics only in anonymised form
Where we are today
Sahman is at an early stage. These are the rules the platform is built on; certifications such as ISO/IEC 27001 are planned and will be listed here only once obtained.
Questions
Can another company in the group see our data?
No. Each company has its own space. A dataset reaches the shared layer only when both companies agree, and access to it is by role and logged.
Does our data leave the country?
Each company’s data is stored in its own country. Only agreed aggregates without personal data reach the group layer.
Who at Sahman can see our data?
Nobody by default. Engineers get time-limited access on request, and the session is recorded.
Start with one question
A pilot takes four weeks, covers one question your leader cares about and has a written measure of success.