LookOut Get started

Security

What the servers can and can't see

LookOut carries private things between two phones. Here is exactly how they are protected, and where the protection stops.

End-to-end encryption

"End-to-end" means the data is locked on the sending phone and only unlocked on the receiving phone. Servers in between only carry scrambled bytes. In LookOut this covers:

  • Moments: photos and doodles.
  • Answers to requests: the recent-calls list and requested photos.
  • Live camera frames: each frame is encrypted on its own.

Encryption is AES-256-GCM, which also detects tampering. Photos are shrunk (at most 1600 px, WebP or JPEG) and call lists compressed before they are encrypted.

Keys

  • Each phone makes its own key pair (elliptic curve P-256). The private key never leaves the phone; it is wrapped with a key from the Android Keystore, the phone's secure key storage.
  • The public keys are swapped through the database when you pair.
  • Both phones then work out the same shared key with ECDH and HKDF-SHA256. That shared key is never sent anywhere.

The crypto code has unit tests that check both phones derive the same key and that tampered data is rejected.

On-phone vault

Received moments are stored in LookOut's private app storage, encrypted again with the phone's Keystore key, so other apps can't read them. The server copy is deleted once both phones have it. Save to phone decrypts one photo into your gallery when you choose.

Access rules

Everything else (your status, places and requests) is stored in Google Cloud Firestore and protected by security rules: each document can only be read or written by the two accounts in that couple. The rules have their own automated tests.

This data is not end-to-end encrypted, because the server needs to read some of it (for example, to know who to send a ring to). That means Google, and the developer as owner of the Firebase project, could technically read battery, call state, location, places and app usage.

Servers in the middle

  • Google Firebase: sign-in, the database, and push messages (Firebase Cloud Messaging).
  • A Cloudflare Worker run by the developer: it checks your sign-in token, then sends push messages for rings and requests, relays live-camera frames (already encrypted), and serves app updates.

Updates only install if they are signed with the same key as the app you have; Android refuses anything else.

What is not done yet

  • LookOut has not had an independent security audit.
  • Status, places and requests are protected by access rules, not end-to-end encryption.
  • There is no key verification (like comparing safety numbers), so you rely on the database to hand over the right public key when you pair.
  • It runs on free Firebase and Cloudflare plans operated by one developer.
  • The APK download link is public. Anyone with it can install the app, but they can't see your data without being paired with you.