DDM Public Hub Relay Agreement
Last updated: June 9, 2026
This agreement covers current and future public hub relay usage in DDM.
What a hub is
A DDM hub is any device or relay node that temporarily holds encrypted message envelopes so another DDM user can receive them later. Hubs are like BBM-era relay points: they move sealed packets, not conversations.
Zero-content access
Hubs — including your device when hub mode is enabled — may see only:
- Recipient DDM ID
- Sender hub ID (if provided)
- Envelope size and expiry
- Hop count
- Encrypted ciphertext (
ciphertext_b64)
Hubs may never access:
- Message text or attachments in readable form
- Private keys or decryption material
- Your contact list, notes, stories, or app-lock code
- Microphone recordings or camera captures
Public hub usage
DDM may allow any user to send encrypted traffic through any available hub. This is intentional for network reach before mesh density is high. Public hubs exist only for encrypted transit and delivery.
Your responsibilities
- Keep end-to-end encryption enabled for private lanes
- Do not send unlawful content through the network
- Accept reasonable battery/data use if you enable always-on hub mode
- You may disable hub mode at any time
Future usage
Future DDM and DDMi releases may add additional relay lanes (LAN, radio, satellite gateway, etc.). Those lanes must follow the same rule: routing only, no hub content access.
Retention
Relay envelopes expire automatically (default 72 hours). Delivered or expired envelopes are removed from relay storage.