Browser Companion privacy
Updated October 8, 2026 · Includes optional desktop messaging and guided WhatsApp setup
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.
Optional desktop messaging through Beeper
Version 0.6.120 adds an optional connection to Beeper running on your computer. The Companion requests identity permission for the consent flow and localhost access; its requests are restricted to http://localhost:23373. It does not expose that service publicly. You approve Beeper’s read/write API access and then choose each messaging account separately for your LoadPilot user and company. The Companion reads account identifiers, labels, connection states and available connection methods to show those choices. iMessage requires Beeper and Apple Messages on a supported Mac; Google Messages requires Google sign-in and Android pairing. Beeper must remain running for this connection.
The Companion uses the selected account’s chat metadata and matching contact information to find the exact one-to-one phone conversation. It displays that conversation’s message text, timestamps, direction, available delivery status and attachment names, and sends text only after your explicit action. Attachments themselves are viewed in Beeper. It verifies the account and recipient before each send and rejects groups and merged conversations. Text passes locally between Beeper, the Companion and the LoadPilot page; this connector does not upload conversation bodies to LoadPilot’s servers. Beeper and the messaging services process messages under their own policies.
The desktop access token and account bindings are kept in extension-only local storage, never Chrome Sync. The trusted Companion setup window may use the token in memory while waiting for device approval; it is not displayed or passed to the LoadPilot webpage or server. Draft text stays in the LoadPilot tab’s session storage. Minimal send records include account identity, recipient, request ID, text hash, provider message ID, timestamps and status, but not message text. They survive disconnection and browser restart to prevent automatic duplicate sends. Sign-out clears page drafts and ends the active LoadPilot context; it does not delete the extension’s protected recovery records. Remove individual channels in Messaging settings, or remove desktop access to delete this browser’s token and bindings. To revoke the token at Beeper too, remove LoadPilot from Beeper’s Approved connections.
Guided WhatsApp setup is available when Beeper offers a supported QR or phone-number pairing flow. You choose the connection, and the Companion sends your entered phone number only to the local Beeper API. QR codes are generated inside the extension; no external image service receives them. Temporary session identifiers and the current QR or pairing-code step are kept in extension session storage; the current step is cleared when the attempt completes or is cancelled, and closing the browser clears session storage. The Companion does not collect provider passwords, authentication cookies or passkeys. Steps requiring provider sign-in remain in Beeper. Phone approval does not change an existing LoadPilot sender: you select the returned account separately. Beeper and the chosen messaging connection may use their own cloud services.
Optional Google Messages conversations
Enabling conversation access requests permission for messages.google.com and scripting. You select a signed-in Google Messages tab and explicitly connect it to your current LoadPilot user and company. The companion reads that contact’s loaded message text, source timestamps, message identifiers, direction and displayed delivery status. It can open an exact phone-number conversation and load older messages. It does not export your full inbox, contacts, browser credentials or cookies. Unverified recipients are left for review.
Conversation text passes directly between your connected browser tab and the LoadPilot interface in the same browser. LoadPilot does not upload these message bodies to its server. Connection information and bounded draft-preparation records remain in browser session storage. Unsent drafts and their preparation identifiers are retained in the LoadPilot tab’s session storage across reloads, separately for the signed-in account, company, Google account, load, role and phone number. They are cleared when you sign out, the session expires, or you disconnect conversations. LoadPilot can prepare a message and open the connected Google Messages tab. You review it and press the native Send button there. LoadPilot does not automatically send messages; uncertain draft preparations are not automatically repeated. Existing message drafts and attachments are preserved. Disconnect conversations in the load panel or remove the optional website permission to stop this connection without unpairing your phone. Google’s service may keep its own message history.
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.
Back to Companion