Last updated: July 2026
The waitlist
If you join the early-access list we store your email address and whether you said you're an owner-driver, a driver, or a fleet, so we can let you in when LoadLens is ready and email you about it. That's all. We don't sell it, we don't pass it on, and you can ask us to delete it any time by emailing the address below.
Your CX credentials
The landing page never asks for your Courier Exchange login. If you later connect the LoadLens bot, your password and 6-digit code are encrypted in transit and at rest using AES-256-GCM, the same encryption standard used for secure message backups.
We log in to CX once on your behalf, save the session cookie, and discard the code. We never receive the long-term secret behind your 2FA QR.
Your load data
When the bot reads a load to check it or send it to you, the details flow live to your Telegram chat and aren't kept afterwards. We don't aggregate one driver's load data with another's, we don't sell it, and we don't run a load board of our own.
How the bot understands your messages
When you message the bot ("loads from Leeds to London tomorrow"), the text of that message is sent to an AI model to work out what you're asking for. We restrict this to AI endpoints that do not train on your messages and either keep nothing at all or auto-delete within days. We never send your CX password, your session, or your account details to any AI provider.
Why this is allowed
TEG's terms for Courier Exchange (TEG is CX's parent company) permit automated tools that operate at human-equivalent request rates. The specific clauses LoadLens is designed around:
- Clause 3.5(c): no reverse engineering or capturing raw protocol payloads. LoadLens reads the standard user-facing web interface only.
- Clause 3.5(g): no systematic extraction beyond your own personal use. Every session is tied to one driver's own account.
- Clause 3.5(i): no automated bots that create excessive server load. LoadLens enforces rate limits stricter than a human would naturally work.
- Clauses 11.1 and 11.3 / AUP: general acceptable use. The bot does not bypass authentication, does not scrape in bulk, and does not share one user's data with another.
In practice: at least 60 seconds between searches, no more than around 200 searches per day, around 30 quote submissions per day, and polling never tighter than 5 minutes. Strictly slower than a determined human refreshing CX by hand. If you hit a limit the bot will tell you, and you can DM /limits to see your current usage.
Reversible in one tap
Reply /forgetme in Telegram any time. We wipe your encrypted credentials, clear your CX session, and delete the small list of seen-load IDs the bot kept to avoid repeating itself. After that the bot has nothing of yours left.
Contact
Questions about how we handle your data, or want it deleted? Email hello@loadlens.co.uk and we'll sort it.