Privacy · Android
This document explains what data is processed when using Serpmonn Messenger, on what basis, for how long, what rights users have, and how to stop processing. It covers Serpmonn Messenger (Android) only and does not replace separate policies for serpmonn.ru or other Serpmonn products.
The personal data operator for Serpmonn Messenger is the rights holder of the Serpmonn project.
Rights holder: Sergey Popov. Status: self-employed. Tax ID (INN): 366230412849.
Contact for privacy requests: support@serpmonn.ru.
Project site: https://serpmonn.ru. App page: https://serpmonn.ru/frontend/en/messenger.html.
Requests for access, correction, restriction, or deletion should be sent to the email above. Responses are provided within timeframes required by applicable Russian Federation law.
This Policy governs information processed when installing, configuring, and using Serpmonn Messenger on the user’s device.
It does not cover: (a) serpmonn.ru and other Serpmonn products with separate documents; (b) app stores (RuStore, Google Play, etc.), payment systems, and telecom operators; (c) other users’ actions in P2P chats; (d) third-party sites linked from the app or site.
Using the app means acceptance of this Policy to the extent permitted by law. If the terms are unacceptable, uninstall the app and stop using it.
Serpmonn Messenger is a peer-to-peer (P2P) client with end-to-end encryption of message content. Chat content is intended to be exchanged directly between participants’ devices.
The operator does not run a centralized cloud account for storing message text, attachments, or chat keys in order to read content.
Processing follows: data minimization; on-device storage by default; encryption of chat content; no sale of personal data; no advertising profiling by the operator.
P2P and encryption do not remove the user’s responsibility for their own messages or for securing the device (PIN, biometrics, OS updates).
Depending on enabled features, the following categories may be processed.
The operator cannot guarantee that intermediate network nodes never see technical traffic metadata. Correctly functioning E2E message content remains unavailable to the operator in plaintext.
Processing is performed to provide app features, security, legal compliance, and support responses.
Legal bases (as applicable): user consent; performance of the agreement to use the app; legitimate interests in security and product operation while respecting user rights; compliance with Russian Federation law.
Permissions that may be requested and their purpose. Actual prompts depend on Android version and whether the user enables the related feature. Denying a permission may limit that feature without removing others.
| Permission | Purpose | Required? |
|---|---|---|
| Internet / network state | P2P connectivity and signalling | Needed for online features |
| Notifications | Alerts for messages and events | User choice |
| Biometric / fingerprint | Local app unlock via OS | User choice |
| Bluetooth (scan/connect/advertise) | Nearby/mesh exchange when enabled | Nearby only |
| Wi‑Fi state / Nearby Wi‑Fi Devices | Nearby / Wi‑Fi Direct scenarios | Nearby only |
| Fine location | On some Android versions required by the system for Bluetooth/Wi‑Fi nearby scanning; not used by the operator for advertising location tracking | Nearby on some OS versions |
| Microphone | Voice messages/calls if the feature is available and enabled | User choice |
| Camera | QR scanning to add contacts (when active) | User choice |
| Vibrate | Haptic feedback for notifications | System |
| Foreground service / data sync | Background delivery per OS policy | For background operation |
| Storage (legacy ≤ Android 9) | Compatibility with older OS file access | Older OS only |
A location permission for nearby APIs does not mean the operator builds a movement history on its servers. The operator does not centrally track precise location history.
Core messenger data stays locally until the app is uninstalled, app data is cleared in OS settings, or specific chats/contacts are deleted in-app (if available).
Device backups (if enabled by the user) may include app data under OS/vendor rules. The manifest sets android:allowBackup="false", disabling default auto-backup of app data and reducing cloud-backup risk — this does not remove responsibility for user-made copies (screenshots, exports, manual backups).
Support email is kept as long as needed to handle the request and protect legitimate interests, then deleted or anonymized unless law requires a longer period.
If auxiliary nodes (signalling/relay) are used, technical logs (if any) are kept only as long as needed for reliability and security and are not intended for reading E2E message content.
The operator does not sell personal data and does not share chat content with ad networks.
Sharing may occur when: (1) delivering P2P messages to a recipient chosen by the user; (2) network providers see technical traffic metadata; (3) app stores process install/update data under their policies; (4) public authorities — only on a lawful basis and only for data the operator actually holds; (5) site hosting/support contractors — under contract and only as needed (support tickets, not chat content).
Because of P2P architecture, packets may traverse networks in multiple jurisdictions. Internet traffic is inherently cross-border. The operator does not maintain a separate foreign archive of chats for reading messages.
Absolute security is impossible. Users should update the OS and app; not share the device or unlock codes; verify contacts before adding; understand malware device-compromise risks.
There is no separate cloud Serpmonn Messenger account with the operator. Local processing stops as follows:
After local deletion, the operator cannot restore chats from a cloud archive because no central user message archive exists.
Messages already delivered to other participants remain on their devices — deleting on the sender’s side does not wipe recipients’ copies (decentralized model).
For store Data safety / account-deletion forms: no cloud account is created; deletion = uninstall + clear app data on device + email request for support correspondence.
To the extent provided by Russian Federation law (including Federal Law No. 152-FZ “On Personal Data” where applicable), the data subject may:
Some data exists only on the user’s device; the operator cannot provide a copy of a local chat database it does not hold. Access/deletion rights for such data are exercised on-device as in section 10.
The app is not directed at children under 13 (or a higher digital-consent age where required by local law).
The operator does not knowingly collect children’s personal data. If such collection becomes known, data the operator holds (e.g. a support email) will be deleted after verification.
Short summary for RuStore / Google Play Data safety forms (details in sections above):
This Policy is governed by the law of the Russian Federation unless mandatory rules of the user’s country require otherwise.
The app is provided “as is”. The operator is not liable for: user message content; other P2P participants’ actions; network or device failures; data loss from device damage/loss; consequences of device compromise; inability to produce local data the operator does not hold.
Users are solely responsible for lawful use of the messenger (including prohibited content, fraud, and third-party rights).
The operator may update this Policy. The current version is published at https://serpmonn.ru/frontend/messenger-privacy/privacy-policy.html (and localized URLs).
The effective date appears at the top. Material changes are reflected by updating the date/version where practical. Continued use after publication means acceptance to the extent allowed by law; otherwise stop using the app and delete data.
Privacy questions: support@serpmonn.ru.
Recommended subject: “Serpmonn Messenger — personal data”.
Rights holder: Sergey Popov (self-employed), INN 366230412849.