Where every driver is, every ten seconds. Treat that accordingly.

A fleet platform holds the movements of thousands of people who never chose it. Every vendor lists the same controls, so this page doesn't start there. It starts with who can see what, what happens on the bad days, and what we have not done yet.

Report a vulnerability

Who can see what

Your roles above the line, ours below it. No one at Saqr has a way to open your footage — there is no screen for it. Our support engineers see nothing until your administrator opens a session, and it closes itself after 24 hours. Pick a row for the reasoning.

Live position	Trip history	Footage	Driver scores	Driver personal details	Fuel and costs	Billing
Yes	Yes	Logged	Yes	Yes	Yes	Yes
Own	Own	Logged	Own	Own	Own	—
Yes	Yes	—	—	—	—	—
—	—	—	—	—	Yes	—
Own	Own	Own	Own	Own	—	—
Session	Session	—	Session	—	Session	Yes
Logged	Logged	—	—	—	—	—

Saqr staff

Saqr support

Our engineers answering your ticket

Nothing until your administrator opens a support session, which expires in 24 hours and shows up in your audit log. Never footage.

YesYes
OwnTheir own scope
LoggedWith a reason, logged
SessionOnly in a support session you open
—No

From the truck to your warehouse

Five places the data passes through, what protects it at each, and where that protection stops.

01
On the unit

What protects it

Firmware is signed and a unit refuses an unsigned update. Buffered positions are encrypted on the flash, and each unit has its own certificate.

Where that stops

Someone with the unit in their hands and time can still pull it off the vehicle. What they get is a unit that can no longer talk to us once its certificate is revoked.
02
Over the air

What protects it

Mutual TLS from the unit to our ingest, over a private cellular network that is not reachable from the internet.

Where that stops

Cellular can be jammed. Encryption cannot stop that; the power-and-motion rules on the Wired page are how it gets noticed.
03
In our systems

What protects it

Stored in data centres in the Kingdom, in two sites, encrypted at rest with keys held in-Kingdom. Production access needs a second person's approval and is logged.

Where that stops

Engineers who run the platform can, with approval, reach production. We keep that group small and the log readable by you — not empty.
04
On your screens

What protects it

Two-factor sign-in for everyone, required for administrators. Sessions expire, and a lost phone's driver app session can be revoked from the dashboard.

Where that stops

A shared password on a shared dispatch PC is still a shared password. We can require two-factor; we cannot make people not share a desk.
05
Leaving through the API

What protects it

Keys scoped per integration, webhooks signed, exports written with credentials that can only add files to your storage.

Where that stops

Once data is in your warehouse, it is protected by your warehouse. That is where most of it ends up.

The bad days, step by step

An API key leaks

Minutes Revoke it under Integrations. Calls with it fail at once; nothing else is affected, because it was one key for one system.
Same day Read the key's access log for what it called and from where. Keys only ever had the scopes you gave them.
Same day Create a replacement and redeploy the integration. The guide does it without downtime.

A driver's phone is lost

Minutes End its session from the driver's record. The app locks on its next connection.
— What was on it: today's jobs and the driver's own events. No other driver's data, no footage, no fleet map.

A unit is pulled off a vehicle

45 min The unit is marked silent and an event is raised, with its last position.
Same day Revoke its certificate. It can no longer send data as that vehicle, or as anything else.
Days A replacement is fitted inside the regional response time.

Someone leaves your company

Minutes Deactivate the user. Their sessions and any keys they created stop working.
— Their past actions stay in the audit log under their name. Deactivating a person does not rewrite history.

You leave Saqr

Before the end Export your full history as CSV or Parquet. No exit fee.
On the last day We point your units at a server you name, if you want to keep them.
90 days after Your data is deleted, and we send a written confirmation that it was.

Something goes wrong on our side

Hours The status page says so first — before we are sure of the cause, not after.
72 hours If your data was exposed, your administrators hear it from us, in writing, within 72 hours of us confirming it.
Weeks A written account of what happened and what changed, whether or not anyone asks.

How long we keep it

Live: Positions on the map within seconds of arriving
90 days: Full-resolution replay, every fix, instant to load
6 years: Complete trip history retained, no thinning
Any time: Export the lot as CSV or Parquet to your own bucket

Retention, export and deletion

What is not done yet

No external certification yet: An independent audit is booked and not finished. Until it is, this page is our description, not someone else's verification, and you should weigh it that way.
Data in the Kingdom, people in three cities: Storage and processing stay in-Kingdom. Support engineers work from Riyadh, Jeddah and Dammam, and a support session you open is visible to whichever of them takes the ticket.
Webhook payloads leave by design: Events you subscribe to are sent to your endpoint and can be replayed for 72 hours. A misconfigured endpoint sends them somewhere you did not intend.
No bug bounty: We do not pay for reports yet. We do answer them, credit the reporter if they want it, and do not take action against good-faith research.

Found something?

Tell us here. It goes straight to the engineers, and a person confirms it within two working days.

Test against your own account or the developer sandbox, not another customer's data.
Do not jam, move or open units on vehicles you do not operate.
Give us a reasonable time to fix it before you publish, and we will tell you when it is fixed.

Current incidents