Last updated: October 25, 2026
Zenlygram's developer does not sell any of your data, and receives no analytics, telemetry, or crash reports from the app. Messaging itself never touches the developer: it goes straight between your device and Telegram. The developer's backend supports account linking, the published FREE or PAID feature policy, entitlements and optional Cloud Tasks — see Feature policy, account linking and Cloud Tasks below for what it receives. Some features connect your device directly to third-party services; they are listed below too.
Zenlygram is an unofficial client for the Telegram network. All messaging traffic goes directly between your device and Telegram's servers using Telegram's official API (MTProto). Your messages, contacts, and account data are governed by the Telegram Privacy Policy. Zenlygram is not affiliated with Telegram FZ-LLC.
Chat history caches, local settings, and PIN hashes for Chat Lock and Secret Vault are stored on your device, including in the device Keychain where applicable. Optional Cloud Tasks content is synchronized with the developer's backend as described below. Call recordings are stored on your device too, and can be uploaded to your own Telegram Saved Messages if you ask for that — see Call recording.
Two optional features keep extra copies of messages. These copies are kept only in the app's local database on this device and are never uploaded:
Turning either feature off deletes the copies it kept on this device and stops it from keeping new ones.
If you had already chosen to turn either feature off in an earlier version of Zenlygram, that choice is kept; the new default applies only where you had not chosen.
If Zenlygram offers call recording in the build you are running, it records only calls you start recording yourself, after a one-time consent screen, and it records both sides of the conversation — your voice and the other person's. Recordings are written to this app's own storage on your device, are excluded from iCloud and Finder backups, and are not synced. The developer never receives them.
A recording can leave your device in two ways, and only if you choose one of them:
While the setting is off, no recording is uploaded on its own; a recording is uploaded only if you pick Send to Saved Messages for that specific recording. Recordings are deleted from the device when you delete them, when the account that made them logs out, and when the last account logs out.
Feature availability follows the published FREE or PAID policy. When a feature requires Zenlygram Pro, the app checks your entitlement with the developer's backend. This does not mean that a subscription product is currently available.
Local Tasks stay on your device unless you explicitly import them into Cloud Tasks. Cloud Tasks is optional and requires a linked account. Its list and task content, dates, completion state, and sharing and synchronization metadata are sent to, stored by and processed by the developer's backend to provide synchronization and sharing. Cloud Tasks is not end-to-end encrypted. Your PINs and the locally stored hidden-message, locked-chat and edit-history data described above are not uploaded as part of Cloud Tasks.
Public feature-policy checks may contact the backend before you buy anything or link an account. Linking and entitlement checks also contact it. Cloud Tasks transfers content through authenticated REST requests; when realtime is available, its messages contain only change hints, not task content, and the app retrieves changes through REST. Depending on the feature you use, the backend receives:
This data is used for account linking, the published FREE or PAID feature policy, entitlements, Cloud Tasks synchronization and sharing, and abuse controls. It is not sold, shared for advertising, or used for tracking. Unlinking an account or logging out does not erase server-held records or cancel an entitlement. A successfully processed server unlink request revokes that device's binding and sessions; an offline local logout does not itself confirm server revocation. To request deletion of records, write to the address under Contact.
Messages are translated by the service you choose in Zenlygram settings under Translate Messages → Service. Quick Translate, the pinned-message bar, whole-chat translation and the translate option in the Send button menu (touch and hold Send to translate the text you are about to send) send the text only to that service. The Translate window (touch and hold a message → Translate, or select text in the message field → Translate) uses Telegram's translation, or Apple's on-device translation when System is selected. If the chosen service fails, the app shows an error (or no translation) and never switches to another service.
Messages in secret chats are never translated, including media captions and text recognized in photos. Copy-protected messages (for example, from chats that restrict saving content, including one-to-one chats where either person restricts saving) are never sent to Google.
Voice-message transcription uses Telegram's service or Apple's speech recognition — the latter when you select the system option, and always on accounts without Telegram Premium (Telegram's own transcription is Premium-only). The app requires Apple speech recognition to run on-device, so the audio is not sent to Apple. Both features run only when you invoke them, apart from Telegram's automatic translation of channels described above.
If you enable the optional Auto-Proxy feature, your Telegram connection may be routed through third-party proxy servers to bypass network blocks. Proxy operators can see your IP address and the fact that you use Telegram, but not the content of your MTProto-encrypted traffic. This feature is off by default.
When you create a Telegram account in Zenlygram, Telegram's servers may ask the app for a sign-up check to confirm that a real person is registering. Only then does the app run Google reCAPTCHA Enterprise, which is part of the official Telegram app code. reCAPTCHA sends device and interaction signals (a device identifier, app performance data and interaction data) to Google. The resulting verification token goes to Telegram's servers, never to the developer. The app runs reCAPTCHA only for this sign-up check. See the Google Privacy Policy and Google Terms of Service.
Besides Telegram, the app connects directly to the services below. Like any server your device connects to, they can see your IP address. The developer operates none of them and receives nothing from them.
Link previews in messages are generated by Telegram's servers, not by your device. Apple speech recognition (voice-to-text) and Apple translation (the System option) run on the device.
Questions: abdurashid1712@icloud.com