Quick Bid — Privacy Policy

Last updated: July 23, 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

How the data is used

Team features and activity monitoring (team members only)

Team membership is optional, but the two team-sharing requirements are mandatory while you are an active member. When you create or join a team, Quick Bid requires you to check both load-market/match sharing and work-activity sharing before team use can continue. A client version that does not contain this required interface is locked until it is updated. If you do not agree, you can leave the team (or delete a team you own) and continue using Quick Bid outside that team.

When you join a team you must enter a first name and last name so teammates and the team owner can identify you. The team owner can see your name, join date, and whether the required team acceptance is complete. Your license email is not shown in that member list. Your bids are shared team-wide as described above. Work-activity sharing records only your browser's active / idle / locked state and, during the shift hours the owner configures, aggregate figures: total active time, number of breaks, and foreground time in the browser versus other applications. The monitor deliberately does not record keystrokes, screen contents, page or message contents, or which specific applications or websites are used.

Where data is stored

Your browser keeps a local runtime copy of settings, team-acceptance state, and cached route results. Approved settings are also stored as one license-scoped AES-GCM encrypted record in Cloudflare D1 so they can be restored after sign-in on a fresh installation. The encryption key remains a Worker secret and is not stored in the extension or database record. Login sessions, team acceptance and idle-permission state, team-owned fleet data, histories, matcher data, Sheet snapshots, route/geocode caches and calculations, and alert deduplication state are excluded from that settings record. Subscription, seat, team-scoped acceptance records, statistics, fleet-alert deduplication records, shared team alert settings and per-delivery preferences, driver-reminder thread and attempt metadata, and shared geocoding/route fallback caches are separately stored on our server (Cloudflare). Shared map-cache keys are SHA-256 digests rather than raw locations; cached values contain coordinates or travel time and distance. For active team members, shared bids, your full name, shared team vehicle configuration (which may include saved driver phone numbers, driver email addresses, and route/appointment fields), assigned-driver match records, and aggregate work-activity figures are also stored on our server so they can be shared with your team.

Third-party services

Data sharing and sale

We do not sell your data. We share only the minimum data needed with the service providers described above to operate Quick Bid, and we do not use it for any unrelated purpose. We do not use it for advertising, creditworthiness, or lending. Bid activity, shared team vehicle configuration, assigned-driver match statistics, and aggregate work-activity data are shared only with the team you choose to join.

Data retention

Local settings and cached routes remain in your browser until you remove the extension or clear them. Server-side successful geocodes are cached for up to one year, driving routes for up to 30 days, and no-result lookups for up to six hours. Raw bid/reply, assigned-driver match, fleet-alert deduplication, and completed or explicitly failed reminder-attempt records are kept about 90 days. Unresolved reminder delivery attempts and their thread metadata may be retained until support resolution or team deletion so Quick Bid can fail closed instead of risking a duplicate email. Reminder thread roots are kept for the life of the team so later reminders can carry the same-conversation threading headers; deleting the team deletes those thread records. Daily totals are kept longer for historical stats. Shared team alert settings and per-delivery preferences are kept with the team. License records are kept while your subscription is active and can be reset on request.

Your choices

You may decline or withdraw the required team sharing by leaving the team in Settings; a team owner may instead delete the team. Quick Bid can then continue outside the team. While you remain an active team member, both required checkboxes must stay accepted. A team owner controls the shared fleet-alert switch and organization recipient, and active team members can turn alerts on or off for an individual loaded delivery. Driver reminder emails are sent only when an active team member requests one. You can remove locally stored data by uninstalling the extension. To remove or reset your encrypted settings backup, license, statistics, team-acceptance, or fleet-alert records, contact us at the email below.

Contact

Questions about this policy: niksafree@gmail.com