CipherMeet Sovereign Emblem
CipherMeet Sovereign Comms
Contact

Privacy Policy

LAST UPDATED: SEPTEMBER 18, 2026 • CIPHERMEET.APP

1. Our Privacy Tenet

At ciphermeet.app, our philosophy is simple: What we cannot see, we cannot store, monetize, or surrender.

Unlike legacy video and voice platforms that inspect audio for advertising, transcribe conversations for AI training, or retain recordings on central cloud servers, our architecture is mathematically engineered to be zero-knowledge.

2. What We Never Collect

  • Zero Voice or Video Media: Audio and video frames are encrypted client-side using IETF SFrame (AES-128-GCM). The server acts purely as a blind packet forwarder and cannot decrypt them.
  • Zero Chat or Transcripts: No chat messages or transcription logs are recorded or stored on any server.
  • Zero Cryptographic Keys: Encryption keys are distributed out-of-band (via URL hash fragments or peer verification) and exist strictly in volatile browser memory.
  • Zero Attendee & Invitee Profiles: Joining a meeting or tactical squad requires zero account creation, zero passwords, and zero profiling. Attendees participate with 100% ephemeral anonymity.

3. Cloud Infrastructure Allocation & FailSafe Studio Authentication

To prevent denial-of-service abuse and protect Google-hosted Selective Forwarding Unit (SFU) cloud compute resources, users who wish to initiate and host new sessions via the web app authenticate with a free FailSafe Studio account.

  • Decoupled from Cryptographic Keys: Your FailSafe Studio account credentials are used exclusively to authorize cloud signaling compute. Your meeting's 256-bit room master keys are generated locally in browser WebCrypto and are never linked to or stored within your FailSafe Studio account profile.
  • Attendee Exemption: Anyone joining an existing room via an invite link or short code joins completely unauthenticated. No FailSafe account or email is ever requested from attendees.
  • Native Desktop App Exemption: Users running the native CipherMeet or CipherWire desktop clients (Windows) bypass web cloud authentication directly.

4. Minimal Ephemeral Routing Data

To establish a WebRTC connection or relay encrypted packets through our Selective Forwarding Unit (SFU), our signaling servers temporarily process:

  • Ephemeral IP addresses and network port numbers required to route encrypted UDP packets between attendees.
  • Room identifier tokens to correlate participants into the requested virtual meeting room.

This routing state is held strictly in volatile server RAM and is permanently purged the moment a participant disconnects or a meeting terminates.

5. Local Storage & Session Management

ciphermeet.app does not use third-party advertising cookies, Google Analytics, tracking pixels, or fingerprinting scripts. We utilize local browser storage (localStorage) strictly for:

  • Remembering your visual theme preference (Dark Mode or Light Mode).
  • Preserving the active FailSafe Studio session token for web session hosts to authorize room creation requests across visits.

6. CipherWire Mobile Application (Android) Disclosures

This section specifically applies to users of the CipherWire Mobile Application for Android (Application Title: CipherWire, Application ID: com.cipherwire.mobile).

A. Device Hardware Permissions & Sensitive Capabilities

CipherWire requests only the minimum hardware permissions required for encrypted tactical squad communications:

  • Camera (android.permission.CAMERA): Camera access is used solely on-device to scan encrypted QR code squad invitations and peer public keys. The camera preview stream is processed in volatile memory in real time exclusively to decode the QR payload. CipherWire does not photograph, capture, record, save to persistent storage, or transmit any images or video frames off the device.
  • Microphone (android.permission.RECORD_AUDIO) & Foreground Audio Service (android.permission.FOREGROUND_SERVICE_MICROPHONE): Microphone access is used exclusively for live Push-to-Talk (PTT) and Voice Activity Detection (VAD) audio streaming in tactical voice channels. Voice audio is end-to-end encrypted directly on the device using WebRTC and SFrame (AES-128-GCM) prior to transmission. Voice audio is never recorded, transcribed, sampled, or stored on any server or local file. The foreground service is strictly utilized to maintain voice channel continuity, display a persistent status notification, and allow Push-to-Talk transmission while the application is in the background or while the device screen is locked.
  • Bluetooth & Audio Routing (android.permission.BLUETOOTH_CONNECT, android.permission.MODIFY_AUDIO_SETTINGS): Used solely to detect connected audio peripherals (such as tactical Bluetooth headsets, bone-conduction earpieces, or wired PTT accessories) and route radio audio to the operator's designated device.
  • Haptics & System Wakelocks (android.permission.VIBRATE, android.permission.WAKE_LOCK): Used to provide tactical haptic feedback on PTT button engagement and prevent the device CPU from sleeping during an active encrypted radio transmission.

B. Accountless Architecture, Data Retention & Deletion

No Account Registration Required: CipherWire does not require user accounts, email addresses, phone numbers, usernames, or passwords. Your identity consists of a sovereign cryptographic key pair generated locally on your device's hardware keystore.

Zero Remote Data Retention: CipherWire central infrastructure acts exclusively as an encrypted Selective Forwarding Unit (SFU). Packets are forwarded ephemerally to authorized squad peers and are never archived. Text messages exchanged within CipherWire are ephemeral and governed by user-configurable burn timers (10 seconds to 24 hours), causing messages to be permanently purged from volatile memory upon expiration.

Autonomous Data Deletion: Because CipherWire maintains no central database of users, contacts, messages, or identities, operators have unilateral control over their data at all times:

  • Local In-App Purge: Operators can delete squads, purge local conversation history, or regenerate key pairs directly within the application settings.
  • Complete Device Wipe: Uninstalling the application or selecting Settings → Apps → CipherWire → Storage → Clear Data on Android immediately and irreversibly destroys all local cryptographic keys, squad configurations, and cached messages.
  • Inquiries: Since no user data is stored on remote servers, no remote deletion requests are required; however, users may contact admin@ciphermeet.app with any privacy verification requests.

C. Zero Third-Party Advertising & Tracking

CipherWire Mobile contains zero advertising SDKs, zero third-party analytics libraries, zero tracking pixels, and zero crash telemetric harvesters. The application does not collect, read, or transmit Android Advertising IDs (AAID), IMEI numbers, hardware serials, device fingerprints, or GPS location data.

D. Children's Privacy (COPPA Compliance)

CipherWire Mobile is designed and intended for tactical operators, team coordinators, and general adult audiences aged 18 and older (and at minimum 13 years of age). We do not knowingly collect, solicit, or maintain personal information from children under the age of 13.

7. Discord Bridge Integration Privacy

When using the CipherMeet to Discord Bridge, Discord channel commands (such as /ciphermeet start) transmit only the public meeting topic and target channel ID to post the announcement embed. The audio and video sessions themselves take place entirely on SFrame-encrypted CipherMeet infrastructure; Discord servers never receive voice streams or decryption keys.

8. Security Inquiries & Contact

If you have questions regarding our cryptographic architecture, mobile permissions, or privacy practices, reach our engineering team directly at admin@ciphermeet.app.