Which Amazon Relay Extensions Collect Your Data?
Some Amazon Relay extensions send your business data - booked loads, payouts, lanes, USDOT number, and carrier details - to their own servers as part of how their features work. Based on a static review of each extension’s shipped code, LoadFetcher and RGD do this. That data is commercially valuable, so it’s worth knowing exactly what leaves your browser - and deciding for yourself. Rocket Relay keeps your business data in your browser.
LoadFetcher (v3.23.4)
Re-checked August 2026 against the current Chrome Web Store build:
- Confirmed - live loadboard loads are sent to its server. Payout, price-per-mile, distance, lanes, and equipment from the loadboard are posted to a LoadFetcher server.
- Confirmed - carrier identity is read. Your company name, email, DOT/authority, carrier ID, SCAC, and MC number are read from Amazon’s data and handed to LoadFetcher’s website when it requests them.
- Confirmed - notifications carry trip and driver details. Trip data, driver names, and your company name are sent to its notification server - this powers its alerts feature.
RGD (v1.1.5)
- Confirmed - booked and missed trips are sent to its server. Payout, cost-per-mile, lanes, facility codes, load ID, and times are uploaded for each load.
- Confirmed - tagged with your carrier identity. Every event carries your company name and email.
- Not found - driver PII. We found no driver names in its outbound data.
How Rocket Relay is different
Rocket Relay reads your loads and drivers in your browser to filter and book on your behalf - and that’s where they stay.
- We do not upload your loads, payouts, lanes, USDOT, carrier identity, or drivers.
- We sync only anonymous aggregate usage stats (such as which mode you ran).
- We do not bundle third-party fingerprinting or sell data.
Your business data is your competitive edge. Keep it that way.
Related: Is Amazon Relay auto-booking safe?