Privacy Policy

Who this covers

This policy covers the One Load Board website and the account behind it, for everyone who uses it, carriers, brokers, shippers, and people who are only reading. Where it says “we”, it means the operating entity behind One Load Board.

What you tell us

Everything in this section is something you type into a form. Nothing here is inferred, bought, or scraped.

• Your account. Name, email address, and a password, which is stored as a one-way hash, so nobody here can read it, including us.
• Your company. Company name, phone number, the city and state you are based in, and your MC or DOT number.
• What you haul and where. The equipment types you run and the states you want to run in. This is the matching profile, and it is the thing that makes an alert worth receiving rather than worth muting.
• What you do on the board. Loads you post, offers you make, bookings, saved searches, and listings you have hidden.
• Messages to us. Anything you send through the contact form or by email, and our reply.

What we record ourselves

• Logins. Each sign-in writes a row with the time, the IP address the request came from, and the browser’s user-agent string. That record is what makes “somebody else is in my account” a question with an answer, and it is why it exists.
• Ordinary server logs. Requests, errors, and timings, kept for a short period to keep the site working and to investigate abuse.
• How you first found us. One cookie records the site or campaign that sent you here, and it is read once, at signup, and then stored on your account. It answers “how was this account won”, not “what has this person looked at”.

We do not build an advertising profile of our own and we do not run session recording. The Meta pixel, described under Cookies, is the one exception to “nothing leaves for advertising”, and it is the one you can switch off.

Cookies

Ours are the first two below, and they are listed in full. Google Analytics and the Meta pixel set the others, and they are the only cookies on this site set for anyone but us.

• olb_session, your login. It holds a random token your browser cannot read from JavaScript, and our database holds only a hash of that token, so a copy of the database cannot be replayed as a login. It lasts thirty days if you tick “remember me” and disappears when you close the browser if you do not. Without this cookie you cannot stay signed in.
• olb_attr, where you arrived from, set on the first page you land on and read once, at signup. It holds a short label such as “google / organic”, not an identifier and not a history.
• _ga and _ga_*, set by Google Analytics. They hold a randomly generated number that lets Google count one browser as one visitor rather than as a new one on every page, so we can see which pages people arrive on and which ones they leave from. Alongside the pages we count the steps of setting up and using an account as they happen: finishing the equipment and lane steps, reaching the board, opening an offer, sending one, a booking being confirmed, the free board closing, a membership button being pressed, a checkout being opened, and a membership being paid for. Each is counted as a number or a short label and nothing else — not which load, not which lane, not which broker, not which account, and nothing you have typed. They carry no name and no email, and we do not use them for advertising.
• _fbp, set by the Meta pixel. It holds a randomly generated number that lets Meta recognise this browser between visits. The pixel tells Meta that a page was viewed, that an account was created, that a checkout was opened, and that a membership was paid for, with the plan or account type as the only detail. It carries no name, no email, no MC number, no load and nothing you have typed. Meta uses it to show our ads to people like the carriers who already use the board and to tell us which ads worked; what Meta does with it on its side is governed by Meta’s own privacy policy.

The Meta pixel is off for any browser that sends a Global Privacy Control signal, and you can switch it off for your browser on the Your Privacy Choices page. When it is off it does not load at all, so Meta receives nothing about the visit, not even the first page view. Your account and the board work exactly the same either way. When an account is created, our server also tells Meta about it directly, so the count survives an ad blocker: the same fact the pixel reports, with your IP address, your browser’s user-agent string and the _fbp cookie, and still no name, email or anything about a load. The same opt-out and the same Global Privacy Control signal stop that copy too.

Analytics tells us how the site is found and where it loses people, which is why the counts above exist: without them we can see that somebody left and not what they were trying to do. Two of them — a booking being confirmed and a membership being paid for — happen when you are not on the site at all, so your browser reports them the next time you open it; we keep a mark against the record saying it has been counted, and that mark is the only thing stored. None of it is joined to your account, and none of it is used to build an advertising profile — Google is sent the fact that an offer was sent, never who sent it or what it was for. You can switch it off for every site you visit with Google’s own browser add-on, and a browser set to block third-party cookies or a tracker-blocking extension already stops it.

If we ever add another advertising cookie or pixel, this section changes before it ships, and consent will be asked for where it is required.

Payments, and why we never see your card

Memberships are sold through Paddle, which acts as merchant of record, Paddle is the legal seller, takes the payment, and handles the tax. Card numbers, expiry dates and billing addresses go to Paddle and stay with Paddle. Not one of them reaches our servers or our database.

