Locked‑down OS
Appliance-like setup that boots straight into OTPhone. Fewer background services. Less clutter. Lower risk.
Privacy-first phone • Locked-down Linux • End‑to‑end encrypted
A phone built for private messaging.
OTPhone is a locked‑down Linux phone designed for privacy‑conscious communication. Choose between modern AES end‑to‑end encryption, server‑assisted OTP, or true One‑Time Pad mode shared in person.
2
Security modes
E2EE
Server can’t read AES/OTP messages
Linux
Auditable, minimal, locked‑down
Designed for privacy‑conscious people
A minimal, locked‑down device and a simple experience: messaging first, attack surface last.
Central relay, optional trust
A relay server forwards encrypted messages and helps with delivery when you’re offline. For AES and OTP modes, it can’t read your content.
Modes per conversation
Use AES for everyday secure chat, or true OTP for maximum confidentiality when you can exchange pads in person.
Pad management
Clear indicators for pad health, offsets, and verification status. Built to avoid accidental reuse.
Identity verification
Compare fingerprints in person before sensitive chats. Helps prevent impersonation and key substitution.
Privacy-first signup
Register interest with an email address only. We’ll never sell your data, just keep you updated.
Two security modes
Pick the right tool for the moment from convenient to extreme.
Mode 1
AES (standard E2EE)
End‑to‑end encrypted messaging with modern authenticated encryption. Best for day‑to‑day private chat.
- Server relays ciphertext only
- Integrity built in (anti‑tamper)
- Fast and low overhead
Mode 2
True OTP (in‑person exchange)
Exchange pads in person (Bluetooth file share) and use one‑time pad encryption. Maximum confidentiality when used correctly.
- No keys or pads on the server
- Ideal for high‑sensitivity chats
- Requires disciplined pad handling
Security note
OTPhone is designed to minimise risk, but no system can protect against a fully compromised device. For true OTP, security depends on correct in-person pad exchange and strict one-time use. Keep devices updated and verify identities for sensitive use.
How it works
Simple flow, clear trust boundaries.
1
Provision
Device generates its identity keys locally and registers a public identity with the relay.
2
Connect
Add a contact using an ID or QR and verify fingerprints for high‑trust chats.
3
Choose a mode
AES for everyday E2EE, or OTP for in-person pad exchange.
4
Message
The relay forwards ciphertext. The device encrypts/decrypts locally and manages pad state safely.
What the relay sees
Minimal routing metadata to deliver messages.
- Sender & recipient IDs
- Timestamps & message sizes
- Encrypted payload blobs
What stays on your phone
All cryptographic secrets and pad material.
- Private keys
- Session state
- OTP/OTP pads & offsets
Register your interest
Get launch updates. No spam. Unsubscribe any time.
FAQ
Quick answers for privacy-first buyers.
Is OTPhone an app or a phone?
OTPhone is a phone-first product: a locked-down Linux handset that boots into a dedicated messaging experience. A central relay helps with delivery and contact discovery.
Can the server read my messages?
In AES and true OTP modes, the server relays encrypted data and is not intended to have message plaintext. OTPhone supports two modes: AES end-to-end encryption for everyday use, and true one-time pad encryption when pads are exchanged in person.
Why three modes?
Different situations need different trade-offs. AES offers convenience and strong end-to-end encryption. True OTP is for maximum confidentiality when you can exchange pads in person.
Will it work without internet?
Messaging to other devices generally needs a network path. The relay supports store-and-forward when devices are offline. True OTP pad exchange can be done locally in person.
What data do you collect for interest signup?
Email is required to send updates. Everything else is optional. You can request deletion at any time.