Secure Channel · security model
Accurate claims, conservative cryptography.
A private access key is a bearer credential, not an encryption key. Transport and storage are encrypted, and the product never calls that end-to-end encryption.
| Area | Design |
|---|---|
| Transport | TLS between the visitor's browser and the customer's server. Storage encrypted at rest with protected backup keys. This is not end-to-end encryption, and it is never described as such. |
| Access credential | A bearer credential of at least 128 bits (target 256) from a server-side CSPRNG. Stored only as a verifier. Throttled per channel, revocable, rotatable. |
| Sessions | Short-lived, Secure, HttpOnly, SameSite cookies after key proof. Credentials never in URLs, localStorage, referrers, analytics, logs or screenshots. |
| Isolation | Separate data boundaries per site; one compromised site must not expose another. Server-side authorisation on every request — browser restrictions are not a substitute. |
| Abuse resistance | Schema validation, output encoding, quotas, rate limits and enumeration resistance, without invasive fingerprinting. |
| No vendor path | No runtime request from a customer deployment to jcijb.com. Assets are bundled locally. Updates are signed packages the customer's administrator installs. |
Commitments
What Secure Channel will never claim
- No promise of absolute anonymity against network or server operators.
- No end-to-end encryption label on transport and storage encryption.
- No identification of visitors from network addresses, fingerprints or enrichment.
- No confirmation shown to a visitor until the message is stored.
Every release is accepted against: a genuine persisted conversation and operator reply without identity; recovery from another browser; no credential or message in URLs, referrers, logs or analytics; cross-tenant and object-level authorisation tests passing; strong staff authentication; backups and restore verified; accessible on mobile, desktop, keyboard and screen reader.
SOVEREIGN BY DESIGN.
Discuss a Secure Channel pilot
Tell us what you need to protect. A briefing is an engineering conversation; it never needs your credentials, network inventories or logs.