Skip to content

Security and data ​

A short customer view. Legal wording lives in the offer and privacy policy on aidir.kz (revision 1.0, 13 November 2026). This page does not claim state SKZI certification or a server country.

Sign-in and 2FA ​

  • passwords stored as hashes;
  • two-factor: authenticator (TOTP) and/or SMS;
  • phone verification is required for SMS 2FA and SMS alerts;
  • session: httpOnly cookie and/or Bearer JWT.

Roles and isolation ​

Every request is bound to an organisation and a role. Another organisation’s data is unreachable. See team and roles.

Files ​

Private uploads (HR, recruiting, attachments) are outside the public site tree. On disk: AES-256-GCM envelope, organisation key wrapped by FILE_KEK. Losing the key loses the files. Integration secrets are encrypted and rotated.

AI perimeter ​

Only Google Gemini and Groq receive tenant text. OpenAI and Anthropic adapters are disabled.

Before a text call the server replaces people and company names, phones, emails, IIN/BIN, cards, and amounts with tokens like [PERSON_1]. The model answer is rehydrated on the server. The log stores metadata (provider, model, sizes, hash), not the text.

Exceptions (bytes sent as-is, log depersonalized=false):

  • image OCR;
  • voice STT (Groq Whisper).

Names that are not in the organisation dictionaries are caught only by regex (phones, IIN, email, amounts), not “every third party on earth”.

self_hosted is reserved: calls fail with “not implemented” until that provider exists. That is not an out-of-the-box on-prem promise.

Backups ​

Organisation backups are encrypted. Restore checks that the snapshot belongs to the same organisation.

What these docs do not claim ​

  • “data is stored only in Kazakhstan”;
  • “certified SKZI”;
  • “nothing leaves the perimeter” for images and voice;
  • “AI runs the company by itself”.

AIDIR client documentation · docs.aidir.kz