Privacy Policy | Loadful.ai

Loadful.ai (“Loadful”, “we”) provides software for auto-transport carriers: sourcing loads, planning trips, and reconciling what was hauled against what was paid. This policy explains how we handle information in that product.

Who this covers

This policy applies to the Loadful.ai web application, the Loadful Chrome extension, and the Loadful API. Loadful is a business tool sold to carriers and dispatchers; we do not knowingly collect information from children, and the service is not directed to anyone under 18.

What we collect

Account information. When you sign up we receive your name and email address from our authentication provider, Kinde. We never receive or store your password.

Company and fleet information you enter. Your company name, DBA, USDOT and MC numbers, business address, contact details, operating regions, trucks, trailers, cost assumptions, and drivers.

Load and trip data. Loads you enter by hand, loads you scout from load boards, the trips and routes we build for you, and the evaluations, bid recommendations and outreach drafts generated for those loads.

Load board data, at your direction. The Loadful Chrome extension runs in your browser, under your own load-board login, and reads pages you are already authorised to see on Super Dispatch and Central Dispatch. It acts only when you ask it to. It copies your own booked and hauled loads — lanes, dates, pay, broker, vehicle and VIN details, driver name, and payment status — into your Loadful account. We do not have your load-board credentials and we never sign in as you.

Bank account and transaction data, if you connect a bank. See the dedicated section below. This is the most sensitive thing we hold, so it is described there in full rather than summarised here.

Operational logs. Ordinary server and application logs — timestamps, request paths, error messages and the account id involved — used to keep the service running and diagnose faults.

We do not sell personal information. We do not use your data to build advertising profiles, and we run no advertising trackers in the application.

Bank accounts and transactions

Connecting a bank account is optional. The product works without it; you connect it only if you want the money that lands in your account matched against the loads you actually hauled — which broker paid, for which loads, and what is still outstanding.

You make the connection, and we never see your banking login. The connection runs through Plaid, Inc. You authenticate with your bank inside Plaid Link — Plaid’s own interface, running in your browser — and you choose there which accounts to share. Your bank username, password and any one-time code go to Plaid and your bank — never to Loadful. We cannot sign in as you, and we have no way to obtain those credentials. Plaid handles what you give it under Plaid’s end-user privacy policy.

What we request. One Plaid product: transactions. We do not request account and routing numbers, identity, income, assets or liabilities. The access is read-only, and that is structural rather than a promise: there is no code path in Loadful that can move, hold or disburse money, and we never asked Plaid for the ability.

What we copy. For each account you share: the institution name, the account name, the last four digits of the account number, and the account type. Never the full account or routing number — we did not ask for them and were not given them. For each transaction: the posted and authorised dates, the amount, the counterparty and merchant name, the original bank memo line, whether it is still pending, and the record of the transaction as Plaid sent it to us. The memo line matters more than it looks: a broker paying by ACH often writes the load number into it, and that is the most reliable way to know which load a deposit settled. A first connection pulls up to 24 months of history, because the whole point is matching loads that were paid months ago.

We keep a local copy rather than querying live for the same reason a bookkeeper keeps statements: matching needs the whole feed at once, repeatedly, and a reconciliation has to be auditable — when a load is marked paid off a bank credit, we must be able to show the exact transaction row as it read at the time.

What we derive. We identify money you moved between your own accounts, match the remaining incoming credits to loads you hauled, and categorise outgoing charges against a chart of accounts so the product can show you a profit and loss. The matching itself is done by deterministic code, not by an AI model.

Your connection token. Authorising the connection gives us a Plaid access token — a durable read handle on the accounts you selected. It never leaves our servers: it is not sent to your browser, not sent to the Chrome extension, and not returned by any API response. In our database it is sealed with AES-256-GCM under a key held in the API’s environment and never in the database itself, so a copy of the database alone decrypts to nothing.

Disconnecting. You can disconnect a bank at any time from Loadful. Disconnecting stops the sync immediately and revokes the access token with Plaid, so the connection can no longer be used to read your account. Your transaction history stays in your Loadful account, because it is your own money record and the reconciliations already made against it have to remain checkable — tell us to delete it and we will, within 30 days; see Deleting your data below.

We do not sell your bank data. We do not share it with any third party, we do not use it to train machine-learning models, and we do not use it for anything other than reconciling your own book.

QuickBooks Online

This integration is not currently available, and no QuickBooks data has ever been collected. Loadful was built to reconcile against QuickBooks as well as against your bank, and that code still exists, but it is switched off: we hold no Intuit credential, the routes are not mounted, and there is no way to connect a QuickBooks company to Loadful today. We describe it here rather than staying silent because the honest answer to “does Loadful read my books?” is a clear no, not an absence.

