Security
Data flow
Exactly what travels where, for a security review.
Files and workspaces
Datasets are read in the browser from what your page provides: arrays, text, File objects or folders the user picks. Workspace JSON goes wherever you send it from engine.io exports and comes back through engine.io imports. The SDK makes no network requests with this data.
Live streams
| Party | Sees |
|---|---|
| Publisher | Plaintext samples and the password (it encrypts). |
| Kymoscope backend | Stream registry rows: name, owner, salt, key check. No samples, no key. |
| Kymoscope relay | Encrypted frames and a short-lived credential per connection. No key. It enforces rate and connection limits. |
| Viewer’s browser | The password (typed by the user), the derived key, decrypted samples. |
| Your backend | Your API key, and whatever authorisation you apply before minting tickets. |
Third parties
- None. Every file the SDK loads, DuckDB-WASM included, is served from your origin.
- No analytics, telemetry or license call-home.
Related
See Watch tickets and Licensing.