Quick Bid — Privacy Policy

Last updated: June 18, 2026

Quick Bid is a browser extension that helps freight dispatchers prepare bid emails from a load board listing. This policy explains what data the extension accesses, how it is used, and who it is shared with. We keep data collection to the minimum needed for the extension to work.

What the extension accesses

• Email addresses (personally identifiable information). The email address you sign in with for your subscription, and the Gmail address you choose to send bids from, are used to verify your subscription and how many sending accounts a license uses.
• Personal communications. The extension reads a broker's contact email from the load listing to pre-fill a bid draft, and reads message subjects/senders in your open Gmail tab to show a timer on bids you sent and to alert you when a reply arrives.
• Website content. The extension reads load details shown on the load board page (origin, destination, miles, equipment, pieces/weight) and the open Gmail page to perform its functions.
• Bid activity statistics. When you send a bid or receive a reply, the extension records a small record (your email, your team code if set, the load's lane and rate, and the time) so you and your team can see bid counts and reply rates.
• Settings you enter. Your vehicle list, default rates, sending accounts, team codes, display name, and optional routing API key are stored to run the extension.

How the data is used

• To open a pre-filled bid email draft in your own Gmail account (the extension never sends email on its own — you review and send).
• To calculate distance, ETA, and transit time by sending the load's origin/pickup/delivery locations to mapping services.
• To verify your subscription and enforce the per-license limit on sending accounts.
• To show bid timers, notify you of replies, and produce your and your teams' bid statistics.
• If you join a team (via a team code), members of the same team can see each other's bid activity (who bid, the amount, and when) on shared loads.
• To send optional load alerts to your own Telegram, only if you configure it.

Where data is stored

Your settings and cached route results are stored locally in your browser (Chrome storage). Subscription, seat, and statistics records are stored on our server (Cloudflare). Raw bid/reply records are retained for about 90 days; only small daily totals are kept longer.

Third-party services

• ExtensionPay / Stripe — handles your subscription and payment. Card details are entered on Stripe's secure page and are never seen or stored by the extension.
• OpenRouteService, OpenStreetMap (Nominatim), OSRM — receive load location names to calculate distance/ETA/transit.
• Our server (Cloudflare) — stores subscription/seat and statistics records keyed by your email and team codes.
• Telegram — receives load alert messages only if you enable and configure Telegram alerts.
• Google (Gmail) — used to open the bid email draft in your chosen account.

Data sharing and sale

We do not sell or transfer your data to third parties, and we do not use it for any purpose unrelated to preparing and tracking load bids. We do not use it for advertising, creditworthiness, or lending. Bid activity is shared only among members of teams you choose to join.

Data retention

Local settings and cached routes remain in your browser until you remove the extension or clear them. Raw bid/reply records are kept ~90 days; daily totals are kept longer for historical stats. License records are kept while your subscription is active and can be reset on request.

Your choices

You can remove all locally stored data by uninstalling the extension. To leave a team, use the Leave button in Settings. To remove or reset your license or statistics records, contact us at the email below.

Contact

Questions about this policy: niksafree@gmail.com