If we do turn it on, it will be optional and read-only. We would request the QuickBooks accounting scope (com.intuit.quickbooks.accounting) and use it to read invoices, payments, and the customer names attached to them, so that hauled loads can be reconciled against what was billed. Loadful would not create, edit, void or delete anything in your QuickBooks company, and you would be able to disconnect at any time from Loadful or from within QuickBooks. We will update this policy and notify account holders before that connection is offered — see Changes below.

How we use it

To run the features you asked for — scouting, trip planning, load scoring, bid pricing, outreach drafting, and reconciliation.
To show you your own book: what you hauled, what was billed, and what is still owed.
To operate, secure, debug and improve the service.
To contact you about your account, billing, or a material change to the service.

AI processing

Some features send data to Anthropic’s Claude API: lane scouting, load evaluation, broker-outreach drafting, plain-English explanations of a reconciliation, and expense categorisation. What is sent is the operational context that feature needs — lanes, dates, rates, equipment, broker names, and figures already computed by Loadful.

What that means for your bank data. One feature touches it: expense categorisation. It sends the descriptor text your bank wrote on a transaction — the counterparty name, the merchant name and the memo line — grouped by vendor, with whether the money went out or came in and how many transactions that vendor accounts for, and asks which category the vendor belongs to. Up to three of those descriptor lines go per vendor, as your bank wrote them, because a vendor is only recognisable from the text itself. We name the memo line here rather than hiding it behind “vendor”: it is the same field an ACH sender may write a load or invoice number into, so that text can reach the model. What does not go is the amount, the date, our transaction identifier, the account number or name, and your access token — nothing that ties a descriptor back to a particular payment. What comes back is a category label, checked against our own list before anything is booked.

Anthropic processes this as our service provider and, under our commercial terms, does not use it to train their models. No credential of yours — bank, load board or accounting — is ever sent to a model. Reconciliation itself is performed by deterministic code, never by a model: a language model explains a result, it does not decide which payment settled which load, and it cannot alter a figure.

Other services we rely on

Kinde — authentication and session management.
Supabase — the managed PostgreSQL database holding your account data.
Vercel — hosting for the web application.
Fly.io — hosting for the API.
Anthropic — the AI features described above.
Sentry — error monitoring. Receives crash reports and performance traces, scrubbed of personal and payment data before they leave our systems.
Plaid — the bank connection described above, if you make one. Plaid receives your banking login directly; we never do.
Intuit — nothing, today. The QuickBooks integration is switched off and we hold no Intuit credential.
NOAA (weather) and the U.S. EIA (diesel prices) — public data, queried by location; no customer information is sent.

We may also disclose information where required by law, or to protect the rights, safety or property of Loadful or others.

Security

Traffic between your browser, our API, and the services above runs over TLS. Data is held in a managed database that is encrypted at rest at the storage layer and reachable only by our application credentials. Every query that touches your loads, trucks or bank transactions is scoped to your account id, so one customer’s data is not readable by another. Access tokens issued to the browser extension are short-lived.

Bank connections get one protection beyond that, because they earn it: the Plaid access token is sealed with AES-256-GCM before it is written, under a key held in the API’s environment rather than in the database. Unlike a password, that token has no expiry to run out and no rotation to invalidate it, so a leaked copy of the database must not be enough to read anybody’s bank feed.

No system is perfectly secure, and we do not claim otherwise. If a breach affects your data we will notify you promptly and describe what happened.

Retention

We keep your account and operational data for as long as your account is open, because the product’s value is largely historical — lane statistics, past rates and prior reconciliations. Close your account and we delete or anonymise your data within 90 days, except where we must retain records to meet a legal or tax obligation. Ordinary logs are retained for a shorter period.

Your choices and rights

Access and correction. Most of your data is visible and editable in the dashboard. Ask us for anything that is not.
Export. Ask and we will provide your data in a machine-readable format.
Deletion. Ask us to delete your account or a specific integration’s data.
Disconnect an integration. Remove the Chrome extension, or disconnect a bank connection, at any time. Disconnecting a bank revokes our access token with Plaid.

Depending on where you live you may have additional rights over your personal information, including under the California Consumer Privacy Act or the GDPR. We honour these requests regardless of whether a specific law applies to you. We will not discriminate against you for exercising them.

Deleting your data

Email hello@loadful.ai from the address on your account and tell us what to delete — your whole account, or just a connected integration’s data. We action deletion requests within 30 days and confirm when it is done.

International transfers

Loadful is operated from the United States and your data is processed there. If you access the service from elsewhere, you are transferring information to the United States.

Changes

If we change this policy we will update the effective date above, and for material changes we will notify account holders by email before the change takes effect.

Contact

Loadful, Inc. — questions, requests, or anything in this policy that is not clear: hello@loadful.ai.