messenger G

Privacy Policy

Version of 9 November 2026

messenger G is a corporate messenger for employees of an organization: regular and secret chats, groups, channels, calls, a news feed and an employee directory. The app runs on iPhone, Android, Mac and in a web browser. The messenger G server is deployed and maintained by the operator for the organization's employees. All data, except what is listed under “Who data is shared with”, is stored on this server. A request to connect a new organization is received not by its server but by the company directory server of the service operator (see “Request to connect an organization”). The Russian version of this policy is the primary one.

Personal data operator: Ruslan Galifanov

Questions about your data and deletion requests: galifanov@gmail.com

What data is processed

Data comes from the employees themselves (the registration request, the profile, messages and content), from whoever invited them and from administrators (the invitation, manager, roles), and automatically from the app and the server during sign-in and use (sessions, push notification addresses, logs).

Account and profile

The profile (name, job title, department, phone, email, photo, manager, online status) is visible to other employees in the directory.

Messages and content

Regular chats, groups, channels and the feed are stored on the server without end-to-end encryption: TLS protects them in transit and disk encryption on the server. Search over them runs on the server. Chat members see the chat's messages; moderators see posts awaiting moderation and reports.

Secret chats

A secret chat is created by the employee. Its messages and attachments are end-to-end encrypted on the device with the MLS protocol (OpenMLS library): neither the server nor administrators can read them. The exception is the text of a message that a chat participant attaches to a report themselves: the server and moderators receive it. The server only relays encrypted data and keeps it until it is delivered to the other participants' devices, but no longer than 30 days; it is not included in server backups. The server can see who takes part in a secret chat, when messages are sent and the size of the encrypted data. A secret chat exists on one device only, and searching it happens only on that device.

Calls

Call audio and video are encrypted (DTLS-SRTP) and travel directly between devices or through the messenger G relay (TURN) server; call keys are bound to the participants' device keys, and the call screen shows a code to compare. The server does not record calls. The server stores who called whom, the call type (audio or video), the start, answer and end times and the end reason.

Call connection diagnostics: after an answered call the device reports to the server whether audio and video connected and how long it took, the type of path (direct, through NAT, or through the TURN relay server over UDP, TCP or TLS), the amount of audio transferred, the number of connection restarts and (on iPhone) whether the device audio session was active at the time of connection. Device IP addresses and ports are not included. The server writes it to its technical logs together with the call identifier (which can be used to find out whose call it was), the side (caller or callee), the call type, its state and the end reason (these are also in the call history) and keeps it for the log retention period; it is not stored in the database.

Devices, sign-in and security

Data on the device

On iPhone, Android and Mac the app keeps a copy of the chats in an encrypted local database whose key is stored in the Keychain or the Android Keystore. The web version does not store messages on the device (only in the memory of the open tab) and has no secret chats or calls.

How data is used

Data is not used for advertising or analytics, is not sold and is not used to track users across other apps or websites. The app contains no advertising or analytics libraries; the Firebase library on Android is included only to deliver notifications.

Push notifications

A push notification contains no message text, names or chat identifiers: the push service receives only an opaque notification (or call) number and the unread count. The device downloads the notification text from the messenger G server over a secure connection. On Android without Google services, notifications arrive over the app's own connection to the messenger G server, without third-party services.

Who data is shared with

Data is shared with third parties only to the extent needed for the app to work:

Data is not shared with other third parties, except where required by law. The operator shares data only with services that protect it at a level no lower than described in this policy. App stores (App Store, Google Play) process app installation data under their own rules.

Retention

Account deletion and your rights

Request to connect an organization

An organization that is not yet in messenger G connects with a request: in the app, on the “Your company” screen, tap “Connect your company”. The request is filled in by the organization's contact person. It is received by the company directory server of the messenger G service operator, not by the organization's server (it does not exist yet); the form data is not saved on the device. The request goes to review, and the email to the operator is sent, only after the contact person confirms the email with a code from an email message. Until then, the request with all its data is kept on the directory server for about one day and is visible to its administrators in the admin panel.

What data is collected

The request fields are not written to technical logs: the only part of a request that appears there is its identifier — in the request path, next to the IP address.

How it is used

Who receives the data

How long it is kept

You can ask what request data is stored, or have it corrected or deleted: galifanov@gmail.com.

Changes to this policy

A new version is published at this address with its version date.

Contacts

Operator: Ruslan Galifanov
Support: galifanov@gmail.com
Support page