Privacy Policy
This policy explains what 4SAKE Agent Co ("we") collects when you or your agent use FMCSA Carrier Intelligence (the "Service") and this website, and what we do with it. We have no user accounts and collect very little. If you ask for an API key, that is the one time we ask who you are (see below).
What we collect when you call the Service
- Network information. Your IP address, the time of each request, and standard request metadata such as the user agent. We use the IP address for rate limiting and abuse prevention.
- Request details. Which tool you called and the names of the arguments you sent. For paid calls whose payment verified, we also record the argument values, such as the USDOT numbers you looked up.
- Payment details. For paid calls: your paying wallet address, the amount, the network and the blockchain transaction signature. Payments settle on a public blockchain (Solana, Base or Polygon, whichever you pay on), so the transaction is publicly visible on the blockchain independently of us.
- Carrier selection records. When you buy a carrier selection record we keep its hash, the time it was issued, the USDOT number and the data as-of date, so the free verify link can confirm it. We do not keep the record's contents or your wallet address in that registry.
- API key requests and keys. If you ask for an API key through the form on this website, we collect your name, work email, company, role and, if you choose to give it, what you plan to use the key for. We use them only to decide whether to issue a key, to email you the key, to support you and to ask how it is working. We keep them for as long as the key is active and for up to 12 months after the last time it is used or the request is declined, then delete them. If you receive a key, we keep a one-way hash of it (never the key itself), its remaining credit, and when it was last used; calls made with a key are recorded like any other paid call, identified by a short key id. We do not sell this information or use it for a mailing list.
- Outcome. Whether the call returned records, was free, or failed, and how long it took.
- Messages that aren't tool calls. If a message to our A2A endpoint contains no tool call (for example a plain-language question), we log its first 200 characters, so we can see what callers are asking for. These are kept with operational logs, not billing records.
Before a payment verifies, we record only argument names, never values. We do not ask for your name, email address or any account information when you simply call the Service, and we do not use cookies on it. The one exception is a request for an API key, described next.
Why we use it
- To operate the Service, enforce rate limits and prevent abuse.
- To keep an accurate, tamper-evident billing record and reconcile it against the blockchain.
- To investigate billing disputes and refund requests.
- To measure reliability and performance.
- To understand what callers need and improve the Service.
We do not sell this information, share it for advertising, or use it to profile you. We may disclose it if the law requires us to, or to protect the Service and its users.
Where it is kept and for how long
The Service runs on Google Cloud in the United States. Google acts as our infrastructure provider. Operational logs are kept for about 30 days. Billing records (the payment and request details above) are kept for up to seven years, for accounting and dispute purposes. We then delete them or keep them only in aggregate form.
This website
This website is a static site hosted on GitHub Pages. It sets no cookies and runs no analytics or tracking scripts. GitHub may log visitors' IP addresses to operate and secure its service, under GitHub's privacy statement.
Carrier data
The carrier information the Service provides comes from FMCSA's public records about regulated motor carriers as businesses. The Service does not return carriers' names, addresses, phone numbers or email addresses. Requests to correct a carrier's underlying record should go to FMCSA, which is the source of the data. Questions about how the Service presents it can go to the address below.
Your choices
To ask what we hold about a wallet address or IP address you control, or to ask us to delete it where we are not required to keep it, email us from an address we can verify against your request.
Changes
We will post any changes to this policy here with a new "Last updated" date.
Contact
4SAKE Agent Co · the contact address, shown when JavaScript is on