Trust and compliance

Who is on the other end of the drive.

Anyone may open a driver account, and nobody claims a drive unreviewed. A driver works under the business their own account operates as β€” themselves as a sole trader, or their company β€” recorded by a Bexongo worker, and the vehicle they name has been reviewed by Bexongo, with its class and plate on record. That is what lets a posted drive be claimed by a stranger and still be safe.

Reviewed supply

Trust has to be settled before the drive is claimed, not after.

There is no bidding round in which to size someone up, and no negotiation in which to ask questions. A driver claims your drive in one action, so everything you would want to know about them must already be true at that moment.

FirstBusiness recordedThenVehicle on record
  • Business recorded
  • Document requirements
  • Risk controls
  • GDPR-conscious setup

Trust architecture

An open door, and a reviewed vehicle behind it.

Signing up is easy anywhere; the hard part is being able to tell a business that the person claiming their refrigerated load genuinely has a refrigerated vehicle. That guarantee comes from reviewing the vehicle itself β€” its papers and its photographs β€” and from vehicle class being enforced at matching time rather than trusted as a claim.

  • VehiclesReviewed

    Every vehicle is reviewed by Bexongo before it can be named on a drive.

  • OperationsTraceable

    Drive status, complaints, and privileged admin actions produce audit records.

  • DataGDPR-conscious

    European data practices need qualified review before launch.

  • Registration is open, work is not

    Anyone may open an account. Claiming a drive additionally needs an active subscription and at least one vehicle Bexongo has reviewed and approved.

  • Documents as governance

    Requirements can vary by company, vehicle, cargo, country, and service scope, and are checked rather than collected.

  • Issue handling as trust

    Complaints, cancellation disputes, and delivery problems are handled in the platform, with mutual ratings on every completed drive.

Trust model

Six controls, each of them built into the platform rather than promised in a policy.

  • Reviewed vehicles

    A vehicle is reviewed by Bexongo β€” papers and photographs β€” before it can be named on a single drive.

  • Document requirements

    Required documents can be configured by company, vehicle, driver, shipment, cargo, country, and service scope.

  • Approval workflows

    Company, document, vehicle, shipment, payment, and complaint states can be reviewed by authorized admins.

  • Auditability

    Privileged changes are designed to produce audit records for operational accountability.

  • Risk controls

    Risk levels, compliance status, problem cases, and blocked states let administrators suspend an account or a company.

  • GDPR-conscious practices

    The platform should be reviewed and configured for European data protection requirements before production launch.

Trust and compliance in detail

Reviewed vehicles, enforced vehicle classes, separated access, and an audit trail.

What a business is trusting when it lets a stranger claim its freight, and what the platform does to make that trust reasonable. Legal review, production provider setup, and final compliance policy remain open items before launch.

An open account, a reviewed vehicle

Anyone may open a driver account, and opening one authorises nothing. Before a drive can be claimed the account must be active, carry an active subscription, and own at least one vehicle Bexongo has reviewed β€” registration papers, insurance, inspection and a complete set of photographs β€” with its class and plate on record, and the business the account operates as must have been recorded by a Bexongo worker. The driver who claims your drive is traceable and the vehicle behind them has been looked at, which is the substitute for the due diligence a quote round would otherwise give you.

Role-based access and audit trail

Admin, company, customer, and driver access are separated. Role-based permissions, tenant isolation, protected routes, and audit logging help keep sensitive operations traceable and reduce the risk of cross-account data exposure.

Location and private data

Matching is by proximity, which does not mean either side gets a map of the other. A business sees who claimed its drive and the vehicle they named β€” and their company, when they have one β€” but not the driver’s coordinates. Drivers cannot see each other at all. Uploaded documents and complaint evidence use private storage access patterns, with S3-compatible private storage in the architecture and live bucket verification still pending provider credentials.

Accountability after the drive

The status chain is enforced server-side, so a drive cannot be marked delivered without having been picked up, and cannot move backwards once advanced. Complaint records, cancellation disputes, and status history are retained. After delivery both sides rate each other per category, so accountability runs in both directions rather than only from business to driver. Legal terms, retention rules, and GDPR details still require qualified review before production launch.

Responsible launch

Clear claims, careful wording, and visible governance.

What is built today, and what is honestly still open.

  • Approval Β· built

    Business and document review

    The business behind a driver account is recorded before it can claim anything, and vehicle class is enforced at matching time.

  • Accountability Β· built

    Audit and exception handling

    The status chain is enforced server-side and privileged admin actions produce audit records.

  • Compliance Β· open

    Legal review before launch

    Privacy, cookies, terms, retention, and processor responsibilities need qualified legal review before launch.

Reviewed supply

A stranger claims your freight. Here is why that is safe.

A recorded business behind every driver account, vehicle class enforced at matching time, a server-enforced status chain, and ratings in both directions.