Google Play Developer Policy Compliant

Privacy Policy

Effective Date: September 24, 2026 | Version 1.0

1. Commitment to Absolute Privacy

OffMesh is developed with a strict Privacy by Default architecture. OffMesh operates as an opportunistic, decentralized mesh communication utility. We do not collect, track, sell, or monetize any personal information, behavioral metrics, or user telemetry.

2. Data Collection and Processing

Personal Identifiable Information (PII) Zero Collected

Phone Numbers & Email Addresses Not Required / Never Requested

Advertising IDs & Trackers Zero SDKs / Zero Tracking

Message Contents End-to-End Encrypted (Unreadable)

Cryptographic Keys Stored Exclusively On-Device

3. Operating System Permissions & Rationale

In accordance with Google Play's Permissions and APIs that Access Sensitive Information policies, OffMesh requests only the minimal permissions required to provide offline peer-to-peer radio communication:

Permission	API Level	Purpose & Compliance Guardrail
`BLUETOOTH_SCAN`	Android 12+ (API 31+)	Used strictly to discover nearby OffMesh peer nodes. Configured with `neverForLocation` flag. We never infer or record geographic location.
`BLUETOOTH_CONNECT`	Android 12+ (API 31+)	Used to establish direct peer RFCOMM/L2CAP channels to exchange encrypted message envelopes.
`BLUETOOTH_ADVERTISE`	Android 12+ (API 31+)	Broadcasts an ephemeral peer beacon containing only your random node identifier hash.
`NEARBY_WIFI_DEVICES`	Android 13+ (API 33+)	Used for high-speed Wi-Fi Direct peer-to-peer data links without internet connectivity.
`CAMERA`	Optional	Requested solely when the user chooses to scan an in-person contact's public QR code to verify identity fingerprints. Images never leave local memory.

4. End-to-End Cryptography and Store-and-Forward Relaying

All messages created in OffMesh are encrypted on the sender's device using ChaCha20-Poly1305 with keys derived from the X25519 Double Ratchet protocol.

Relay Privacy: When intermediate devices forward encrypted envelopes, they have zero access to the plaintext content, recipient metadata, or sender identity.
Zero Central Decryption: There are no master keys or backdoors. Only the recipient with the corresponding private key can decrypt the message.

5. Server Synchronization and Ephemeral Cache Retention

If a device connects to an optional OffMesh sync gateway when internet access is present:

The gateway only stores encrypted ciphertext blobs.
Retention Period: Blobs are subject to a strict 7-day Time-To-Live (TTL) cache, after which they are automatically permanently purged.
The server maintains zero user accounts, zero device identifiers, and zero persistent relational logs.

6. Data Deletion and Self-Service Wipe

You maintain 100% ownership and control over your data. Because OffMesh does not store personal data on central servers, wiping your local data completely erases your cryptographic presence.

To initiate an instant full data shred, open OffMesh -> Settings -> Data & Storage -> Wipe All Identity Keys & Local Data. For full instructions, visit our Data Deletion Policy.

7. Contact and Inquiries

For compliance, privacy inquiries, or security verification:

OffMesh Compliance Team

Email: privacy@offmesh.org

GitHub Security Advisory: github.com/Prince364133/offmesh/security