TL;DR: Load Lens collects minimal data. Core features (highlighting, profit estimation, email drafts) require no personal information. Feedback submissions are voluntary and only store what you explicitly provide. License activation sends your license key and a local device identifier to Creem for validation — we never see or store your card details (Creem handles all payments as our Merchant of Record).
1. Overview
Load Lens ("the Extension") is a Chrome browser extension that helps freight dispatchers analyze load board data on DAT One. This privacy policy explains what data the Extension accesses and how it handles that data.
2. Data We Collect
The Extension does not require user accounts, login, or registration. No personally identifiable information is collected through normal use. Specifically:
No browsing history is recorded
No user behavior is tracked or analyzed
No cookies are used
No analytics or telemetry are embedded
Exception: If you voluntarily submit feedback (bug report or feature request), your message and an optional email address are stored on our server. See Section 7 for details.
3. Data Accessed Locally
The Extension reads the following data, all of which remains on your device:
DAT One page DOM: Load board rows (origin, destination, RPM, total pay, broker info) are read from the webpage to provide highlighting and profit estimation. This data is never transmitted to our servers.
User preferences: Settings such as minimum RPM threshold, fuel cost, and truck MPG are stored locally in chrome.storage.sync. This is Chrome's built-in encrypted storage and is not accessible to us.
Usage counters: Daily profit calculation and email draft counts are stored locally in chrome.storage.sync to enforce free-tier limits. These counters reset daily and are never transmitted.
Device identifier: A random device_id (generated locally via crypto.randomUUID()) is stored in chrome.storage.local. It is used only for license activation to bind your license to this device, and contains no personal information. It is not linked to your identity.
License tier & cache: Your current tier (free/pro/team) and a 1-hour license validation cache are stored locally. The cached license key is held only on your device.
4. Data Sent to Servers
When you actively request a feature, the Extension sends only the minimum data needed to our serverless API:
Profit calculation (/api/profit): Origin, destination, fuel cost per gallon, and truck MPG. No load identifiers, broker info, or user identity is sent.
Email draft generation (/api/email): Origin, destination, rate, total pay, equipment type, and pickup date. No user identity, email address, or account info is sent.
Feedback submission (/api/feedback): Message content, feedback type (bug/feature/other), and an optional email address for follow-up. This data is stored — see Section 7.
License activation (/api/validate-license): Your license key and device identifier are sent. The license key is forwarded to Creem for validation; the device identifier is forwarded to Creem as an instance_name to bind the license to your device (Creem's activate flow). No load data or personal identity is included.
Profit and email API calls are stateless. Our servers do not store request data, log user activity, or maintain any database of user behavior for these endpoints. License validation results and Creem webhook events are cached in Upstash Redis (see Section 5 and Section 7).
5. Third-Party Services
The Extension's serverless API uses the following third-party services to process requests:
Google Maps Platform: Used to calculate driving distance between origin and destination. Google's privacy policy applies: policies.google.com/privacy
DeepSeek / OpenAI: Used to generate email draft text. Only load details (origin, destination, rate, equipment type) are sent. No personal data is included in these requests.
Vercel Blob Storage: Used to store voluntary feedback submissions. See Section 7.
Creem (Merchant of Record): Handles all payment processing for Load Lens Pro subscriptions. We never receive, store, or process your card details — payment is entirely between you and Creem. When you activate a license, your license key and device identifier are forwarded to Creem's license API (the device identifier is sent as an instance_name for device binding via Creem's activate flow). Creem's privacy policy applies: creem.io/privacy-policy
Upstash Redis: Used for license status caching and webhook idempotency. The cache contains only license metadata (status, product ID, event IDs) — no personal identity, no load data, no license key plaintext. Keys are isolated by namespace (checkout: / creem:event:) and never shared with other applications. Upstash's privacy policy applies: upstash.com/privacy
6. Permissions Justification
The Extension requests these Chrome permissions, each with a specific, limited purpose:
storage: Save user preferences (RPM threshold, fuel cost), daily usage counters, device identifier, and license tier/cache locally.
alarms: Schedule daily reset of free-tier usage counters at midnight.
offscreen: Play alert sounds using Web Audio API when a qualifying load appears. This is Chrome's recommended way to play audio in Manifest V3.
host_permissions (dat.com): Read load board data from DAT One pages to provide highlighting and analysis. The Extension does not modify DAT pages beyond injecting visual highlights and action buttons.
host_permissions (loadlenshq.com): The Extension's landing page (used as the post-payment success redirect after upgrading to Pro), the development mock-DAT page, and the serverless API. No personal data is exchanged with this domain by the Extension itself; it is used for API calls and the post-payment redirect.
7. Data Retention
Feedback data
When you voluntarily submit feedback through the Extension:
What is stored: Your message, feedback type, timestamp, and optional email address.
Where it is stored: Vercel Blob Storage (US region), accessible only with an admin token.
How long: Feedback entries are retained until manually deleted by the administrator.
IP addresses: Your IP address is used solely for rate limiting (10 submissions per day) and is not stored with your feedback entry.
To request deletion of your feedback data, contact us at the email below.
License & payment data
Card details: Never collected, stored, or processed by us. All payment data stays with Creem (Merchant of Record).
License metadata cache: Creem webhook events (payment status, license status) and validation results are cached in Upstash Redis with a 24-hour TTL for idempotency and license lookups. This cache contains license metadata only — no personal identity, no load data, no license key plaintext.
Local device data: Your device identifier, license tier, and 1-hour license cache persist only on your device until you uninstall the Extension or clear Chrome storage.
Feature API data (profit, email)
Profit calculation and email draft requests are processed in real-time and not retained on our servers.
8. Children's Privacy
This Extension is a professional tool designed for commercial freight dispatchers. It is not directed at children under 13, and we do not knowingly collect data from children.
9. Changes to This Policy
We may update this privacy policy from time to time. Changes will be reflected in the "Last updated" date above. If the changes are significant, we will notify you through the Extension. You may uninstall the Extension at any time if you do not agree with the updated policy.
10. Contact
If you have questions about this privacy policy or wish to request data deletion, contact us at: