lossless_protocols
LP-02 · icon: final at launch
◌ in development · not in app stores · no date yet LP-02 · location domain · proof two

locate. Location sharing the server cannot watch.

Family location sharing is the harder problem: it needs a server. Most apps solved that by letting the server see everything, and some then sold what it saw. locate solves it by building the server blind. End-to-end encrypted. The relay forwards packets it cannot read.

Signal path

The relay stores ciphertext. It reads none of it.

locate: signal path Your phone encrypts your location, sends ciphertext through a blind relay that cannot decrypt it, and your family's phone decrypts it. Plaintext never leaves your devices. ciphertext ciphertext your phone encrypts blind relay cannot decrypt family's phone decrypts plaintext never leaves this phone stores ciphertext, reads nothing keys exist only on your devices

what we store: ciphertext. what we can read: nothing.

The idea

Why this is proof two.

zero proved the principle where no server is needed. locate proves it where one is. The industry position says location sharing requires a company that can see the locations. It does not. It requires a company that can move them. Encryption happens on your phone, decryption on your family's phones, and the keys never touch us. locate is designed so that if our relay were ever seized, subpoenaed, or sold, its contents would be the same to the new owner as they are to us: noise.

Specification · partial, honest

The datasheet so far.

Part
LP-02
Status
In development. Not in any app store. Where it stands
Encryption
End-to-end
Content the relay can read
0
What the relay can see
Network metadata. Listed below
Accounts
No identity beyond your keys
Verify
Whitepaper and independent audit. Not published yet
Passes R1R2 pendingR3R4
Noise floor · requirement R4

What the relay can see.

"Cannot read" is about content: where you are, who is in your circle, what anything says. A relay still has to move the packets, and moving packets shows it things. This is the list, by design. The whitepaper will carry the final one.

Status · as of 2026-11-15

Where it stands.

When it exists, it will be here, with the whitepaper and the audit report to check it against. Back to the protocol.