Privacy Policy

Wallet addresses. Signing in means proving control of an address. That address identifies you to us. It is also already public: it exists on a public blockchain whether or not you use Fatstack.

Listings you submit. Name, description, category, endpoint URL, price, payout wallet, optional schema and README. Live listings are published; rejected ones are retained with the reason.

Payment records. Transaction hash, payer address, amount, block and timestamp, read from the public chain and matched to a listing. We observe these; we do not create them.

An optional email, only if a provider supplies one for review notices. Nothing requires it.

A salted hash of your IP address, if you use the “Try it” sandbox, to enforce a daily spending cap. The raw address is not stored. The salt is secret, which matters: an unsalted hash of an IPv4 address is trivially reversible by trying all of them.

Call outcomes — success or failure, per tool — used to publish error rates. Moderation decisions are logged with the reviewing wallet and reason.

No names, no passwords, no postal addresses, no payment card details, no government identifiers. No analytics or advertising trackers. No third-party cookies. We do not sell or share personal data for advertising, and there is nothing here that would be useful for it.

One cookie: a signed session token holding a single value — your wallet address — set after you sign in. It is HTTP-only, secure, same-site, and expires after seven days. Signing out deletes it. There are no other cookies.

Fatstack runs on infrastructure operated by others. Each sees only what it must:

• Hosting, database and edge providers — our application, database and edge network. They process what the service stores and serves.
• An AI provider — the text of a submitted listing is sent for automated screening against prompt injection, fraud and illegal content. Listing text only; never your payment records or session.
• A blockchain node provider — reads public chain data and broadcasts the transfers you authorise.
• A public on-chain sanctions oracle — a provider’s payout wallet is checked against it. This is a read of public blockchain state; no data about you is sent anywhere to perform it.

Proxy-mode traffic. Where a provider chooses proxy mode, requests and responses pass through our infrastructure in plaintext and are therefore visible to us in transit. We do not store request or response bodies. Providers who cannot accept this can run the payment middleware themselves.

We disclose data to authorities only where legally required, and we would not be able to produce most of what such a request might assume exists.

Payments happen on a public blockchain. Transaction hashes, wallet addresses, amounts and timestamps are recorded there permanently, replicated worldwide, and readable by anyone. Fatstack did not put them there and cannot remove them.

If you ask us to erase your data, we can delete what we hold — listings, the optional email, our copy of payment records, moderation notes. Your on-chain history will remain, because no one has the ability to alter it. Treat every payment as public and permanent, because it is.

Listings and moderation records are kept while a listing exists and afterwards as a record of decisions taken. Payment records are kept as long as the service operates; they mirror public data. Sandbox IP hashes are kept only as long as the daily cap they enforce needs them. Session tokens expire after seven days.

Depending on where you live, you may have rights to access, correct, export or delete personal data we hold, to object to processing, or to complain to a supervisory authority. Write to message@fatstack.net and we will respond.

Two honest limits. We identify you by wallet, so a request has to come from an address we can verify you control. And as above, we cannot delete the blockchain.

We never store private keys belonging to users. Sessions are signed tokens rather than server-side records. Sandbox IP addresses are salted and hashed. Admin access is restricted to an allowlist of wallet addresses and is never inferred from anything a browser sends.

No system is immune. If a breach affects you, we will say so — plainly and promptly — rather than minimise it.

Material changes will be published here with a new revision date. The date at the top always reflects the current version.

Questions about this document: message@fatstack.net.