Nothing about you ever leaves this room.

The list of "no".

None of the following exist anywhere in CodeB Conference. No exceptions, no "but only if you opt in", no asterisks.

• No third-party analytics — no Matomo, no Plausible, no Mixpanel, no Amplitude, no Segment, no first-party analytics either.
• No advertising trackers — no ad-network pixels of any kind. No retargeting tags, no audience pixels.
• No cookies — we don't set any cookies, first-party or otherwise. The app uses localStorage for your preferences only, and even that stays on your device.
• No session recording, heatmaps or scroll tracking — no FullStory, Hotjar, LogRocket, Mouseflow or similar.
• No A/B testing platforms — no Optimizely, no LaunchDarkly, no feature-flag service of any kind.
• No error reporting to third parties — no Sentry, no Bugsnag, no Datadog RUM. Errors stay in your browser console.
• No CDN dependencies in the call path — the QR code generator, the WebRTC client and the signaling endpoint are all served from phone.codeb.io.
• No mandatory third-party logins — no social-account sign-in, no Microsoft account, no SSO required to join a room. You enter a room code; you're in.
• No identity providers in the middle — your name is whatever you type; we don't verify it against an external directory.
• No meeting persistence on any server — recordings exist only on the recorder's machine; chat lives only in browser memory and disappears when the tab closes.
• No telemetry from the app itself — the running browser code does not send "the user clicked X" events to any endpoint, period.
• No ad-supported tier — there are no ads on any page, ever.

The list of "yes — briefly".

The list of things that actually happen is short enough to fit on this page.

• The IIS server keeps a short in-memory list of "who is in which room right now" so it can route signaling between you. When the last person leaves the room, the entry is gone. Nothing is written to disk.
• Standard IIS access logs record HTTP requests (URL, status code, IP, user agent) the same way every web server does. Most operators rotate these out after 14 days. We do not parse them.
• Your browser stores a handful of personal-preference keys in localStorage: display name, selected camera/microphone, mirror toggle, push-to-talk, auto-spotlight, background-blur, join-muted and join-camera-off. Clear your browser data and they're gone.
• For meetings that require it, an HMAC-SHA1 TURN credential is generated for your browser at room-join time. The credential expires after one hour. It does not contain your name, email or any persistent identifier.

Where bytes leave our network.

Three external hosts may be contacted by the browser, depending on which features you use. None of them ever see your video, audio, chat or files.

For an air-gap install, the WebRTC signaling, TURN relay, JS, CSS, fonts and ML model can all live on the customer's own LAN. The build supports it; the recipe is documented in the deployment README.

Why the colour scheme looks like a 1980s terminal.

The accent colour you see throughout CodeB Conference — that warm #f5a524 against the deep #0a0d12 background — is a deliberate tribute to amber-phosphor CRT monitors.

For roughly fifteen years, from the late 1970s into the early 1990s, the people who ran the world's most consequential computers stared at amber screens. The IBM 5151, the Wyse 50, terminals on hospital nursing stations, manufacturing line PLCs, air-traffic-control consoles, defence command terminals — they all glowed in this same warm yellow at around 580 nm wavelength.

The reason wasn't aesthetic. Amber phosphor (P3, later P134) was chosen because it sits in the sweet spot of the human eye's photopic sensitivity curve. Operators staring at a screen for ten or twelve hours — radiologists, air-traffic controllers, machine-tool programmers — experienced measurably less eye fatigue with amber than with the otherwise-common green P1 phosphor, and significantly less than with the white CRTs that became fashionable later. Amber was the colour of tools for people whose work mattered.

That's the lineage we wanted CodeB to invoke. A serious tool for people doing serious work — clinicians, engineers, factory operators, public servants, defence supply chains — the same people CodeB Identity Solutions has served for two decades. The codeb.io design language uses amber the way those terminals did: high signal, no decoration. There is one accent colour because the work is what matters; the chrome shouldn't compete with it.

(And there's a small practical bonus: against a dark background, amber has the highest perceptual contrast of any single accent colour, and it remains distinguishable to people with the most common forms of red-green colour vision deficiency. The 1980s engineers picked it for ergonomic reasons; we picked it for the same ones plus a bit of historical respect.)

The promise written down.

If any of the items in section 01 ("things we do not do") ever stops being true, this page changes before the change ships. We won't roll trackers in quietly. We won't bury new analytics three menus deep.

The source code for CodeB Conference lives on your own IIS server. Every JavaScript file, every C# handler and the entire TURN service is open to inspection by anyone in your organisation. There is no obfuscation, no minification step that hides logic, and no compiled binary that contains anything not visible in the source.

If you spot something in the running app that contradicts this manifesto, please write to info@codeb.ioCall. A real person reads that inbox — or answers that phone.