DGram Privacy Policy

Effective date: June 30, 2026

1. Scope

This Privacy Policy explains how the DGram Android application ("DGram", "the app", "we", "our") handles information when you install and use the app. It covers the DGram app layer, including local app features and optional DGram-specific proxy features.

This policy does not replace Telegram's privacy policy for the Telegram messaging service, Telegram accounts, Telegram cloud chats, Telegram contacts sync, Telegram calls, bots, channels, payments, or other Telegram server-side services.

2. Relationship With Telegram

DGram connects to the Telegram network using Telegram APIs. To create or use a Telegram account, you may provide Telegram with data such as your phone number, login email if enabled by Telegram, profile information, contacts if you choose to sync them, messages, media, calls, location messages, and other Telegram account data.

Telegram, not DGram, operates the Telegram cloud service and determines how Telegram account data is stored, transmitted, retained, and processed on Telegram servers. You can review Telegram's policy at https://telegram.org/privacy.

3. Information Handled by DGram

3.1 Local app data

DGram may store app settings and feature data locally on your device, including interface preferences, folders, tags, feed settings, proxy settings, cache settings, and other app configuration. This data is used to operate app features and normally remains on your device unless you export it, back it up, or send logs/support information yourself.

3.2 Telegram content displayed in the app

DGram displays Telegram chats, media, contacts, channels, stories, calls, and other Telegram content available to your account. This content is transmitted through Telegram infrastructure and is subject to Telegram's service behavior. DGram may cache media and message-related data locally to improve performance, as Telegram clients normally do.

3.3 Optional DGram proxy and Xray features

If you enable DGram's proxy or Xray route features, the app may store proxy profiles locally and may contact a configured DGram route API endpoint to retrieve route metadata. When your device contacts any server, that server may receive technical connection data such as IP address, request time, and user agent or network metadata. Proxy traffic may also be visible to the selected proxy provider according to that provider's own practices.

DGram exposes selected Xray routes to Telegram through a local SOCKS endpoint on your device. If an Xray route is unavailable, DGram may allow traffic to use the direct system route, which may include your active system VPN.

3.4 Logs and diagnostics

The app may generate technical logs on your device for troubleshooting. Logs can include app version, device model, operating system version, connection state, crash details, and error messages. DGram does not require you to send logs, but if you share them with support, they may contain personal or account-related information depending on the issue.

4. Permissions

DGram may request Android permissions to provide Telegram-compatible messaging features. Depending on how you use the app, these permissions may include:

• Contacts: to help Telegram find contacts who use Telegram, if you choose to sync contacts.
• Camera and microphone: for photos, videos, QR scanning, voice messages, and calls.
• Photos, media, and files: to send, receive, save, and cache media and documents.
• Notifications: to show message and call notifications.
• Location: to send your location or live location when you choose to use those features.
• Phone and call-related permissions: where supported, for login verification or Telegram call features.
• Network and foreground service access: to connect to Telegram, proxies, and optional DGram network services.

You can manage permissions in Android system settings. Some features may not work if required permissions are denied.

5. Third-Party Services

DGram may rely on third-party services that are part of the Android and Telegram ecosystem, including Telegram services, Google Play services, Firebase Cloud Messaging for push notifications, Google Play billing or integrity services where applicable, map/location providers where applicable, and any proxy provider you choose to use.

These third parties process data according to their own policies. DGram does not control Telegram's, Google's, or a proxy provider's independent processing of data.

6. How Information Is Used

Information handled by DGram is used to:

• provide Telegram-compatible messaging, media, calls, notifications, and account access;
• operate DGram-specific local features such as folders, tags, feeds, appearance settings, and proxy settings;
• maintain security, prevent abuse, and troubleshoot technical problems;
• improve app reliability and compatibility.

DGram does not sell personal data. DGram does not use Telegram message contents for advertising.

7. Sharing of Information

DGram may share or transmit information in these situations:

• to Telegram servers when you use Telegram account and messaging features;
• to Google or Android platform services when using push notifications, app integrity, billing, crash, or platform services included in the build;
• to proxy or Xray route providers when you choose to route traffic through them;
• to support or diagnostics recipients if you choose to send logs or support emails;
• when required by applicable law or legal process.

8. Retention and Deletion

Local DGram settings and cache remain on your device until you change settings, clear cache, remove data through Android settings, or uninstall the app. Telegram account data is retained and deleted according to Telegram's settings and policies. You can manage Telegram privacy and data settings inside the app under Telegram's Privacy and Security settings.

9. Security

DGram uses Android platform security and Telegram-compatible transport behavior to provide the app. No app or network system can be guaranteed to be completely secure. You are responsible for keeping your device, Telegram account, passcode, two-step verification, and proxy configuration secure.

10. Children

DGram is not directed to children. Users must comply with Telegram's age and account requirements and with applicable local law. If you believe a child has provided personal data through DGram in a way that should be removed, contact the developer using the contact method below.

11. Your Choices

You can control many privacy choices through Android settings and Telegram privacy settings, including permissions, notification access, contacts sync, active sessions, blocked users, phone number visibility, profile visibility, location sharing, and cache management.

12. Contact

For privacy questions about the DGram app layer, contact the developer using the developer email address shown on the DGram listing in Google Play.

For Telegram account data and Telegram server-side services, use Telegram's privacy and support channels described by Telegram.

13. Changes

This policy may be updated when DGram features, third-party services, or legal requirements change. The effective date at the top of this page indicates the latest version.