𝐍𝐚𝐲𝐚𝐆đĢ𝐚đĻ 𝐏đĨ𝐚𝐭𝐟𝐨đĢđĻ

Privacy & Security Portal
NayaGram Logo
💎 Google Play Data Safety Form Ready â€ĸ Updated 23 October 2026

Privacy & Security Charter: 𝐍𝐚𝐲𝐚𝐆đĢ𝐚đĻ 𝐏đĨ𝐚𝐭𝐟𝐨đĢđĻ

A comprehensive, legally binding, and technically transparent declaration of our Zero-Intermediary Architecture, direct MTProto encryption, client-side sandboxing, and complete compliance with Google Play Store and Telegram Developer policies.

Explore Open Source Repository →
✓ Google Play Developer Policy Compliant

Direct MTProto Relay-Free

Pure client-to-Telegram encryption. Zero intermediate servers or proxy relays.

Sandboxed Local Storage

App cache restricted to hardware-isolated Linux UID path: /data/data/org.nayagram.platform/.

100% Auditable Open Source

Complete GPL Android codebase published on GitHub for third-party auditing.

Zero Tracking & No Ads

No tracking SDKs, no behavioral profiling, and strict adherence to Google Play policies.

A.1

Legal Foundation, Independence & Licensing

NayaGram is an independently developed, third-party messaging client built upon the official open-source Telegram Android codebase published by Telegram FZ-LLC under the terms of the GNU General Public License (GPL v2 / v3).

It is of paramount importance to recognize that NayaGram is entirely unaffiliated with, unsponsored by, and unendorsed by Telegram FZ-LLC. All trademarks, service marks, trade names, and product names relating to "Telegram" are the proprietary assets of Telegram FZ-LLC.

As a decentralized application built on free open-source software, NayaGram adheres unconditionally to the open-source spirit. Our modified client-side source code is transparently hosted and publicly auditable on our official repository: NayaGram Official GitHub Repository.

B.1

Telegram API Terms, Official Policy Compliance & Account Ban Grounds

NayaGram is engineered in strict conformity with the official Telegram API Terms of Service. We do not engage in unauthorized API scraping, protocol tampering, or automated spam operations. Every network transmission respects Telegram's rate-limiting, authentication structures, and user safety standards.

Official Telegram Policy References

Users of NayaGram interact directly with Telegram's global infrastructure. Consequently, all users are bound by the following official agreements:

📄 Telegram Terms of Service (TOS) 🔒 Telegram Official Privacy Policy ⚙ī¸ Telegram API Terms of Service

Crucial Notice on Account Suspensions & Server-Side Bans:
Because NayaGram does not operate proprietary user servers or custom databases, all user authorization, phone number verification, and account bans are executed exclusively by Telegram FZ-LLC's servers. NayaGram has zero technical capacity to ban, unban, restore, or modify any user account. Violations of Telegram's policies will trigger autonomous enforcement by Telegram's systems:

  • Spam & Unsolicited Bulk Messaging: Sending unrequested messages to unknown contacts will trigger Telegram's automated anti-abuse system (@SpamBot) or an immediate account freeze.
  • Illegal Activities & Violence: Distributing child abuse material, terrorism promotion, illegal contraband, or incitement of violence results in an instantaneous permanent ban by Telegram.
  • Copyright Infringement & Fraud: Impersonating public figures, phishing, financial scamming, or intellectual property violations are grounds for immediate termination under Telegram TOS Section 2.
  • Flooding Telegram APIs: Attempting to overwhelm server connections or reverse engineer API limitations triggers server-side IP and phone-number blocks (PEER_FLOOD).
C.1

Zero-Intermediary Architecture & Direct MTProto Data Flow

