> For the complete documentation index, see [llms.txt](https://me0-50.gitbook.io/telega-app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://me0-50.gitbook.io/telega-app/en/privacy.md).

# Privacy Policy

Last updated: October 27, 2026.

This policy describes the current iOS version of Telega App, developed by Rudaki, Inc. Telega App is a client for your own key or a compatible subscription link, including one issued by Telega Panel. Telega Panel is a separate panel based on 3x-ui, installed and administered by its server owner. The app itself does not provide VPN access. If you use a third-party server or panel, its operator sets its own data-processing rules.

## Keys, settings, and storage

The app stores added links, keys and received configurations, the selected server, connection and interface settings, and technical state on your device. These may include access secrets and server addresses. They are saved in app data and passed to the system VPN service and network extension as needed to connect. A rollback snapshot of earlier state may also be retained on the device.

Removing a key in the app removes it from the main list, but does not itself confirm removal of all copies from the rollback snapshot, system VPN configuration, device backups, iCloud, or the provider's server. Uninstalling the app also does not establish that a third-party server operator has deleted its records. If you need help with deletion, contact us below; for data held by another server operator, also contact that operator. Do not send support your secret key or subscription link.

## Import and connections to your servers

When you add or refresh an HTTPS link, the app requests it from the server you specify. The request may include the secret link's path or parameters, your IP address, ordinary network headers, operating-system type and version, device model, app version, and an `x-hwid` random pseudonym scoped to the provider's domain. This pseudonym is derived from a random local value and is not a hardware UDID. The server, its host, and network intermediaries process the request under their own rules. Do not share the link: it may grant access to your configuration.

When VPN is active, network traffic follows your configuration through the selected server or other configured routes. The VPN server operator and network providers may receive and retain technical information available to them; their practices are not governed by this policy. Function and privacy also depend on the protocol, routes, DNS and settings of your server and devices.

To display latency and choose a server at your request, the app may check the addresses and ports of your servers using TCP or ICMP. If you enable local automatic selection, which is off by default, the app checks servers in the current key after refreshing it and before connecting the VPN. These checks may be visible to the relevant servers and your DNS provider. Selection is based on measured latency, not server load; the full key link is not sent to the remote ORIEN selector. If no measurements are available, the app notifies you and uses the previously selected server. Results and the preference may be stored on the device.

## DNS and connectivity checks

DNS requests are handled by the resolver selected in your settings or configuration. The code supports Cloudflare, Google and Quad9 options; the actual route depends on the configuration and protocol. Resolver operators may receive DNS request data under their own policies.

When the legacy failover mechanism is enabled and its conditions are met, the app may check network reachability using Cloudflare, Google and Apple. Those requests expose your IP address and ordinary connection metadata to the respective services. Availability depends on the version and saved settings.

## Legacy ORIEN requests in the current iOS build

If an added subscription contains provider account or support links, the app may fetch a public link policy from `api.orien.cc`. The code does not add your key or installation identifier to this request, but the server and network receive your IP address and ordinary HTTPS metadata.

If the selected key belongs to `obuna.osonak.tj`, after a connection is established the app may perform up to two short reachability checks against `api.orien.cc`. The check does not add the key, configuration, or pseudonym to the request, but the recipient receives the IP address and ordinary HTTPS metadata.

The automatic diagnostic-event upload and remote ORIEN auto-selection channels are disabled in this build, including when a prior consent or mode was saved. A previously saved choice and the local queue of such events remain on the device; starting the disabled service does not change them or upload events. This does not establish deletion of data that may have been sent by older versions; contact us to request deletion of previously shared data.

## Camera, clipboard, and local network

Camera permission is requested when you choose to scan a QR code. Code recognition happens on the device; this mechanism does not send camera frames to a server. The clipboard is read when you tap the paste button. Scanning or pasting fills the field; adding a key requires a separate action.

When you enter a special TV pairing code, the app may send the selected subscription link or configuration to the specified local-network device over HTTP together with the pairing token. Share a key only with a device and network you trust: the link or configuration contains an access secret.

## Apple ID and iCloud

The app retains code for Sign in with Apple and iCloud synchronization. If this feature was enabled in an available app version or an earlier state remains on the device, it may process an Apple user identifier, name and email supplied by Apple, and synchronize a snapshot of keys, configurations and settings through the user's iCloud storage. First launch alone does not overwrite the cloud snapshot. The current iOS interface does not display a separate screen for enabling this feature; availability and actual data deletion must be verified for the relevant version and account.

Apple processes iCloud data under its own terms. Do not assume uninstalling the app deletes an iCloud snapshot. If you previously used synchronization and wish to request deletion, contact us and review your Apple ID and iCloud settings.

## Notifications

After a key is successfully added, the app may request system notification permission. If permitted and an expiry date is supplied by the server, it may schedule local reminders before and at expiry. The device uses the date and technical identifiers for scheduling; the secret link is not included in reminder text. You can change notification permission in iOS Settings.

Firebase Messaging components are included in the app, but the inspected iOS build does not contain a usable Firebase configuration, so this code does not configure Firebase for remote push notifications. Local reminders work independently of Firebase. This policy must be reviewed if the build contents change or Firebase is configured. A history of received notifications may be stored on the device.

## Support and retention

When you email us, we receive your email address and message contents. Retention and handling depend on the email service and the nature of your request. Do not send passwords, tokens, keys, QR codes or other secrets. We do not claim that third-party VPN servers, DNS providers or other services follow a universal no-logs policy.

For data processing and deletion questions: <jaman2001jj@gmail.com>.
