LoadLens

Your CX login. Straight answers.

You're trusting us with the keys to your livelihood. Here's exactly what happens to them, in plain English, with nothing buried in legal.

In writing, LoadLens will never:

Where does my password actually go?

It's encrypted before it's stored, using AES-256-GCM (the same class of encryption banks use), and it's only ever decrypted for the moment the bot signs in to CX on your behalf. It's never written to a log, never visible to us in plain text, and it travels over encrypted connections end to end.

Your 2FA stays yours too. We never see the secret behind your authenticator QR code. You give us one 6-digit code at connect time, we use it once, then throw it away.

Can it bid without me?

No. Every bid begins with you tapping a button on a specific load. And if a price looks odd against your own history (suspiciously low or suspiciously high), the bot stops and asks you again before anything is submitted. Two taps for the weird ones, zero bids you didn't ask for.

Can other drivers see my searches, my rates, my jobs?

No. Everything is walled off per driver. Your searches, your alerts, your rate profile: none of it is pooled, compared, or shared. Your rate floor is calculated from your own completed jobs only, and it exists to protect your quote, nobody else's.

What do you keep, and for how long?

As little as we can get away with. Load details the bot shows you are held for minutes, not months. The list of loads you've already seen lasts a day so we don't ping you twice. Your personal rate profile (a few pence-per-mile averages from your own diary, if you opt in) refreshes every 30 days. Your encrypted login and session stay only while you're a user.

Send /forgetme in Telegram and all of it (credentials, session, profile, history) is wiped immediately. No email to support, no 30-day "processing period".

Does AI read my loads?

When the bot uses AI to make sense of a messy load note, the request goes through providers under no-retention terms: they're barred from storing it or training on it. Your loads don't become anyone's training data.

Will this get me in trouble with CX?

Honest answer: we've built it to behave like you on a normal day, not like a machine. One login session, human-speed limits hard-coded for every account: at least a minute between searches, a daily cap well below what a busy human does by hand, and no rapid-fire polling. The exact numbers are published on the connect page and you can check your own usage any time with /limits.

We're an independent tool and we don't speak for Courier Exchange or Transport Exchange Group. What we can promise is that the bot never bypasses their security, never touches other members' accounts, and never hammers their site. Your account, your call. That's also why the first 30 days are free, so you can judge it on your own terms.

Who's behind this?

A one-person build, out of the same driver group chats you're probably in. Not a forwarder, not a data company. Questions, doubts, or you just want to hear a human answer before you connect: hello@loadlens.co.uk. Sceptical is the right way to be. That's rather the point of the product.

The boring-but-real stuff

The web side runs with strict security headers, rate limiting on every public endpoint, and secret-token verification on the Telegram webhook with timing-safe comparison. Credentials keys can be rotated without downtime. None of this is exotic. It's just actually done.