Privacy Policy
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
- Full name, job title and department — from the registration request an employee fills in after an invitation; manager and roles (employee, moderator, administrator) — set by the invitation and by an administrator.
- Work email — from the invitation; it receives the invitation, the decision on the registration request, one-time sign-in codes and the account deletion confirmation code.
- Phone number — from the registration request; the employee can change it in the profile.
- Profile photo — from the registration request; metadata (including EXIF with location) is removed on upload.
- Internal account ID, account status (active or blocked), last seen time.
- Settings: theme, language, notification settings, Do Not Disturb schedule and its time zone.
- Invitations: the invitee’s email, who sent the invitation, the manager, the expiry date, when the invitation was used or revoked and by whom. Registration requests: full name, email, job title, department, phone number, photo, manager, who sent the invitation, the decision on the request, who made it and when, the rejection reason.
The profile (name, job title, department, phone, email, photo, manager, online status) is visible to other employees in the directory.
Messages and content
- Messages in regular direct chats, groups and channels: text, replies, forwards, mentions, reactions, pinned messages, drafts, delivery and read marks, folders and chat settings.
- Photos and videos an employee sends to chats and the feed, group and channel photos.
- Voice messages.
- File attachments, feed posts, comments, polls and votes, reports about messages and posts (reason, comment; for a secret chat message — the text attached by the reporter).
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
- Sign-in sessions (devices): platform, device name, app version, sign-in and last activity time, which session ended another one; the device's push notification addresses (Apple Push Notification service token, including the one for calls; Firebase Cloud Messaging token; the browser's Web Push subscription).
- Public keys of devices and of the account for secret chats and calls, confirmation of a new device from a trusted one. Private keys stay on the device: in the Keychain (iPhone, Mac) and the Android Keystore.
- The list of blocked contacts: whom the employee blocked and when.
- One-time sign-in codes (stored on the server only as a hash) and the number of failed attempts.
- Action log: actions of administrators and moderators (registration decisions, invitations, roles, blocking, moderation of the feed and reports), as well as each employee’s sign-ins and sessions (sign-in, new device, session ended, sign-in locked after wrong codes) and changes to their keys and trusted devices. It records who did what and when — identifiers only, without names, emails or texts.
- Technical logs of the web server and the server: IP address, time, request method and path without parameters, response code; call connection diagnostics (see “Calls”). Message texts, emails, phone numbers and sign-in codes are not written to logs.
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
- Running the messenger: messaging, calls, the feed, the employee directory, notifications; finding out why calls fail to connect (call connection diagnostics).
- Security: sign-in with a code, notifying all devices about a new sign-in, confirming new devices, blocking accounts, blocking contacts, reports and moderation, the action log.
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:
- Apple Push Notification service (Apple) — on iPhone and Mac: device token, notification or call number, unread count.
- Firebase Cloud Messaging (Google) — on Android with Google services: device token and Firebase installation ID (Google uses it to determine which device to deliver a notification to), notification or call number, unread count.
- Browser Web Push services (Google, Mozilla, Apple or Microsoft, depending on the browser) — in the web version, if notifications are allowed: the subscription address and the encrypted notification number and unread count.
- Email service — the organization's mail server or Mailgun (Mailgun Technologies, Inc.), if the operator uses it: recipient address, subject and text of the email (sign-in code, invitation link, registration decision and rejection reason, account deletion confirmation code; to administrators — a notice of account deletion with the name of the person who deleted it; for a request to connect an organization — the email confirmation code and emails to the contact person about receipt of the request, the decision with the rejection reason and the company server being ready, and an email with all request data to the operator).
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
- Profile — while the account exists.
- Notification content on the server — 7 days; device sync events — 30 days.
- Sign-in code: once it is used to sign in, its record is deleted immediately. An unused code is valid until it expires, and its record is deleted on one of the later sign-in code requests (by any employee), but not earlier than one day after expiry and not before a sign-in lock after wrong attempts ends.
- Invitations and registration requests — for a period set by the operator; until it is set, they are not deleted automatically. The exception is the photo of a rejected registration request: it is deleted 30 days after the decision.
- Unfinished file uploads — 24 hours; files no longer referenced — about one day.
- Secret chats — until delivered to the other participants' devices, no longer than 30 days.
- Messages in a chat with auto-delete — until the period chosen for the chat (1 day, 1 week or 1 month).
- An employee can edit or delete their own message within one hour after sending. Deleted messages and earlier versions of edited messages are kept on the server together with the conversation and are visible to those who see the conversation — chat members, and in a channel everyone who can see the channel: a deleted message is shown as “Message deleted”, and tapping it shows its original content with attachments. When a message is reported, a moderator sees it, including a message its author deleted, and its earlier versions until the report is resolved. A message deleted by a moderator after a report or by auto-delete is erased from the server together with its earlier versions and attachments (a file is deleted once nothing else refers to it: a forwarded or re-sent file remains). In secret chats, a deleted message is deleted on the devices.
- A task created from a message in a regular chat keeps a copy of the message text and references to its files under the rules for tasks: the copy is visible to the task participants and their managers, and it remains after the author edits or deletes the message and after the message is auto-deleted (the files are not deleted while the task refers to them). If a moderator deletes the message after a report, what was copied from it into tasks is erased, and the files are deleted once nothing else refers to them.
- A device's push notification address is deleted when its session ends.
- Server technical logs — as they fill up: no more than 5 files of 20 MB per service.
- Requests to connect an organization — see “Request to connect an organization”.
- Everything else (messages, the feed, the action log, the history of sign-ins, calls and reports) is kept for a period set by the operator; until it is set, data is not deleted automatically.
Account deletion and your rights
- You can delete your account in the app: “Settings” → “Delete account”, confirmed with a code from an email. Deletion happens immediately after confirmation; administrators receive an email about the deletion with the name of the person who deleted the account. The account cannot be restored; you can only come back with a new invitation.
- What is deleted: personal data — the name (replaced with “Удалённый пользователь”, Russian for “Deleted user”), work email, phone, photo, job title, department, last seen time, roles, registration requests; settings, drafts, folders, notifications, sign-in codes and the list of blocked users; push notification addresses; comments on submitted reports and the texts attached to them; the public keys of the account and devices and participation in secret chats. All sessions end on all devices. On the devices, the app erases its data — the copy of chats, secret chats and keys (on other devices — when they next connect to the server).
- What remains and why: messages, files, posts, comments, reactions and poll votes sent to direct and group chats, channels and the feed, including messages the employee deleted themselves and earlier versions of edited ones, remain with the other participants, signed “Удалённый пользователь” (“Deleted user”) — without the name, photo or contact details. messenger G is a closed corporate system, not a public service: people can join only by invitation and with an administrator's approval, and chats are visible only to their members — employees of the same organization. These messages are part of the other participants' work conversations, so they do not disappear for them when one account is deleted. For the same reason, chat membership remains: the member list shows “Удалённый пользователь”. Secret chat messages are stored only on the participants' devices (except the text that another participant attached to a report themselves), and the server cannot delete them from other participants. The sign-in history keeps the platform, app version and time, without the device name. Reports submitted from the deleted account keep the type and reason — without the comment or attached text. Other employees' reports about its messages remain with moderators as submitted, including the message text attached to them: these are other employees' requests, just like their conversations. Call history, other employees' lists of blocked users and the action log keep only the internal account ID. Copies of the former profile in the sync queues of other employees' devices are erased within 30 days at most.
- You can also request account or data deletion, ask what data is stored, or have it corrected: galifanov@gmail.com. An account is deleted on request within 30 days, and completion is confirmed by a reply email.
- Deleting the account also withdraws consent to data processing.
- You can end the session of any device in “Settings” → “Devices” and turn off notifications in “Settings” → “Notifications” and in the system settings.
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
- About the organization: name, country, registration number, website (optional), number of employees (a range) and the preferred company code — it becomes the address of the company server and the code employees enter to sign in.
- The contact person's full name and job title (optional).
- The contact person's work email — only on the organization's domain (addresses of public email services are not accepted). It is confirmed with a code from an email: the code is valid for 10 minutes and is stored on the server only as a hash, together with the number of wrong attempts.
- The contact person's phone number.
- The app language (emails about the request are sent in it), the request status, the time the request was sent, the email was confirmed and the decision was made, and the rejection reason.
- The marks “I am authorized to apply on behalf of the organization”, acceptance of the Terms of Use and consent to the processing of personal data: the request cannot be sent without them.
- The device IP address — to limit the request rate (the counters are kept in server memory and are not written to the database) and in the technical logs of the web server and the server, as for any request; it is kept for the log retention period (see “Retention”).
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
- Reviewing the request: checking the organization and that the request comes from its representative.
- Contacting the contact person: emails about receipt of the request, the decision and the company server being ready; clarifying details by email or phone.
- Connecting the organization: adding the company to the directory (the organization's name and the server address based on the company code), setting up the company server and creating on it the first administrator's account with the contact person's full name, job title and work email. After that, this account is processed like any other (see “Account and profile”).
- Protecting the service from abuse: the number of requests and code emails is limited, including per email address.
Who receives the data
- The messenger G service operator — Ruslan Galifanov: administrators of the company directory server see all request data, including unconfirmed requests (in the admin panel and in the operator's commands on the server), and review confirmed requests; a confirmed request with all its data is sent to the operator by email. Decisions made in the admin panel are recorded in the action log: who made the decision and when, the request identifier and the company code — without the contact person's data.
- The email service (see “Who data is shared with”) — emails to the contact person and the email to the operator.
- The company server, after the request is approved — the contact person's full name, job title and work email for the first administrator's account.
- After the organization is connected, its name and the company server address are shown to anyone who enters its code on the “Your company” screen.
How long it is kept
- A request whose email has not been confirmed is kept for about one day after it was sent and then deleted; a new request with the same email replaces the previous one.
- A confirmed request is kept until the operator makes a decision.
- A rejected request is deleted 30 days after the decision.
- An approved request (the company and its first administrator were created from it) is kept for a period set by the operator; until it is set, it is not deleted automatically.
- The email to the operator with the request data is kept in the operator's mailbox for a period set by the operator.
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