Laneworks Trust Center

Trust is part of the workflow.

This page describes the controls implemented in Laneworks today, including their practical boundaries. We would rather be precise than imply a certification, partnership, or guarantee we have not earned.

Workspace boundaries

Operational records are scoped to an organization and protected by role-based authorization and database row-level security policies.

Boundary: Laneworks uses shared application infrastructure with organization-scoped records; it does not claim that every customer has separate physical tables.

Protected integration credentials

Supported integration credentials are encrypted server-side with authenticated encryption before storage and are not returned to the browser as plaintext.

Boundary: This statement applies to supported stored integration secrets, not as a blanket claim that every field receives separate application-layer encryption.

Browser companion boundaries

The companion runs customer-directed, read-only load searches inside the user’s existing authorized browser session.

Boundary: It does not request provider passwords, read password fields or cookies, contact a broker, bid, or book freight. Customers must use their own provider account and follow its terms.

Agent controls

Agent tools are read-only by default. Owners can enable supported write tools, and consequential actions require explicit confirmation.

Boundary: Agent execution records are written for accountable review. An enabled tool is still limited by the signed-in user’s organization and role.

Policy-controlled data export

Workspace owners can request a policy-controlled JSON export of supported operational records.

Boundary: Exports exclude integration credentials, authentication tokens, document binary content, and other protected or unsupported data. Supported tables are subject to service limits.

Operational evidence

Documents, readiness results, load events, and approved agent actions stay connected to the operating record that created them.

Boundary: Laneworks aims to make a decision traceable. It does not convert an internal audit trail into a third-party certification or legal assurance.

Built from freight operations

The Logiq FM relationship

Laneworks was shaped inside real freight operations at Logiq FM. Logiq FM uses its own organization workspace. Access to other organizations is governed by tenant membership, roles, and database policies.

Current posture

No borrowed trust badges.

Laneworks does not represent itself as SOC 2 certified today. Provider names describe infrastructure or customer-directed connections—not endorsement or a commercial partnership unless explicitly stated.