The core architectural pillar of NayaGram is our uncompromising Zero-Intermediary Principle. Unlike predatory applications that route traffic through intermediate proxies or analytics collectors, NayaGram operates as an absolute direct pass-through client.

  • Zero Relay Infrastructure: NayaGram Platform does not own, lease, deploy, or operate any intermediary proxy servers, cloud compute clusters, message gateways, or analytics brokers.
  • Direct MTProto Socket Transmission: Every byte of your chats, high-resolution media, voice memos, files, and contact lookups is packaged using official MTProto 2.0 cryptographic primitives on your device and transmitted via encrypted TLS/TCP/HTTP sockets directly to official Telegram datacenters across Europe, North America, and Asia.
  • Secret Chats End-to-End Encryption: Secret Chats are encrypted with ephemeral Diffie-Hellman keys created on the participating endpoints. The ciphertext never traverses any NayaGram-affiliated machine and remains completely undecryptable by any third party.
D.1

Local Storage Security & Android OS Sandbox Clarification

To deliver an ultra-fast and resilient messaging experience, NayaGram caches your encrypted sessions, recent media, and contact thumbnails locally on your physical smartphone. We enforce strict mobile operating system isolation to ensure your private data is never exposed.

Clarification: What is /data/data/org.nayagram.platform/?

This is NOT an Internet link, website, or web address.
Rather, it represents the local, private internal directory path located inside your Android device's flash storage:

🔒 Protected Android App Sandbox Directory

Technical Architecture Note: /data/data/org.nayagram.platform/ is NOT a web address, URL, or remote endpoint. It is the private, hardware-isolated filesystem sandbox allocated exclusively to NayaGram on your Android device by the Linux kernel (UID isolation). Neither external entities nor other installed applications can access files within this isolated storage.

Under the Linux Kernel architecture powering Android, each installed application is assigned a unique system User ID (UID). This directory is fortified by OS-level sandbox boundaries. No other application on your phone (including browsers, file managers, or third-party tools) can read, modify, or inspect the session keys or databases housed in this protected directory unless your device is rooted or compromised.

  • Volatile Caching & Fast Eviction: Temporary files such as voice messages, stickers, and image thumbnails are managed through an automated cache eviction policy. Users can purge this storage at any time via Settings → Data and Storage → Storage Usage → Clear Cache.
  • Secure Key Storage: Passcodes and local biometric encryption tokens are safeguarded using Android Keystore hardware-backed security modules.
E.1

Absolute Prohibitions: Anti-Surveillance & No Data Selling

We believe user privacy is an inalienable human right in the digital era. Therefore, NayaGram establishes categorical prohibitions against invasive digital surveillance:

  • No Commercial Monetization of Personal Data: We do not sell, rent, lease, trade, license, or monetize user data, chat histories, telephone numbers, or behavioral patterns under any circumstances.
  • Zero Content Inspection: We possess zero technical mechanisms to read, eavesdrop on, decrypt, or log text messages, voice calls, video meetings, secret notes, or attachments.
  • No Behavioral Fingerprinting: NayaGram contains no covert cross-app trackers, advertising IDs harvesting algorithms, or silent hardware fingerprinting scripts.
  • No Government Backdoors: There are no surveillance backdoors, secret decryption keys, or telemetry taps built into NayaGram.
F.1

Hardware & Operating System Permissions Breakdown

NayaGram requests only standard Android permissions strictly necessary to deliver modern messaging, voice calling, and media sharing. Each permission is requested dynamically at the precise moment of use:

Camera (āĻ•ā§āĻ¯āĻžāĻŽā§‡āĻ°āĻž)

Required exclusively when you initiate video calls, capture instant video notes, or take photos within the chat view. Never accessed in the background.

Microphone (āĻŽāĻžāĻ‡āĻ•ā§āĻ°ā§‹āĻĢā§‹āĻ¨)

Utilized solely for crystal-clear voice calls, sending recorded audio voice notes, and capturing sound during video recording.

Contacts (āĻ•āĻ¨ā§āĻŸāĻžāĻ•ā§āĻŸāĻ¸ - āĻāĻšā§āĻ›āĻŋāĻ•)

Optional permission. Allows synchronization of your address book with Telegram servers so you can discover which contacts already use Telegram.

Storage & Photos (āĻ¸ā§āĻŸā§‹āĻ°ā§‡āĻœ āĻ“ āĻĢāĻžāĻ‡āĻ˛)

Allows saving received documents and photos to your device gallery, or selecting media from your internal storage to share.

