IndagateDOCUMENTATION
TRUST & OPERATIONS Live

Data paths, privacy and retention

Understand which public demo, control-plane and device data is processed and where deployment-specific terms are required.

Last updated 27 July 2026 ยท Documentation version 2026.07

Public hosted scenarios

The product interface states when frame content is sent to an AWS-hosted model in us-east-1. The public demo states that uploaded frames are used for the request and are not retained by the demo. Do not submit confidential, regulated or personally identifying production imagery to a public evaluation surface.

Platform data

The managed platform stores invited-account attributes, tenant-scoped device records, telemetry snapshots, release metadata, hashed credentials and MCP audit events. Private release artifacts are retained in versioned S3 storage.

Edge data

Local camera/model processing can remain on the device. Optional private camera preview uploads the latest inference JPEG through an outbound authorization bound to the device, object size and SHA-256. Logged-in workspace users receive a separate short-lived viewing URL; the private preview object expires after two days. Sites can set camera_preview_enabled to false to keep every frame at the edge.

Outbound telemetry and preview policy should be reviewed during commissioning. Any evidence retention beyond the short-lived preview must be agreed for the production workflow.

Requests and residency

Send access, correction or deletion requests to info@oddessy.io. Include desired AWS region and data-residency constraints in the platform invitation request before a pilot.