Skip to content
Aitechestvo

Security

Security & compliance

How Aitechestvo treats your data — and what masking does not guarantee.

Principles

  • No request content at rest

    Prompts, answers and placeholder mappings live only in the gateway's memory for one request. Logs, metrics, events and the database hold metadata only.

  • Fail closed

    If masking cannot be completed (detector error, NER unavailable under a strict policy, an unknown request field), the request is rejected and never reaches the model unmasked.

  • Isolated regions

    The Russian and international regions are independent installations with separate databases, storage, keys and legal operators. They share no data and no network paths.

  • One egress point

    Only one gateway module connects to LLM providers — and only with an already masked request body. Provider addresses are checked by SSRF protection.

Data flow

Employee or system
Gateway in your region
NER service (no internet access)
Log: metadata only
LLM provider
Original values never leave the gateway; the provider gets placeholders, and the answer is restored on the way back.

Where data is stored

The Russian region is a separate installation in Russia. User data is recorded and stored in databases located in the Russian Federation, and the region's third-party services that receive personal data are located in Russia.

  • Servers

    Timeweb Cloud (TIMEWEB.CLOUD LLC): a virtual server in a Moscow data centre (zone ru-3) that runs only Aitechestvo — database, cache, object storage and gateway. TLS terminates on the same server; there is no CDN or proxy in front of it.

  • Backups

    The database is backed up daily; each copy is encrypted on the server before upload and kept for 14 days in separate Timeweb Cloud object storage in Russia. The decryption key is not stored on the servers.

  • Email

    Service emails (address confirmation, invitations, notices) are sent by Unisender Go (Unisender Smart LLC), a Russian provider. Recipient addresses and message texts are not transferred abroad; emails never contain request content.

  • Platform models

    YandexGPT (Yandex.Cloud LLC) and GigaChat (Sberbank PJSC) receive requests after masking under your policy. Providers that do not serve Russia are not available in this region; if you connect your own endpoint, you decide where it is and make that transfer as the operator.

The full list of recipients is in the privacy policy and the data processing agreement.

152-FZ (Russian data protection law)

  • A separate, versioned consent to personal data processing at sign-up and in forms.
  • Localization (Art. 18(5)): data of Russian-region users is recorded and stored in databases in Russia — on a Timeweb Cloud server in Moscow, with encrypted backups in Timeweb Cloud object storage in Russia.
  • No cross-border transfer of Russian-region personal data: emails go through Unisender Go, a Russian provider, and the browser makes no requests outside the region. If you connect a model endpoint abroad yourself, you make that transfer as the operator.
  • For data inside requests we act as the customer's processor (data processing agreement, list of sub-processors).
  • Data subject requests: answers and data exports within 10 working days, account deletion within 30 days.
  • We notify the customer's security contact of incidents within 12 hours and the regulator within the statutory deadlines.
  • Payment records are kept for 5 years after the year of payment, as tax law requires, even after an organization is deleted.

Technical safeguards

  • TLS 1.2+ (1.3 preferred) and HSTS on every external connection.
  • Provider keys and secrets are encrypted with AES-256-GCM and rotatable keys; restore tokens use separate keys and expire after 24 hours.
  • Passwords hashed with argon2id; two-factor authentication (TOTP) with recovery codes.
  • Roles: owner, administrator, security officer, auditor, member. Every change is audited.
  • The site and console load nothing from third parties: own fonts, no analytics, CDNs or external widgets; a strict Content Security Policy.
  • “Did anyone send this INN?” is answered with one-way fingerprints (HMAC), without storing values.

Model output is untrusted

The gateway restores original values into the answer, including links and tool-call arguments. A prompt injection can therefore make a model place data into a link or an image. Clients that render markdown or execute tools must treat the answer as untrusted. Our web chat never loads images from external links and opens links only after a confirmation that warns when the address contains your data.

Residual risks

Masking reduces risk; it is not a guarantee. The “Baseline” template alone does not ensure 152-FZ compliance.

  • A pseudonymized prompt may still be personal data in context.
  • The “warn” and “allow” actions forward the original data to the model.
  • The patterns_only mode skips name recognition.
  • Personal and company names written without capital letters are not detected by NER — such text is forwarded unmasked unless a dictionary or custom pattern covers it.
  • Unclassified provider fields are only scanned, never masked: a detected value rejects the request, but anything the detectors miss there (e.g. lowercase names, or names during an NLP outage under patterns_only) is forwarded as is.
  • Image, document and audio attachments forwarded under “allow” are not masked.
  • Provider-side retention and chat history on your own endpoints are outside our systems; we disable retention wherever the provider allows it.
  • Console chat history is kept in the browser separately for each site address: signing out clears only the current address's copy, and after account deletion another address's copy on that device is cleared only on that address's next visit.
  • Unmask reveals all values to whoever receives the response.
  • Semantic obfuscation is not detected: descriptions that identify a person without explicit data.
  • With platform keys, the provider's prompt caching may create a response-timing side channel.