Session Management
netbobr runs entirely in your browser and is ephemeral by default - nothing is stored in localStorage, sessionStorage, or cookies, and no data is sent to any server. Session management lets you save and restore your work across browser sessions.
Save session
Click Save Session in the header to download a JSON file containing your complete application state:
- All validated flows and their results
- Zone definitions, subnet assignments, and policy matrix
- Zone attributes (classification, environment, compliance scope, data sensitivity)
- Risk score weights and threshold settings
- Framework toggles (which frameworks are enabled/disabled)
- Active tab selection
The downloaded file can be stored wherever you keep your working files - a shared drive, a Git repository, or locally.
Load session
Click Load Session and select a previously saved JSON file to restore the full application state. Loading a session replaces all current state.
The session format is v4 with backward-compatible migration from v3. Sessions saved in older formats are automatically upgraded on load.
Reset
Click Reset to clear all state back to defaults - all flows, zones, and weight adjustments are removed. This is equivalent to a fresh page load.
Separate export/import options
In addition to full session saves, netbobr provides targeted export and import for sharing specific configurations with teammates:
| What | Format | Where | Use case |
|---|---|---|---|
| Zone configuration | CSV | Zones tab | Share zone definitions and policies across a team |
These targeted exports contain only the relevant subset of state, making them lighter and easier to share than a full session file.
Privacy model
All data stays in browser memory for the duration of your session. Specifically:
- No localStorage or sessionStorage - closing the tab discards all state unless you have saved a session file.
- No cookies - netbobr sets no cookies of any kind.
- No server communication - validation, scoring, and rule evaluation all run client-side. No flow data, IP addresses, or rule configurations leave your browser.
If your organization requires an audit trail, save sessions to a shared location and treat the JSON files as your record of analysis.