Privacy

Effective 15 October 2026

This Policy

ZEAM Labs, LLC (“ZEAM Labs”, “we”, “us”) operates the websites zeamlabs.com, zeamprism.com, zeampass.com and zeambridge.com, the ZEAM :: Prism endpoint at mcp.zeamprism.com and the ZEAM :: Bridge and ZEAM :: Pass services at api.zeampass.com. This policy says what they collect, why, who else receives it and how long we keep it.

The same policy is posted on every one of those sites. Every section is shared except the last, which covers the product of the site you are reading. The product sections of all of them are part of this policy: zeamlabs.com, ZEAM :: Prism, ZEAM :: Pass and ZEAM :: Bridge.

The Short Version

We keep server logs. They hold IP addresses. They stay on our servers.
No cookies, no third-party analytics or ad trackers, no accounts and no profiles.
We do not sell or share our logs. Cloudflare carries the traffic as our network provider.
A wallet address, or the address of a pass a wallet funded, is the only lasting identifier the paid services use.
We never hold your money.
Payments settle on Base, a public blockchain. Anyone can see them.

Server Logs

We keep server logs to run and secure our services and to understand the traffic to them, including who visits and which agents call. There are three kinds, and they are kept for different lengths of time.

The front web server’s log. Every request to every site and service passes our front web server. For each request it records the IP address, the time, the method, the full address requested including any query string, the status, the size, the referring page, the user agent and how long the request took. When a request fails, its error log records the IP address, the request and the error. These logs rotate once a day, on days they are not empty, and we keep 14 rotated files and then delete the oldest. A line is normally deleted about 15 days after it was written. A log that has days with no requests keeps its lines longer, because an empty day is not a rotation. Our backups do not copy these logs.

Each site’s own web server log. Behind the front web server, each site’s own web server keeps a request log: the time, the address requested, the status, the size, the referring page and the user agent. It can also hold your IP address. This log is not rotated and has no fixed period. It is deleted when that site’s server is replaced, which happens at some deploys and not at others, so it can be days or months old.

Each service’s process log. The product section says what each service writes to its own log and how long that log lasts.

The one exception is a request that carries a credential in its address. The product section names it, and we do not log it.

How We Use Information

To serve and bill paid calls, and to reconcile what was charged against what settled on chain.
To return unspent balances to the wallets that funded them.
To enforce free limits and rate limits, and to prevent abuse.
To keep the Service secure and to debug it.

We do not build profiles, advertise, or use it for anything else.

We do not sell, rent, trade or share our logs or any other data. The only others who receive it are:

Cloudflare, our network and content delivery provider. Traffic to our public sites and services passes through Cloudflare on its way to our servers, so Cloudflare sees each request, including your IP address and the full address requested. Cloudflare also asks your browser to report failed connections to Cloudflare.
Base, the public blockchain every payment settles on. What goes on chain is public by the nature of the chain. Our services reach Base through our own node, or through Base’s public endpoint when our node is behind.
Sellers. When you call or pay a seller that is not ZEAM Labs, the call and the payment go to that seller’s own server. The product section says what the seller receives, and the seller’s own terms cover what it keeps.
Anyone the law requires us to disclose to.

Chain Data Is Public

Payments, deposits and returns settle in USDC on Base. The wallet addresses, the amounts and the times are public and permanent. Neither we nor you can remove them. If that matters to you, pay from a wallet you are willing to have associated with the Service.

How Long We Keep It

The front web server’s logs: 14 daily rotations and the current file. Normally about 15 days; longer for a log with days that had no requests.
Each site’s own web server log: no fixed period. Deleted when that site’s server is replaced.
Each service’s process log: as its product section states.
Counters for free limits and rate limits: they count one hour at a time. An old count is dropped when a newer one replaces it, and a count kept only in memory also when the service restarts, as the product section states.
Records of payments and passes: kept for accounting and to return balances. They have no automatic deletion date.
On-chain records: permanent, by the nature of the chain.

Your Rights

You can use the websites without connecting a wallet, and you can stop new collection at any time by ceasing to use the Service.

Write to [email protected] to ask what we hold about a wallet address, a pass or a payment, or to ask us to correct or delete it. If you are in the European Economic Area or the United Kingdom, you have rights under the GDPR, including the rights of access, correction and deletion, and you can exercise them at the same address.

We cannot delete anything on chain. A payment record is what lets an unspent balance be returned, so take the balance back before you ask us to delete the record.

Changes

We may update this policy from time to time. Changes are posted on every site named above with the same new effective date.

Contact

ZEAM Labs, LLC · [email protected]

A Delaware limited liability company, file number 10206382.

ZEAM :: Bridge

zeambridge.com is static pages. It sets no cookies, uses no browser storage, and runs no analytics and no third-party scripts. Its typeface is served from the site itself.
The plugin runs on each seller’s own server with the seller’s own keys. We do not run seller servers. A seller receives the calls an agent makes, the network address they come from, the paying wallet’s address, the pass’s address where a pass pays, the signed payment and any grant. The seller’s own terms cover what it keeps.
What a seller’s plugin sends us. When it takes payments: the transactions it has signed, for the relay to send, with the address of the seller’s split. When it buys gate credit: the number of checks, the seller’s name in the plugin, the seller’s payout address and the payment. Gate checks run on the seller’s server and never reach us. The WordPress plugin also asks zeampass.com whether a new version exists, at most every 12 hours.
Relay. It sends transactions to Base. It keeps one state file, so that its gas rules hold across a restart. The file holds, for a paying wallet’s address, the times in the last day that a deposit or payment it signed failed on chain; for a seller’s split address, the gas the relay paid for it in the last day and the fees earned on what the relay sent for it; and for a channel id, how many deposits the relay sent into it, the gas of the refunds or exits the relay paid for, and the transaction hashes of deposits a pass service sent. These are addresses, channel ids and transaction hashes that are public on Base, and counts: no name, no IP address and nothing of a call. The times of failures and the last day’s gas drop out after a day; the totals for a split and for a channel have no automatic deletion date. Its log records batches of transactions it sends, by transaction hash, its own gas balance, and errors with the request’s contents removed. It logs no IP address. The log rotates out once it passes 250 MB.
Credits. It sells gate check credit. It keeps one file on disk for each purchase, so that a payment is never taken twice and a note asked for again is sent again: the address that paid, the payment it signed, whether the payment has settled, and the credit note issued for it, which holds the seller’s payout address, the seller’s name in the plugin, the number of checks, when it was issued and the transaction. These files have no automatic deletion date. Its log records the number of checks, the seller’s name in the plugin, the seller’s payout address and the transaction, and rotates out once it passes 250 MB.
The front web server logs requests to the relay and to the credit service as it does every request. The address of a credit request carries the number of checks, the seller’s name and the seller’s payout address.