Notifications (āĻ¨ā§‹āĻŸāĻŋāĻĢāĻŋāĻ•ā§‡āĻļāĻ¨)

Delivers timely message alerts, incoming voice call banners, and background sync updates without keeping the screen active.

Location (āĻ˛ā§‹āĻ•ā§‡āĻļāĻ¨ - āĻŦā§āĻ¯āĻŦāĻšāĻžāĻ°āĻ•āĻžāĻ°ā§€ āĻ¨āĻŋāĻ°ā§āĻ­āĻ°)

Requested strictly when you deliberately tap "Share Live Location" or send a map pin. Never tracked silently in the background.

G.1

Advertising Policy & Google AdMob SDK Transparency

We are completely honest and upfront regarding our commercial architecture:

  • Current Operational Status: NO ACTIVE ADVERTISEMENTS. At present, NayaGram serves ZERO ads, zero interstitial video popups, and zero promotional banners during your chat interactions.
  • SDK Dormancy Disclosure: The Google Mobile Ads (AdMob) SDK dependency may exist in compiled application binaries for potential future operational sustainability. However, this SDK is currently disabled or maintained in a dormant non-tracking state.
  • Advance Notice Commitment: If non-intrusive advertisements are enabled in a future release, this Privacy Policy will be amended in advance, a clear announcement will be distributed in the app, and any advertising will strictly adhere to Google Play Developer Program policies without compromising chat confidentiality.
H.1

Account Deletion, Cloud Erasure & Local App Purge

You retain absolute sovereignty over your account existence and message history:

  • Direct Cloud Account Self-Destruction: You can permanently terminate your Telegram account and all cloud-stored chats, groups, channels, and contacts at any time through the official path:
    Settings → Privacy and Security → Delete My Account If Away For... (or via Telegram's official deactivation portal at my.telegram.org).
  • Immediate Local Wipe Upon Uninstall: Uninstalling NayaGram from your Android device causes the operating system to immediately destroy all local sandbox databases, encryption keys, and cache files stored under /data/data/org.nayagram.platform/.
  • Message Self-Destruct Timers: NayaGram honors all Telegram native self-destruct timers for media and messages in Secret Chats and standard private dialogues.
I.1

Children's Privacy Protection (COPPA & GDPR-K Compliance)

NayaGram is not directed towards, designed for, or intended to attract children under the age of 13 (or under 16 in the European Economic Area).

We do not knowingly collect or solicit personal information from minors. In accordance with Telegram's global Terms of Service, anyone below the minimum statutory age requirement in their jurisdiction is prohibited from registering an account.

J.1

Third-Party Components & Core System Dependencies

NayaGram integrates specific industry-standard open-source and OS-level components:

  • Telegram MTProto Native C++ Core: The low-level encryption and transport protocols are executed via high-performance native binaries built from Telegram's official source code.
  • WebRTC Media Engine (tgvoip): Peer-to-peer VoIP voice and video calls utilize WebRTC and Telegram's custom audio engine, ensuring crystal-clear audio with end-to-end cryptographic key verification.
  • Google Play Services (FCM Push): Firebase Cloud Messaging is utilized exclusively for wakeup pings so incoming messages wake your phone smoothly without depleting battery life.
K.1

Reproducible Builds, Verification & Auditability

Trust in security is built upon verifiable proof, not blind promises. We support reproducible builds to empower independent security researchers:

  • Public Git Repository: Anyone can inspect our exact commit history, diff files, and verify that no hidden telemetry or surveillance spyware exists in our source code: NayaGram Official GitHub Repository.
  • Independent Compilation: Developers can clone our repository and compile the APK directly using Android Studio and standard Gradle commands.
L.1

Security Vulnerability Disclosure & Official Inquiries

We welcome white-hat security researchers and community feedback. If you discover a potential vulnerability in our client application or wish to submit legal inquiries regarding this Privacy Policy:

Please reach our dedicated security desk at support.nayagram@gmail.com or message our verified Telegram staff account @NayaGramPro. We acknowledge security reports promptly within 48 business hours.

✓ Copied to clipboard!