OmnioIQ · Company

Security, stated plainly.

How the platform and the data within it are protected. Only what is true today, and nothing more.

Book a pilot Report a vulnerability

Access and transport

Signed in, and encrypted on the way.

Sign-inPeople sign in through Logto. Console and API access is tied to that sign-in.

In transitConnections use TLS, with HSTS so browsers keep to it.

Stored secretsPasswords, tracking-page checks and PINs are hashed, never kept as typed.

Customer tracking page: postcode check before personal details appear

Tracking links

Personal details wait for a check.

Tracking links are long and random. The customer confirms their postcode before the address, driver or exact ETA appear.

Repeated wrong tries lock the link for a while.

Audit trail

Who did what, and when.

Bookings, jobs, stops and routes keep a record of who changed what, when and why.

Custody chain after a breakdown handover

Event log

Every change is an event on the record.

Changes are written as events, so the history of a booking can be read back in order.

Webhooks

Signed, so you can check where they came from.

Outgoing webhooks are signed so your system can check where they came from, and are retried if they fail.

Retention

Kept as long as you choose.

Per workspaceEach workspace sets how long its data is kept.

Archive, then purgeA nightly job archives it and then removes it.

Reporting a vulnerability

If you believe you have found a security vulnerability in OmnioIQ, tell us before disclosing it publicly. Email office@omnioiq.com with enough detail to reproduce the issue. We will acknowledge your report and keep you updated while we investigate.

Security review

Running a vendor assessment and need more than this page? Write to sales@omnioiq.com and we will work through your questions with you.