~/offline $ ssh anonymous @relay.offlineapp.org
Offline

No phone number. No cloud. No trace.

A messenger designed to leave nothing behind. End-to-end encrypted by default. No SIM required. No cloud backup. The server can't leak what it doesn't hold.

0
phone numbers
0
logs kept
X25519
encryption
OSS
relay source
✓ You're on the list. One email, only when it launches.

Private beta · iOS & Android · Nothing else stored.

scroll ↓

We can't leak what we don't have. That's the entire design.

[ 01 ]

No identity

No phone number. No email required to use. No real name. You generate a cryptographic ID on your device. That's your entire identity.

[ 02 ]

No metadata

The server logs no IP addresses, no timestamps, no who-talks-to-whom graphs. We can't hand over data we never wrote down.

[ 03 ]

No cloud

Messages live only on your devices. Lose your phone, lose your history. That's not a bug — it's the guarantee.

[ 04 ]

No persistence

Messages are deleted from the relay the moment they're delivered. The server is a mailbox, never an archive.

[ 05 ]

No tracking

No ads. No analytics. Not even anonymous telemetry. We don't want to know things about you.

[ 06 ]

No black box

The relay server code is open source. You can audit exactly what it does — and what it doesn't.

Simple crypto. No magic.

~/alice/send-to-bob.sh
alice $ offline generate-id generated X25519 keypair on device ID: of1_aC9Kq7xM...p4N   alice $ offline add bob_id exchanged prekeys with bob session established — verify fingerprint: f3:b2:9c:4a   alice $ offline send bob "signal's down — switching to this" encrypted with ChaCha20-Poly1305 relayed as ciphertext: 247 bytes ↳ server sees: "user X → user Y · blob" ↳ server does not see: contents, your IP, timestamps   # message delivered. relay deletes it. no copy anywhere except # alice's device and bob's device. that's the whole design.

What Offline protects you from. And what it doesn't.

✓ Offline protects against

  • ISP surveillance of your message contents
  • Government subpoenas for chat history (we have nothing to give)
  • Hackers breaching the relay server (they'd only get ciphertext)
  • SIM-card registries linking you to an identity
  • Cloud provider scanning your conversations
  • Metadata graphs showing who you talk to
  • Corporate advertisers profiling your behavior

✕ Offline cannot protect against

  • A compromised phone (keylogger, spyware, etc.)
  • Someone physically taking your unlocked device
  • The person you're chatting with screenshotting messages
  • Deep state-level adversaries with zero-day exploits
  • You being socially engineered into adding a fake contact
  • Loss of your device (no cloud = no recovery)
  • Traffic analysis by a global passive adversary

// Honesty matters more than marketing. Any messenger claiming total privacy is lying.
We can tell you exactly where our protection ends.

Side by side with everything else.

WhatsApp Signal Telegram Offline
End-to-end encrypted by default yes yes no yes
No phone number required no no no yes
No cloud backup at all no opt-in no yes
No metadata logging no partial no yes
Open source server no yes no yes
Owned by ad-driven corporation yes no no no
Works anonymously no no no yes

What's live. What's next.

✓ done · Q2 2026

Relay server — live

Go-based WebSocket relay. Runs on a single VPS. Handles E2E-encrypted ciphertext. Logs nothing. Deletes messages after delivery.

✓ done · Q2 2026

Landing & waitlist

What you're reading now. Warrant canary published monthly. No tracking. No cookies.

◉ in progress

Web app — /app

Fully in-browser messenger. Keys generated locally via Web Crypto API. Works on iPhone & Android as a PWA. No install required.

· next

Android beta

Native Android app. Google Play + direct APK. Push notifications via Signal-style sealed sender.

· later

iOS beta

Swift + CryptoKit. TestFlight first, App Store after review. Feature parity with Android.

· future

Independent audit

Third-party cryptographic review of relay + clients, published publicly. We want adversarial eyes.

Questions people ask before signing up.

Who is Offline for?

People who care more about privacy than convenience. Journalists protecting sources. Activists in countries where SIM cards are registered to the state. Anyone who thinks a chat app shouldn't require handing over their phone number, location, and social graph to a corporation in exchange for basic communication.

How is this different from Signal?

Signal is excellent — we use the same underlying encryption primitives (X25519 + ChaCha20-Poly1305). The difference: Signal requires a phone number tied to your real-world identity. Offline doesn't. You get a cryptographic ID generated on-device. No SIM. No phone bill. No metadata trail back to you.

Is it really free?

The basic messenger is free forever. Later, premium features (larger file transfers, multi-device sync, custom human-readable handles) may cost a small subscription. We will never run ads. We will never sell data. We have nothing to sell.

What if I lose my phone?

Your messages are gone. That's the tradeoff for having no cloud backup. If we can't read your messages, we can't restore them either. Your contacts can re-verify you with a new ID via safety-number comparison.

How do I add contacts without a phone number?

QR code, shared link, or typing someone's ID directly. The web app can generate a QR you scan in person. Your contact list lives only on your device.

Can I use it on multiple devices?

Not in the MVP. Multi-device is planned but requires careful key distribution to avoid becoming a security hole. We'd rather launch one device done right than three done poorly.

Who built this?

A small team with backgrounds in smart contract security and cryptography. We've written audit reports on DeFi protocols holding hundreds of millions in user funds. We take privacy seriously because we know exactly what it costs when it fails.

Is the code open source?

The relay server will be open source at launch. Clients (web / iOS / Android) will be open-sourced in phases as they stabilize. We believe you can't claim to protect privacy with closed-source code.

Why should I trust you?

You shouldn't. Trust the math. Trust the open-source code. Trust the warrant canary. We designed Offline so that trusting us isn't required — the server architecture genuinely cannot leak what it doesn't store.

Ready to chat without being watched?