Browser Companion privacy

Updated September 20, 2026 · Covers 0.1.2 and the prepared 0.6.0 update

What the companion uses

When an authorized employee requests a browser review, LoadPilot sends the selected load’s transport fields to the companion. These can include vehicle details and VINs; pickup and delivery addresses; contact names, phone numbers and email addresses; transport instructions; carrier price and payment terms. Super Dispatch reviews can also include customer billing contact details and the customer price. Central Dispatch reviews exclude customer billing details, private payment links, internal general notes and uploaded documents.

The companion reads the current supported page’s URL, form headings, labels and existing field values to check the destination and avoid overwriting different values. Shipment addresses describe pickup and delivery locations; the companion does not request device GPS location.

Versions 0.3.0–0.6.0 can read matching saved load pages, including load ID, VINs, marketplace prices, status, driver and carrier, pickup and delivery addresses, contacts, email addresses, business hours, dates, vehicle details, payment terms, instructions and notes. It can also read the same saved Super Dispatch order’s Revision History: supported changed field names, previous and new values, displayed employee and time. It sends these selected fields to the same brokerage in LoadPilot. It does not send the whole page or unrelated account records. While LoadPilot is open, unlinked Super loads can be searched by current ID, previous IDs and VINs; a full matching identity is required before linking. Linked records are due for another check hourly. One background tab is used at a time. These checks can fill the list search field but cannot fill or create load forms, and browser-only checking stops when the browser is closed.

Optional Google Sheets helper

Version 0.5.0 offers an optional helper on docs.google.com. Enabling it requests Chrome’s permission for that website and scripting. It shows only for a workbook paired with your signed-in, open LoadPilot company tab. The helper displays the company name, connection state and last export time, links to the managed tabs, and lets you request synchronization through LoadPilot. It does not read spreadsheet cells, Google cookies or Google credentials. Closing LoadPilot stops helper actions; switching companies or signing out clears the pairing, and stale pairing data expires after 90 seconds. Pairing information stays in browser session storage.

Extension work panel

Version 0.6.0 adds a company work panel in the extension popup. It requests fresh, authenticated status from your open LoadPilot tab before displaying company totals, connected-service status or load search results. Search results contain load identifiers, vehicle, customer, route, transport status, payment status and amount. These results are held in popup memory and are not written to local extension storage. The panel remembers only the selected workspace identifier and the notification you hid. If several company sessions are available, it requires a company selection. Signing out or losing access prevents further requests.

The panel can focus an existing LoadPilot tab, open a selected record or tool, and open Super Dispatch, Central Dispatch or your connected spreadsheet. It checks for a marketplace sign-in form without reading passwords or cookies; an open marketplace tab does not prove API access. Gmail and QuickBooks credentials remain on LoadPilot’s server. The extension does not read those websites, send payment reminders, create accounting entries or mark money received. Financial changes retain LoadPilot’s role and confirmation controls.

Where the information stays

Load details used by the companion stay in chrome.storage.session for the current browser session. Closing the browser clears that session storage. LoadPilot keeps the saved load, review request and recovery history in the brokerage workspace. The browser keeps minimal request and workspace identifiers, tab references, timestamps, operation states and result counts in local extension storage to prevent duplicate openings and support recovery. It does not sync load data through Chrome Sync.

Versions 0.3.0–0.6.0 also store canonical destination record URLs with minimal local identifiers. Pending observations stay in session storage until acknowledged. LoadPilot retains linked-record comparisons and change history in the brokerage workspace. For companies with advanced synchronization enabled, supported driver, carrier, contact and stop-note changes can update the local load when they do not conflict with newer local edits. Displayed revision authors can be matched to company employees. A filling request expires after 15 minutes; a foreground observation session lasts up to 12 hours, and an individual linked-record check has a two-minute limit, while discovery has a four-minute limit. These limits do not erase retained business records. Removing the extension clears its browser storage.

Sharing and purpose

In 0.1.2 the employee requests field filling in the review panel. In 0.3.0–0.6.0 choosing Open for a new load can fill supported empty fields automatically when its creation form appears. Check that the correct company is signed in before opening a new load. Different existing values and ambiguous fields are left for review. The companion can use the Vehicles Add control and select an exact field option; it never saves or publishes the form. The destination may process entered values before Save. Operation results and selected saved-page observations return to LoadPilot for the requested dispatch workflow. This information is not sold, used for advertising, or used to determine creditworthiness or eligibility for lending.

What it does not collect

The companion does not read provider passwords or authentication cookies, access the Chrome History API, record general browsing history, or monitor unrelated websites. It has no advertising or analytics service and does not call Super Dispatch or Central Dispatch APIs. LoadPilot offers a separate optional server connection to the Super Dispatch Shipper API. Its credentials stay encrypted on the server and never enter the companion.

Your controls

Check the destination account before opening a new load. The companion never clicks Save or Publish. Cancel queued requests in LoadPilot. Disable or remove the extension to stop browser observation, or close LoadPilot to stop its background check queue. These actions do not delete saved LoadPilot loads. Managers can disconnect the separate API connection in Connections.

Updates and support

Standard installation and routine automatic updates are available after Chrome Web Store publication. On first installation the extension opens LoadPilot; routine updates do not open those pages. Connections provides a manual Chrome update check and a fresh-tab reconnect; pending extension restarts wait for unfinished companion work. Additional website permissions, if needed for a future feature, require the browser’s approval.

For companion support or privacy questions, email gdb090803@gmail.com or visit Setup & support. Contact your brokerage’s LoadPilot administrator about employee access and retained business records. Do not email passwords, verification codes, API keys or customer documents.