Security & privacy
Honest about what the pilot does today.
Images can contain employees, customer labels, shipment information and personal information. We treat them accordingly — and we're clear about what's in place versus what's still post-pilot.
Encryption in transit
All API and dashboard traffic is served over HTTPS in deployment. Worker tokens, API keys and webhook signatures are never sent in plaintext across the network.
Every actor authenticates
Workers sign in with an employee code and PIN to get a short-lived signed token. Customer
systems use a hashed clr_ API key, and webhooks are
HMAC-SHA256 signed with a per-connection secret.
Evidence images stay separate
Evidence photos are stored apart from public URLs and are not exposed through any public endpoint. They exist to prove what was seen, when — not to be browsable on the web.
Audio is not stored
The pilot stores the transcript of a command, not the raw audio. Text-to-speech and speech-to-text are pass-through stubs in the mock provider; no audio files are kept.
Retention settings
Configurable image retention and scheduled deletion are planned but not yet built in the pilot. Today, evidence images persist with the event they document.
Access logging
Structured audit of who accessed evidence images is a post-pilot hardening item. Warehouse actions themselves are already logged as an immutable event trail.
Pilot-scope honesty
Cleer is in a warehouse pilot. The security model above reflects what the pilot implements today; the system has not been production-certified against a formal security standard. Before general availability we'll add signed/private image access, retention policies and access logging. If your data-handling requirements are stricter than pilot scope, tell us — the Enterprise plan is where those controls land.