Last updated November 20, 2026

Privacy Policy & Zero-Knowledge Disclosure

SquadAir (squadair) is designed so there are no user accounts, no cloud databases, and no unencrypted media servers to subpoena, leak, or monetize.

1. Zero Cookies, Zero Analytics, Zero Conversation Logs

SquadAir operates on three verifiable defaults:

  • Zero Cookies: squadair.app sets zero HTTP cookies, zero localStorage tracking identifiers, and zero third-party scripts.
  • Zero Analytics & Telemetry: Neither the desktop client nor this website ships crash telemetry, usage analytics, advertising SDKs, or device fingerprinting.
  • Zero Conversation Logs: Voice audio, screen streams, chat text, screenshots, and files are encrypted client-side with ChaCha20-Poly1305 and never decrypted or stored by any SquadAir server.

2. Data Stored Strictly on Your Local Device

SquadAir stores preferences, contacts, and recent room state solely inside your operating system's standard user application data directory. Configuration files are created atomically with restrictive user-only permissions (0600 on Unix).

Artifact Contents Retention
config.toml Nickname, local client_uuid, Base58 X25519 identity secret, audio/overlay settings, saved room URIs. Local only until deleted by user
friends.json Up to 256 trusted friend X25519 public keys, nicknames, and local timestamps. Local only until removed by user
Room chat history Up to 30 recent messages per joined room for local display and peer history sync. Capped at 30 messages per room
Inline & avatar cache Inline clipboard screenshots (<= 200 KB) and P2P custom avatars (128x128 JPEG, <= 64 KB). Avatars auto-pruned after 30 days

3. Ephemeral RAM Data on the Signaling Coordinator

To connect peers behind home routers and NATs, the public coordinator rv.squadair.app:3478 (or your own self-hosted squad-rendezvous binary) holds strictly ephemeral signaling coordinates in volatile RAM with zero disk persistence and zero database backing:

  • Friend Presence Ping (15 s TTL): Stores your public socket IP:port, X25519 public key, display nickname, and boolean in_room state so saved friends can see when you are online. Evicted automatically if heartbeats stop for 15 seconds.
  • Active Room Registration (6 s TTL): Holds an opaque 16-byte room_id, session client_uuid, socket IP:port, and local LAN hints to facilitate UDP hole punching. Automatically reaped after 6 seconds of inactivity.
  • 6-Digit Voice Codes (600 s TTL): Maps an ephemeral 6-digit code to the room host's socket address and SPAKE2 challenge routing. Room decryption secrets never leave client memory.
  • Rate-Limiting Buckets (60 s TTL): Temporary per-IP token buckets and failed short-code counters in memory to mitigate UDP flooding and brute-force guessing.

When two peers cannot punch directly or bridge via a teammate (Tier 1 or Tier 2) and fall back to the optional Tier 3 server relay, the coordinator forwards only encrypted voice and text datagrams (<= 320 bytes) without possessing the room key needed to decrypt them.

4. Website Hosting & Desktop Auto-Updater

This documentation site is served as static files over Cloudflare Pages with zero cookies and zero analytics scripts. Standard edge infrastructure providers process transient HTTP connection metadata (such as IP address and TLS handshake) solely to route HTTPS responses and defend against network abuse.

When you check for updates inside the SquadAir client, the updater connects directly to GitHub Releases (https://github.com/alivergg/squad-air/releases/latest) to compare release tags and verify installer checksums against SHA256SUMS.txt.

5. Contact

For privacy questions or questions about self-hosting squad-rendezvous, contact support@squadair.app or review the open-source code at github.com/alivergg/squad-air.