Contextator

Closing the Encrypted Browser Loop

Pairing, encrypted relay envelopes, phone-side review, and safe field insertion connected the separate prototypes into one approval loop.

By 24 May 2026, Contextator's separate prototypes had been connected into an integration-alpha loop. A Chrome extension could begin pairing, an iPhone could approve the pairing, and the two clients could exchange encrypted request and response envelopes through a relay.

The product boundary mattered as much as the transport. The browser did not receive the vault. It sent a request for a persona package. The phone generated that package from verified local context, displayed the exact outgoing payload and its included or excluded items, and required device authentication before approval. The extension could then insert approved text into a focused field without submitting the page.

The relay was designed as a temporary courier. It handled pairing and message availability while the client endpoints performed X25519 key agreement, HKDF-SHA256 key derivation, and AES-GCM encryption. Audit entries on the phone stored sharing metadata instead of the payload.

The milestone closed the main protocol loop in code and automated tests. The repository was explicit that this did not establish beta readiness: the physical Chrome and iPhone interface path still needed to be run and recorded.

← Back to Contextator