Back to all guides & notes
2026-10-10•5 min read•Security & Systems Team

Why We Built ApnaSandesh Without android.permission.INTERNET

An engineering manifesto on radical privacy by design. Why omitting network permissions is the only verifiable guarantee against small business customer data leakage.

#Architecture#Security#Privacy#Android

Privacy Promises Are Cheap. Architecture Is Absolute.

Almost every SaaS marketing platform advertises that they "value your privacy" and "encrypt your data in transit". Yet every week, another cloud database misconfiguration exposes millions of phone numbers, addresses, and purchase records to the public internet.

When we designed ApnaSandesh for local retailers, doctors, tailors, and auto mechanics, we decided that legal promises in a 40-page terms of service were insufficient. We wanted a product where privacy could be mathematically and cryptographically verified by anyone with basic Android developer tools.

That is why ApnaSandesh contains zero lines of networking code and does not even request android.permission.INTERNET.


What Android's INTERNET Permission Really Means

On the Android operating system, an app cannot open a TCP/UDP socket, resolve a DNS query, or connect to any web address unless it explicitly declares:

```xml

```

in its compiled AndroidManifest.xml file.

Because ApnaSandesh completely omits this declaration:

  1. The Operating System Enforces the Block: Even if a rogue library or dependency attempted to transmit data, the Linux kernel and Android runtime would immediately reject the socket creation with a SecurityException.
  2. Zero Analytics or Tracking SDKs: We cannot include Google Analytics, Facebook Pixel, Mixpanel, or advertising trackers, because none of them can phone home.
  3. No Account Servers: There are no passwords to hack, no remote user accounts to breach, and no centralized databases to leak.

What About Customer Backups?

Because ApnaSandesh stores customer records in a local SQLite database using Android's Room persistence library (/data/data/com.apnasandesh.app/), we also set:

```xml

android:allowBackup="false"

```

This prevents Google Cloud's automated device backup from quietly copying your customer address book to unencrypted remote cloud drives without your knowledge.

Instead, ApnaSandesh puts data sovereignty entirely in your hands: you can export your verified customer directory and campaign logs to a clean CSV file anytime using the native Android Storage Access Framework (SAF).

You own your phone. You own your SIM. You own your customer relationships.

Download ApnaSandesh on Google Play

Start communicating directly from your Android phone without cloud servers.

View on Google Play