Whispr Privacy Policy

Whispr is written and maintained by one developer in Würzburg, Germany, publishing under the name PointBreakLab (pointbreaklab.com). The operator is the data controller for the purposes of applicable privacy law (GDPR / DSGVO). Contact: mail.roshankumargupta@gmail.com

We collect nothing. Whispr has no registration step and no backend to register against. The build carries no analytics SDK, and the app never opens a connection to a PointBreakLab server.

Messages travel directly between devices over three channels: • Local Wi-Fi (LAN): direct HTTP between devices on the same network, with every message wrapped in ECIES application-layer encryption so contents are invisible to everything else on that network. • Bluetooth LE mesh: multi-hop relay between nearby devices for offline messaging. Payloads are end-to-end encrypted before entering the mesh. This is the least dependable of the three: through walls, with people moving, a hop can simply fail. • Tor hidden services: over the internet via the Tor anonymity network. Your IP address is not revealed to your contact. All three channels apply end-to-end encryption using the Signal Protocol (X3DH key agreement + Double Ratchet algorithm) before any data leaves your device. PointBreakLab cannot decrypt your messages even if compelled by law.

All app data is stored exclusively on your device: • Messages, contacts, and settings are stored in an SQLite database encrypted with SQLCipher (AES-256-CBC full-file encryption) on Android and iOS. • Cryptographic private keys are stored in your device's secure hardware enclave: Android Keystore on Android, iOS Keychain on iPhone. • The database encryption key is derived from your password using PBKDF2-SHA512 (200,000 iterations) and is never stored in plaintext. • Whispr does not use iCloud, Google Drive, or any cloud backup for message data. If you use the built-in encrypted backup feature, the backup file is saved to your local device storage, and you pick the folder.

Whispr carries no ad SDK and no social-login button. The only third-party component that may contact an external server is the embedded Tor daemon, which connects to the Tor network for routing, not to any PointBreakLab server. The Tor Project's privacy policy applies to that connection (torproject.org). The QR-code scanning library (Google ML Kit via mobile_scanner) includes Firebase Transport Runtime as a transitive dependency. This component is bundled but does not transmit data; it is used only for local barcode detection. No Firebase project is configured in Whispr. The runtime is there because it arrives with ML Kit.

Whispr requests the following device permissions, for the reasons given below. The battery-optimisation exemption needs the most justification: Android throttles the Tor service as soon as the screen goes off, and Whispr has no server to hold a message in the meantime.

Everything lives on your device, so you delete it yourself: • Uninstalling the app removes all stored data. • The "Data Burn" feature (Settings → Security → Panic Button) performs a 3-pass cryptographic wipe: the database encryption key is destroyed first (making all stored data permanently unreadable), all table rows are deleted, and the database file is overwritten three times before unlinking. On flash storage the overwrite is the weakest of those three steps; destroying the key is what actually makes the data unreadable. • Disappearing messages are automatically deleted from your device after the timer you set expires. There is no data stored with PointBreakLab to delete.

Whispr is not directed at children under 13 (or under 16 in the European Economic Area). We do not knowingly collect information from children. Because Whispr collects no data from any user, no special handling of children's data is required.

Under GDPR, CCPA, and similar laws you have rights including access, rectification, erasure, and portability of your personal data. PointBreakLab holds no personal data about you, so there is nothing on this end to access, correct, export, or delete. All such data is in the encrypted database on your device, where you can access it directly. If you have questions, contact us at mail.roshankumargupta@gmail.com.

• End-to-end encryption: X3DH + Double Ratchet (Signal Protocol), AES-256-GCM per message. • At-rest encryption: SQLCipher AES-256 full-database encryption on mobile. • Key protection: private keys stored in Android Keystore / iOS Keychain with hardware-backed protection. • Transport: ECIES application-layer encryption on LAN; Tor hidden services for internet transport; BLE mesh, multi-hop, for offline relay. No security system is perfect. Whispr is provided as-is without warranty. See the in-app Security Guide for best practices.

This document changes only when a new build of the app ships, because nothing can push it out on its own. The copy inside Whispr and the copy at pointbreaklab.com are edited together. The date at the top of this document reflects the most recent revision.

Questions about this Privacy Policy: PointBreakLab mail.roshankumargupta@gmail.com pointbreaklab.com