Skip to main content

Security

Sign-in and sessions​

  • Each person signs in with their own e-mail and password, set through their invitation.
  • The console and the web apps keep the sign-in tokens on their server, never in the browser. The browser holds a session cookie the scripts cannot read, for its own host only.
  • Sign out ends the session in the app and at the sign-in service.
  • A disabled member is refused at sign-in.

Roles​

What a member may do follows their role, checked by the platform on every request, not only hidden in the menu. A member's access never exceeds their role, and an API key never exceeds its creator's. See Roles.

Isolation​

Each organisation's records are its own. Another organisation's request finds nothing.

Approvals​

Risky commands, such as an engine cut, need a reason and a second person: the person who asks cannot approve. See Remote commands.

Secrets​

Shown once, never listed again: API keys, OAuth app secrets, webhook signing secrets, insurer programme secrets, test keys. An e-lock's PIN is kept sealed and reaches only the lock. An adapter's secret settings are never shown back.

Sealed records​

These are sealed when made and cannot be changed afterwards. A changed or removed one breaks its chain:

  • the audit log;
  • proof of delivery (e-POD) and e-CMR consignment notes;
  • freight rate confirmations, invoices and dispute threads;
  • privacy decisions;
  • customs timelines, screening decisions and audit packs;
  • closed pay statements and end-of-service settlements (hashed);
  • ZATCA tax documents;
  • tachograph files, the yard log, traffic fines as issued.

Integrations​

  • Webhooks are signed; a rotated secret signs the next delivery.
  • A custom domain is used only once its DNS TXT record proves who holds it.
  • An adapter a publisher submits in Adapter Studio carries the publisher's signature, which ZAITRACK checks before approval; revoking the key revokes what it signed. ZAITRACK's own built-in adapters are not yet signed.

ZAITRACK's staff​

ZAITRACK's staff work across organisations in their own console. Each change they make is written to the organisation's audit log before and after it runs, and refused while the log cannot record it. A fleet's people cannot sign in to the staff console.