Start with the minimum data required to prove the audit.
This page describes the current public website and pilot intake posture. It avoids claiming infrastructure controls that are not visible in this static codebase.
Data minimization
For a revenue leakage audit, the starting point should be the smallest useful export: completed loads, invoice lines, accessorial records, timestamps, and billing rules where available.
No upload on the website
The current site does not provide a sensitive-data upload workflow. The audit request form is for intake only.
CSV-first pilot
The revenue recovery offer is designed so the first review can begin from a limited historical CSV/export rather than production credentials.
Read-only preference
If a direct connection is later discussed, read-only access is the preferred audit pattern. Write access is not required to evaluate leakage.
Anonymization
Customer or driver identifiers can often be anonymized for early review when those fields are not required for the analysis.
Human approval
The revenue recovery workflow is positioned around review and approval before recovery action. The site does not claim automatic production rebilling.
Important boundary
Do not send sensitive freight data through the website form. The form uses Web3Forms for message delivery and is intended only to start the conversation. A suitable transfer method, retention expectation, and deletion expectation should be agreed before any customer data is exchanged.
What is and is not claimed.
The current repository is a Vite/React static website. It does not include a freight data backend, credential vault, tenant-isolation layer, audit log service, or file upload workflow.