Security & data handling

Carrier invoices are parsed in memory during the request. The uploaded file itself is not written to disk or object storage.

Driver mobile numbers, national identifiers and other personal details are stripped before any analysis runs and are never returned in results, memos or alerts.

Only corporate entity names, Pro/shipment references, currency values and monetary line items are retained for the audit record.

Audit output is deterministic and traceable: every flagged line carries the contract rule and the exact variance it breached, so findings can be reviewed line by line.

Administrative views (submission ledger, pipeline, billing) require an authenticated account. There is no anonymous access to stored submissions.

Every database table storing submissions, tenders or engagement events denies public access by default; reads and writes happen through server-side functions only.

Prospect material is delivered on private, per-company links. Links are unique, unlisted, excluded from search engines and can be rotated on request.

Client portals are token-scoped: a portal link exposes only that company's own audits and disputed lines.

Audit records are retained for the life of the commercial relationship. On written request we delete a company's submissions, audit records and engagement history within 30 days.

All traffic is served over HTTPS/TLS. Plain HTTP requests are redirected.

Data at rest is encrypted by the managed database platform; backups are encrypted with the same controls.

Application logic runs in an isolated managed runtime with no persistent local filesystem, so invoice content cannot linger between requests.

Integration credentials (TMS handshake keys, notification keys) are held in encrypted secret storage, never in application code or in the browser.

Inbound TMS webhooks are authenticated with a shared key compared in constant time, and payloads are schema-validated before they reach the database.

Lawful basis: invoice and tender data is processed on the basis of the contract with the customer, or legitimate interest for an evaluation you initiate yourself.

Roles: the customer is the controller of its freight documents; SwiftLogiAudit acts as processor and processes only on documented instruction.

Data minimization is enforced in the engine itself rather than by policy alone — personal identifiers are removed at ingestion.

Data subject requests (access, correction, erasure) are actioned within 30 days of a written request.

Subprocessors: a managed cloud application platform (hosting and edge delivery), a managed Postgres database provider (storage), a large-language-model provider used only for fallback extraction where a document does not match a known carrier layout, and a transactional email provider for internal alerts. An up-to-date subprocessor list is available on request.

No invoice content is used to train third-party models.