Docs / Reference
Data boundaries
Raw recordings stay on your machine. You decide when to upload one derived file, and you can read exactly what is in it first.
Stays on your machine
- Raw MCAP and rosbag2 files
- Message payloads: images, point clouds, GPS positions, decoded data
- Original file, topic and schema names; absolute local paths
- Absolute timestamps
- Credentials and environment variables
mapping.json(it contains your topic names)
Velune Trace and Velune Adapter run locally and perform no network transfer.
What is inside comparison.velune
- Neutral stream and schema keys (for example
stream.unmapped.003) - Per-second message counts and interval statistics, in time relative to the start of each run
- Run-level metadata such as duration and counts
- The category labels you assigned
- How each stream was paired across runs (stream key and basis only)
- Manifests with SHA-256 hashes of every file
The preview file, comparison.preview.json, lists every entry and the excluded categories. How to review it.
Derived does not mean anonymous. The file still describes the structure of your system — which streams exist, how often they publish and how their timing behaves. We do not describe it as fully anonymous. During the Beta, transfer boundaries are reviewed with each team.
On the Compare service
- Access requires Beta credentials (HTTPS, browser sign-in).
- Each upload is processed in a temporary directory that is deleted when the report is returned. Reports are not stored on the server.
- Access logs record request time and status, not file contents.
How your data may be used
| Option | Terms |
|---|---|
| Contribution Access · no fee | Approved derived data may be used to develop, evaluate and improve VeluneOS products and services, including aggregate or comparative analysis across customers' approved data. |
| Private Access · quoted per team | Your data is used only to provide and operate the service you requested. It is not reused to improve VeluneOS products or services. |
Both options use the same engine and produce the same report. Choosing an option in a request is not consent: data-use terms are confirmed in writing before your first upload.
What VeluneOS never decides
- Root cause
- Fault, responsibility or liability
- Whether the robot is safe
- Whether a change is a regression
- Release go / no-go
Find the events. Engineers find the cause.