For security and legal teams
iiVox information security architecture
This document defines the information-security architecture of the iiVox platform, data-protection measures, and the split of responsibility between iiVox and the Client when using AI communications.
1. Legal
1.1. Call labelling
From 1 September 2025, mandatory labelling of outbound calls by legal entities applies. Major Russian operators (MTS, Beeline, MegaFon, T2) offer labelling so the callee sees the company name and call category. Typical cost is about 0.30 ₽ per attempt. Operators have started blocking mass automated calls without labelling contracts.
iiVox recommendation: the Client must contract labelling with the operator serving callees and ensure the correct company name is displayed on outbound calls via iiVox.
1.2. Consent for advertising autodial
Under Article 18(2) of Federal Law No. 38-FZ “On Advertising”, using telecom networks to distribute advertising via automatic number selection/dialling without a human is prohibited unless prior identifiable subscriber consent is obtained.
1.3. Liability
Spam autodial without consent may lead to administrative fines (legal entities 300,000–1,000,000 ₽; credit and microfinance organisations up to 1,600,000 ₽). iiVox is a technology integrator. Compliance with advertising law, consents and call labelling is entirely the Client’s duty. This page is incorporated into the iiVox public offer.
2. Personal data
2.1. 152-FZ definition
Personal data processed on the platform include names, phones, emails, call audio (biometric personal data in a broad sense), transcripts and interaction history. Audio is used only for technical recording, QA and STT — not for biometric identification/authentication under 572-FZ. Unified Biometric System (EBS) placement requirements therefore do not apply to iiVox, and the Client is not required to register such recordings in the EBS.
2.2. Retention
| Data type | Recommended retention | Basis |
|---|---|---|
| Call audio | 3–6 months (QA); up to 3 years (disputes) | Processing purpose / limitation periods |
| STT transcripts | Until purposes are met (typically until contract end or consent withdrawal) | 152-FZ Art. 5(7) |
| Name, phone | Until consent withdrawal or service completion | 152-FZ Art. 5(7) |
| Call logs | May be kept longer as interaction history | Contract |
After purposes are met, personal data are destroyed within 30 days. Audio is rotated after 30 days on iiVox servers; transcripts are stored encrypted; stop-list on subscriber request is supported.
3. Information security
Infrastructure: Yandex Cloud with ISPDn attestation under 152-FZ at protection level UZ-1, Government Decree No. 1119 and FSTEC Order No. 21; ISO, GDPR, PCI DSS, GOST R 57580. Storage and inference in a certified contour. AI: Yandex SpeechKit and Yandex GPT. Voice media: encrypted gRPC over TLS. Open-source components are audited with SAST/DAST per FSTEC guidance.
| Control | Description |
|---|---|
| API authentication | Tokens on every API request |
| Roles and access | Client-side staff access split |
| Encryption | Data at rest and in transit |
| Logging | Actions on data |
| Access control | Infrastructure access |
| Retention settings | Configurable retention |
| Data deletion | Guaranteed destruction on request |
| Webhook security | Protected webhook delivery |
| Logical isolation (multi-tenancy) | Per-client DBs and model context; no cross-tenant access |
| Incidents / Roskomnadzor | iiVox promptly informs the Client for joint regulator notification (24 hours under RF law) |
De-identification adapter before model input. iiVox is not liable for Client-connected telephony, operator policy changes, labelling, tariffs, number blocks or operator outages.
4. AI component security
New agent versions are crash-tested in a sandbox; prompt-injection resistance; models receive de-identified data; dialogue context is scoped; logs encrypted with limited retention. Framework: 152-FZ, 572-FZ (with §2.1 caveat), 38-FZ, FSTEC Order 21, Decree 1119, GOST R 57580.
Final provisions
This page is part of the iiVox public offer. Use of the platform means the Client collects subscriber consents, contracts call labelling, and accepts full responsibility for advertising and personal-data law and for telephony operators.
Current version is published on the iiVox website. Last updated: 28 August 2026.