1. Verification of sensitive instructions
1.1 Treat unexpected changes to pickup, destination, carrier identity, bank accounts, factoring or remittance details as requiring independent verification. Use an established contact channel rather than relying solely on a number or link supplied in the change request. Retain the original instruction and verification record.
1.2 An urgent tone, familiar logo or apparent executive signature does not establish authenticity. Pause a suspicious action and contact VEXO through the known business relationship. These controls reduce risk but do not guarantee prevention of every fraud or transfer responsibility regardless of fault.
2. Shipment identity and release
2.1 Use the agreed shipment reference and verify the expected carrier, driver and equipment before releasing freight. Report substitutions and mismatched credentials. Do not distribute release codes or cargo-location details to an unverified party.
2.2 An identity check must be lawful and proportionate. Do not collect unnecessary government identifiers in a public form. A specific customer security requirement should be agreed before shipment so the parties can confirm a practical and lawful process.
3. Documents and access
3.1 Share tax, insurance, contract and shipment files only through the agreed channels with authorised recipients. Protect downloaded copies and avoid placing confidential documents on public pages or shared links. Remove access when it is no longer needed.
3.2 The website requires secure hosting and appropriate administrative controls. The website does not establish that malware scanning, identity verification or every desired security measure has been deployed. Ask VEXO for an appropriate document-transfer method before sending sensitive records.
4. Reporting a suspected vulnerability
4.1 Report a suspected website security issue to dispatch@vexologistics.com with a concise description, affected page, approximate time and non-sensitive reproduction information. Avoid including credentials or other people’s records in the first message. Request a suitable transfer method if supporting material is sensitive.
4.2 Do not exploit the issue, access unrelated records, disrupt service or publish confidential data to demonstrate the problem. This notice does not authorise penetration testing or promise legal immunity; any authorised testing scope must be separately agreed.
5. Incident preservation and communications
5.1 Preserve suspicious messages, headers, transaction references and relevant records without forwarding them to unnecessary recipients. Avoid opening unexpected attachments or continuing a compromised session. Notify the appropriate internal decision-maker so containment can be coordinated.
5.2 VEXO should assess the affected information, operational risk and applicable reporting duties. No fixed public acknowledgement or remediation deadline is promised before an operational response process is established. Urgent physical safety matters must be directed to emergency services.