Security & data handling

We only ever read

Every operation we issue against your ELD is a read. We do not create, modify or delete anything in your ELD account: not your hours-of-service logs, not your vehicles, not your drivers, not your groups. Nothing we do can alter a record you may later need for a compliance audit.

What we read is narrow, too: vehicle identifiers and names, GPS positions with speed and heading, and timestamps. We do not read driver records, messages, or camera footage, and the service asks nothing of your drivers at all.

Your ELD credentials

Credentials are encrypted with AES-256-GCM before they are written to the database, using a key held outside it. GCM is authenticated encryption, so tampering with a stored value is detected rather than silently decrypting to something else.

They are used for one thing: reading your own fleet's telemetry on your behalf. You can disconnect at any time, which stops all further access immediately.

Keeping carriers separate

Every piece of carrier data — vehicles, telemetry, facilities, detention events, invoices — is stored against the carrier it belongs to, and every query that reads it is scoped to the carrier making the request. There is no path by which one carrier's account can read another's.

Within a carrier, permissions are enforced on the server on every request and read from the database rather than the session, so a stale token cannot carry stale privileges. Anything unrecognised is denied rather than allowed. Hiding a button is a courtesy; the server decision is the control.

A person approves every invoice

We infer detention from where a truck was and for how long. We have no load data, so we cannot distinguish “waiting to unload” from “parked here by arrangement” — which is why nothing is ever sent to a broker automatically. Someone at your company reviews and approves each claim, and every one of those decisions is recorded with who made it and when.

We never touch your money

Invoices go out under your own billing identity and brokers pay you, directly. We are not a party to any claim, we hold no funds, and we are not a collections agency. Our fee is a flat rate per truck — never a percentage of what you recover.

Who we rely on

DwellWatch runs on managed infrastructure and uses a small number of service providers: hosting and a managed database, an email provider for delivering invoices and account mail, and a payment processor for subscriptions. Each receives only what it needs, and none may use your data for their own purposes. Card details go straight to the payment processor and never reach us.

What we have not built yet

We would rather you learn this here than find out later. DwellWatch is an early-stage product run by a small team, and the following are honest gaps rather than omissions:

• No third-party security audit or SOC 2 report. We have not been independently assessed.
• No automated deletion of old telemetry yet. We can report what would be removed and we will delete on request, but scheduled retention is not in place. Deleting data that supports an invoice you have already sent would leave you unable to defend it, which is why this is being built carefully rather than quickly.
• Formal incident response is still being written. In the meantime the commitment is simple and we will hold to it: if carrier data is exposed, we tell the affected carriers what happened and what we know, promptly, without waiting to have a complete story.

Reporting a vulnerability

Write to [email protected]. Tell us what you found and how to reproduce it. We will confirm receipt and keep you updated, and we will not pursue anyone acting in good faith to make this safer.