This is an English translation provided for convenience. In case of any discrepancy, the Russian version prevails. See the Russian version.
1. What this document is about
This document describes data processing inside the VAU! Chat application (the iOS and Android mobile apps, the desktop app, and the web client) — that is, what happens once you have already signed in and are using the messenger. This is a separate document from the en.chat.vau.one website privacy policy, which describes the processing of data of website visitors and customers purchasing a license.
This document applies to the «ВАУ! ЧАТ» (VAU! Chat) app on Google Play (com.vau.chat) and the App Store. The developer and publisher of the app on Google Play is Yauheni Boidak, e-mail: s917by@gmail.com.
2. Who is the controller of your data
VAU! Chat is corporate messenger software that is deployed as a separate instance on the server of the client organization. The controller (operator) of the personal data processed within a particular instance is the organization that deployed that instance and issued you your account — typically your employer or another organization that invited you to the messenger. It is this organization that determines the set of users, the retention period for correspondence, and the procedure for handling data deletion requests.
917 World LLC (ООО «917 Ворлд») develops and licenses the software but has no technical access to the databases of other parties' instances and cannot, on its own initiative, view, export, or delete the client's users' data — this follows from the architecture of the product (see Section 4) and is confirmed by the license agreement (the public offer).
If the particular instance you use is hosted and administered directly by 917 World LLC (for example, if it is the official demo or personal version of the service rather than your company's instance), then 917 World LLC acts as the data controller in this case; see Section 10 for its details.
If you do not know who administers your instance, please check with whoever issued your account or invited you to the messenger.
3. What data the application processes
The application and its server-side component process the following categories of data:
- Account. Login (username), display name, avatar, and any additional profile fields, if the instance administrator has enabled them.
- Device sessions. On sign-in, the system stores the IP address, the user-agent string (for the web client), the device identifier and name, the platform (iOS/Android/web/desktop), and the app version — this is needed for the "Active devices" screen, where you can view and end a session.
- Push notifications. Technical subscription data for notifications (the push service address and the push provider's channel encryption keys — not the app's own keys; on iOS, additionally the APNs/VoIP token). The message text never enters the notification: the server cannot read it (see Section 4), the notification shows only the sender's name and the chat name.
- Contacts within the system. The list of users of your own instance whom you have added as contacts. The application does not request access to the device's address book and does not sync it.
- Calls. To set up audio and video calls, the server processes technical data: which chat the call is in, which participants are calling, and the start and end time. The media stream itself is routed through the call-routing server (LiveKit, see Section 6) and is not recorded by the product — there is no call-recording feature in the application.
- Message metadata. The chat and message identifiers, the sender, the time of sending, editing, and deletion, the read status, reactions (which emoji and who added it), and "reply to" / "forwarded from" links (by identifier, without content). For attachments — the mime type, file extension, the size of the encrypted file, and, for images and video, the pixel dimensions (needed to render a preview before decryption). This is open (unencrypted) data — see Section 4 for details.
- Technical diagnostics. The application may send error reports to the server (the error message, call stack, platform, app version, in-app route, and the request's IP address and user-agent). These reports do not contain the text of correspondence, are stored on the instance's own server (without being sent to external analytics services such as Sentry), and are automatically deleted after 30 days.
- Content of messages and attachments. The text of messages, attachment captions, file names, and the duration of voice and video messages — all of this is encrypted on the device and is never sent to the server in plaintext (see Section 4).
4. What is protected by end-to-end encryption, and what is not
VAU! Chat operates only in end-to-end encryption (E2EE) mode: sending a plain, unencrypted message text is technically disabled at the server level.
Encrypted on the device — the server cannot read it:
- message text;
- the content of attachments (photos, videos, files, voice and video messages);
- attachment captions, original file names;
- the duration and "waveform" of voice and video messages;
- the content of the message's edit history (every version of the text).
Not encrypted — visible to the server as metadata:
- who sent a message to whom, in which chat, and when;
- the fact that a message was edited or deleted, and the time of that event;
- read statuses and reactions (which emoji and who added it);
- which message is being replied to or which chat a message was forwarded from (by identifier);
- the mime type, extension, and size of the encrypted attachment, and, for images and video, the width and height in pixels;
- a flag indicating that "the message contains a link" (without the link itself, which is inside the ciphertext).
This is a trade-off, not an oversight: the server needs this data to display the chat list, enforce file size and type limits, deliver notifications, and build attachment previews without decrypting them. A fully "blind" server (with no metadata at all) is not possible within this architecture — other E2EE messengers work the same way.
5. Where encryption keys are stored
- On a phone (iOS/Android) — in the operating system's secure storage (Keychain on iOS, Keystore on Android).
- In the desktop application — in the operating system's key storage, through a separate secure module of the application.
- In a browser (the web version/PWA, without installing the desktop app) — in the browser's local storage on that device. This storage is not protected at the OS level the way Keychain/Keystore is: it can be accessed given physical access to the device or through malicious code in the browser.
In any case, the keys are never sent to the server. Each device has its own key pair; the key for a particular chat is encrypted separately under the key of each device of the chat's participants. When a new device is added to an account, the keys are transferred in encrypted form, and the code to decrypt them is shown only via a QR code during scanning and is never sent to the server.
6. Who the data is shared with
- LiveKit — the audio and video call routing infrastructure. It receives the technical data needed to connect participants and the media streams themselves during a call; it does not store or record calls in the product's current configuration.
- Push providers (browser push-notification services, Apple APNs) — receive the subscription address, the push channel keys, and the text of the notification itself (the sender's name and the chat name, without the message text).
- Hosting infrastructure — the server on which a particular instance is deployed is chosen and controlled by that instance's operator (Section 2), not by the software developer.
The instance operator may use additional third-party services (for example, an SMTP provider for e-mails, or object storage for files) — the specific list of such services is determined by the operator, not by this application.
7. Data retention and deletion
The product does not set a single automatic retention period for correspondence and does not delete accounts after any such period elapses — with the exception of technical error reports, which are automatically deleted after 30 days. The retention period for other data (messages, attachments, sessions, contacts) is determined by the operator of the particular instance.
On your own, within the application, you can: view and end your active sessions on other devices ("Settings → Devices"), revoke the push subscription of a particular device, delete a chat or contact, and enable auto-deletion of messages in a chat, where that feature is available. You can delete your account yourself: "Settings → Delete account"; see the "Account deletion" page for details.
If you are unable to sign in, or you need a copy of your data, contact the administrator of your instance (see Section 2), or, if the instance is administered by 917 World LLC, use the contact details in Section 10.
8. Children and age restrictions
The application is intended for users over 13 years of age. The instance operator may set a higher age threshold in accordance with the law applicable in its jurisdiction.
9. Certifications and standards compliance
The product does not hold any third-party security or compliance certifications (ISO 27001, SOC 2, HIPAA, or similar). If the instance operator needs to comply with a particular regulatory requirement (for example, the GDPR for users from the EU), ensuring such compliance is the operator's responsibility as the data controller.
10. Changes to this document and contacts
This document may be updated as the product changes; a new version takes effect from the moment it is published on this page.
For questions about data processing in an instance administered directly by 917 World LLC:
917 World LLC, UNP (taxpayer ID) 193645619, Republic of Belarus, Minsk, Kharkovskaya St., 3A. E-mail for inquiries: hi@917.by. The processing of data is governed by the law of the Republic of Belarus.