Guide 18
Privacy & access
Understand session storage, network requests, and account access.
Session lifecycle
Imported datasets are processed in the browser. Temporary session storage supports refresh; a new tab starts a separate workspace. End the session from the top bar to clear its dataset and scenarios.
Browser or device failure can interrupt cleanup. Do not treat temporary storage as a permanent archive or an absolute data-erasure guarantee. Export your results deliberately.
Network boundaries
Map services receive requests for the areas being viewed. Cici requests share the question and a metric summary when you choose to send them. Account access requires the configured authentication service.
An unavailable basemap can fall back to a planar route view. Full map tiles and remote analysis are not guaranteed offline.
Engineering reports enable basemaps by default: providers receive tile requests for the approximate route bounding box, not raw logs or measurement values. Disable basemaps in the report toolbar to avoid those requests. Attribution stays in the PDF; unavailable imagery is explicitly labelled as a schematic. Workspace snapshots stay in browser memory (maximum four) and disappear on reload. RNO JSON configuration imports are validated locally and require review and Apply; Run and remote Save remain separate actions.
Access & accounts
Registration is open: create an account with your email and confirm it before signing in. The landing is public; importing data and opening the workspace require a verified account. For anything else, contact hello@cakramon.online.
Cici context privacy
Automatic segment payloads contain counts, numerical distributions, relative duration and observed-transition counts. They exclude coordinates, cell identities, file names, original timestamps and raw source rows. These values are sent only when you submit a question.
Your typed question is also sent. Do not paste credentials, confidential logs, personal data or GPS coordinates into the question. Local evidence/source inspection remains distinct from the remote numeric summary. Model and pilot exports can contain sensitive location/source references; export consent is separate.