JC!IJB! LogoJC!IJB!
Menu
JC!IJB! / SECURE COMMUNICATIONS

PRIVATE COMMUNICATIONS. CUSTOMER CONTROL.

JC!IJB! Secure Channel is a self-hosted communications platform that lets visitors open and revisit private two-way conversations without creating an account or providing an email address.

Available in current prototype

A distinct product from the JC!IJB! sovereign cyber-defence appliance. No data channel exists between the two products.

01

Self-hosted by the customer

02

Anonymous-to-the-recipient enquiries

03

Controlled access with a private recovery credential

A locally deployed widget and customer-operated backend. No vendor telemetry. No mandatory JC!IJB! cloud connection.

Visitor experience

Open. Write. Keep the key. Return.

A real persistent conversation, confirmed only after it is stored.

  1. OpenThe visitor selects OPEN PRIVATE CHANNEL on the customer's website. The panel names the customer as the organisation they are writing to, and explains that no personal details are needed.
  2. WriteThe visitor chooses a topic and writes. The customer's server validates the message and stores the conversation before anything is confirmed.
  3. Keep the keyOnly after the message is stored, the server issues a private access key — at least 128 bits from a server-side cryptographic random source — shown once, with copy and recovery-card options. The server keeps only a verifier, never the key.
  4. ReturnFrom any browser, the visitor enters the channel reference and private access key to read the reply. A short-lived, secure, HttpOnly session is created; the key never appears in a URL, log or analytics event.
  5. AnswerCustomer staff reply from their own inbox, behind strong authentication, with roles, audit and site-level isolation.
Architecture

Operated entirely by the customer

JC!IJB! Secure Channel deployment architectureA visitor browser talks over TLS to the customer website, whose widget is bundled locally, and to the customer-hosted Secure Channel service with a visitor API, an operator API, encrypted storage and an audit log. Customer staff answer from their own inbox. The JC!IJB! vendor has no runtime connection; the customer administrator downloads signed releases.CUSTOMER-OPERATEDVisitor browserno account, no emailCustomer websitewidget bundled locallySecure Channel serviceVisitor APIOperator API (MFA, roles)Encrypted storageAudit logStaff inboxsite-isolatedJC!IJB! vendorno runtime connectionSigned releasesfetched by the admin
Every component inside the dashed boundary runs on the customer's infrastructure. The vendor has no runtime connection.
Editions

Packaging

Available in current prototype

Site Edition

One website, one inbox.

Available in current prototype

Organisation Edition

Many websites of one organisation, with site-isolated inboxes and an optional combined view.

Available in current prototype

Enterprise Edition

Self-hosted, offline-installable, for environments with their own security requirements.

Deployment · Security model

SOVEREIGN BY DESIGN.

Discuss a Secure Channel pilot

For organisations that want private two-way enquiries without accounts, operated entirely in-house.

Request a Technical Briefing View Sovereign Architecture