Vangrid’s privacy model is architectural, not just a policy. Raw sensor data is processed directly on the edge node that captured it — your API calls never receive raw sensor streams and raw data never traverses the network. What reaches your application is derived, aggregated ground truth with a cryptographic provenance record.Documentation Index
Fetch the complete documentation index at: https://docs.vangrid.io/llms.txt
Use this file to discover all available pages before exploring further.
How edge-computed privacy works
Every Vangrid edge node runs a local compute layer that:- Captures multi-view observations from the physical environment
- Processes those observations locally into structured ground truth (geometry, classification, confidence)
- Signs the derived output with a node-specific cryptographic key
- Transmits only the signed, derived record — never the raw sensor stream
This means you cannot retrieve raw sensor imagery or unprocessed data through the Vangrid API. You receive verified, structured spatial observations only.
What you receive vs. what stays at the edge
| Data type | Available via API | Stays at edge |
|---|---|---|
| Geometry (location, shape) | Yes | — |
| Ground truth score | Yes | — |
| Observation classification | Yes | — |
| Provenance hash | Yes | — |
| Raw sensor images | No | Yes |
| Unprocessed point clouds | No | Yes |
| Node identity / location | Aggregated only | Precise location |
Privacy for your queries
Your spatial queries are also handled with privacy in mind:- Query parameters (AOI geometry) are not persisted beyond the request lifecycle
- Results are scoped strictly to your API key’s authorized regions
- No query history is shared across customers