What we store on your account is Paddle’s account of the subscription and nothing more: Paddle’s customer and subscription identifiers, which plan and which price you are on, the status of the payment, and the next renewal or cancellation date. No card, no last four.

Paddle processes your payment data as an independent controller under its own privacy policy. If you want a card removed or a receipt reissued, Paddle is the party that can do it.

Public records we check

We verify the MC and DOT numbers our members give us against the FMCSA’s free public register. That is a public database, we do not add anything to it, and the only thing we take from it is whether the number is active and whose it is. The verification badge on a profile is the result of that check and nothing more.

What we do with it

• Run your account, sign you in, and keep it secure.
• Match freight to your equipment and lanes, and send you the alerts you asked for.
• Show your company details to the other party on a load you post, offer on, or book, because that is how the load gets covered.
• Take membership payments, through Paddle, and tell you about renewals and failures.
• Verify authority and investigate double brokering, fraud and abuse.
• Answer your emails.
• Understand which of our own pages bring in carriers and brokers, in aggregate.
• Measure whether our ads on Facebook and Instagram bring in carriers, through the Meta pixel.

We send marketing email only if you have asked for it. Alerts and account emails are a different thing: they are the product, and they are controlled by the notification switches in your settings rather than by an unsubscribe link.

Who else sees it

Five groups, and no others.

• The other party on a load. When you post, offer on, or book freight, the company at the other end sees your company name, your authority number, and how to reach you. There is no way to do freight without this.
• Paddle. Your email address and the plan you are buying, so it can sell you a subscription and send you a receipt.
• The services that run the site. Hosting, the database, and email delivery. They process data on our instructions and for no purpose of their own.
• Meta. Through the pixel described under Cookies: that a page was viewed, an account created, a checkout opened or a membership paid for, against the browser’s _fbp number. Never your name, email, company or anything about a load.
• Anyone the law obliges us to tell. A valid legal demand, or a situation where somebody’s safety or somebody’s freight is at immediate risk. We will tell you when we are allowed to.

We do not sell personal information for money and we do not rent our member list. The Meta pixel is, under some US state privacy laws, “sharing” personal information for cross-context behavioural advertising, and you have the right to opt out of it: use the Your Privacy Choices page, or send Global Privacy Control from your browser. If the business is ever sold or merged, your data would move with it, and you would be told before that happened, not after.

Freight data that is not about you

Load listings come from the companies that post them and from third-party feeds we license. A posting carries the posting company’s details, not yours, and the posting company is responsible for what is in it. If a listing contains something about you that should not be there, tell us and we will take it down while we sort it out.

How long we keep things

• Account and company details: while your account is open, and for a short period after you close it in case you come back or a dispute follows.
• Loads, offers and bookings: kept as a record of what was agreed, because that record is what settles an argument about a rate months later.
• Login records: a rolling window long enough to investigate a compromised account.
• Server logs: days to weeks, not years.
• Billing records: as long as tax and accounting rules require. Those records are Paddle’s as much as ours.

How it is protected

Traffic is encrypted in transit. Passwords are stored as one-way hashes and cannot be recovered, only reset. Session tokens are random, held in a cookie the browser cannot read from JavaScript, and stored on our side only as a hash, and because they are database rows rather than self-contained tokens, a session can genuinely be revoked rather than merely expiring.

None of that makes a breach impossible. If one happens and it affects you, we will tell you what was taken and what to do about it.

What you can ask for

Whatever law applies to you, these are available on request:

• A copy of the personal data we hold about you.
• Correction of anything that is wrong, most of it you can edit yourself in settings.
• Deletion of your account and the personal data in it, except records we are required to keep or that are needed to settle a live dispute.
• An end to marketing email, immediately and without asking why.
• An explanation of anything in this policy that is not clear.

Email the address below. We will confirm it is really you, and answer within thirty days. We will not charge you, and we will not make the account worse for asking.

Where your data is

The network is operated for the United States market and the data is processed there. Paddle operates internationally, so payment data is handled outside the US under Paddle’s own arrangements. If you use the site from outside the US, you are sending your data to the US.

Not for children

This is a service for freight businesses. It is not for anyone under 18, and we do not knowingly collect anything from a child. If one has got through, tell us and we will delete the account.

Changes to this policy

When what we collect or who we share it with changes, this page changes with it and the date at the top moves. For a change that materially affects you, we will email you before it takes effect rather than relying on you to notice a date.

Getting hold of us

Privacy questions, data requests and complaints go to support@oneloadboard.com or through the contact page. How we handle your account is also covered by the Terms of Use.

The agreement covering your use of the network is the Terms of Use.