How LoadLens handles your data, from the waitlist to the bot.
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.
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 WhatsApp uses for 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.
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.
TEG's terms (Courier Exchange's parent) permit automated tools as long as they stay within human-equivalent request rates. The bot rate-limits every account to enforce it: at least 60 seconds between searches, no more than around 200 searches per day, around 30 quote submissions per day, and polling intervals never tighter than 5 minutes. Strictly slower than a determined human refreshing the CX web app by hand. If you ever hit a limit the bot will tell you, and you can DM /limits to see your current usage.
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.
Questions about how we handle your data, or want it deleted? Email hello@loadlens.co.uk.
© 2026 LoadLens. Not affiliated with Courier Exchange or Transport Exchange Group.