Private by design

The intended production architecture is end-to-end encrypted so that room content can be read only on authorised members' devices.

This prototype demonstrates the intended experience. Its encryption architecture has not yet been implemented or independently audited. Do not put anything sensitive into it.

Three separated layers

Layer 1

The room

People talk, ask, decide and plan privately.

Layer 2

One

The user's own device helps reveal what matters.

Layer 3

Permission gateway

Only an explicitly approved requirement can connect to an outside service.

The conversation stays. The intention can travel — with permission.

  room  ──▶  permission gateway  ──▶  minimum requirements
   │                                        │
   │                                        ▼
   │                        maps · calendar · tasks · booking
   ▼                                        │
 conversation never leaves  ◀── confirmed outcome returns

What we will not say

No padlock badges on prototype messages
No "military-grade encryption", "unhackable" or "zero knowledge"
No claim that Signal Protocol or MLS is implemented
No claim of independent audit

Secure group messaging needs device identity, key rotation, forward secrecy, multi-device support, lost-device recovery, encrypted attachments and backups, key verification and independent review. That is specialist cryptographic engineering using a recognised, maintained implementation — never an invented protocol.

Message storage today

Private development beta · not yet end-to-end encrypted

Sign-in and database permissions control access. They are not encryption: an authorised operator could read stored content. Plaintext room storage must be replaced with a specialist-designed, independently reviewed architecture before general users are invited.

From agreement to real life

A confirmed room outcome could — with permission — become:

A place in maps
An event in a calendar
A task
A journey
A reservation
A payment request
A shared list
A reminder

No partnerships exist. Every external action must state:

What will be shared
With whom
For what purpose
For how long
Who approved it
What returns to the room

Scope

Now

Working in this prototype.

Talk
Ask
Decide
Plan
Do
Complete a room
Attention controls
Installable app experience

Specialist cryptographic engineering. Not started.

Specialist-designed encryption
Device verification
Encrypted attachments
Multi-device keys

Later

Interactive concept demonstrations only.

On-device interpretation
Recommendations
Maps and calendar
Bookings
Payments
Third-party platform

Privacy centre