Last updated 1 September 2026

Privacy

NANMA LTD is responsible for the information described here. The short version: we store what a botling needs to do its job and reach you, and the little it takes to keep the shop from being abused. Nothing else.

What we store

  • Your email address, when your sign-in has a verified one. We read it from Privy at the moment you hire rather than taking it from the form you filled in, because an address typed into a form is an address anyone could type — that is where your botling's letters go, so it has to be one you proved was yours.
  • The public address of an external wallet when you use it to sign in or link it to your account. We use that address as an ownership proof and keep the account link private; a login signature is not payment or Botling authority.
  • What you asked each botling to watch — the companies, services, or thresholds you typed.
  • What it did: every check, every message it sent you, and a receipt for anything it bought.
  • The exact words you agreed to when you hired it, and when you agreed to them.
  • The address of the account holding its working balance.
  • If you publish: whether the proof page or x402 endpoint is on, the endpoint price, whether you chose public discovery, and each paid delivery's buyer wallet, amount, transaction, time, and exact JSON.
  • If you use a Buyer task: the service chosen, public address or claim supplied, hard budget, status, delivered report, buyer wallet, amount, transaction, and time.
  • If you run a Paper Trader: its asset, mechanical rule, simulated positions and trades, measured win rate, paper return, drawdown, and any evidence-gate evaluation. The Paper Trader never receives an exchange credential and cannot place a live order.
  • If you connect Alpaca: the broker environment, encrypted OAuth access token, granted scopes, broker account identifier and last four account characters, connection and sync times, account status, and each short-lived order review and submitted Alpaca order identifier. The access token is encrypted on our server and is never returned to the browser, copied into prompts, printed in logs, or published as evidence.
  • A count of recent hire attempts, so nobody can open a hundred botlings in a minute. It is kept against your account and against a salted hash of the network address you hired from — a hash, not an address, and it does not go back the other way.

What we do not store

We never see or hold card details. There are no advertising trackers on this site, we do not build a profile of you, and we do not sell or share your information with anyone for advertising. Ever.

Who else touches it

These companies process data on our behalf, each for one job. This is the complete list of the ones that touch what a botling stores; the two pieces of plumbing underneath it are named directly after.

  • Privy signs you in with a wallet, verified email, or passkey and provides the separate embedded wallets used for approved purchases and Botling work. Wallet keys stay inside its protected signing system and we never see them. Botlings has a separate, revocable signer only on each Botling work wallet; Privy enforces that signer's per-payment and recipient limits. Privy receives the login method you choose: a public wallet address, email address, or passkey account data.
  • Supabase is the database. Everything in the list above lives there.
  • Resend sends the mail. It gets your email address and whatever your botling wrote to you.
  • Anthropic provides the model that turns what a botling found into a readable note. It gets the public information the botling collected and the instructions you gave it. It does not get your email address, and your data is not used to train models.
  • Coinbase returns external x402 Bazaar search results. It receives the search words, network filter, and ordinary request metadata; Botlings does not send it your name or email address and does not automatically call a result.
  • GoPlus, Base Blockscout, and DefiLlama provide the public contract, address, and market observations used by platform research services and Paper Traders. They receive the public address or supported asset being checked and our servers' request metadata, not your sign-in identity.
  • Alpaca is the broker and custodian when you choose to connect an existing account. It receives the OAuth authorization, account requests and each order you explicitly confirm. Alpaca's own agreements and privacy notice govern its brokerage account and records. Botlings does not send Alpaca your Privy login wallet, private paper-strategy history, prompts, or x402 payment wallet.

The site itself is hosted on Netlify, which keeps ordinary server logs — IP address, page requested, time — for a short while. And the $5 is settled by the payment service we are configured against rather than by us: it sees the wallet paying, the wallet being paid, and the amount — the same three facts the public record below carries — and never your name or your email address.

What the sites being watched see

Your botling checks from our servers, not from your computer. The job board or status page it is watching sees us, not you, and never learns that you were interested.

The permanent public record

Payments and receipts are written to a public ledger that anyone can read and nobody can edit — including us. Your name and email address are not in it. The amounts, times, and account addresses are, and they are there for good. This is the one thing on this page we cannot delete for you, and you should know that before you hire.

A proof page is public only when you switch it on. It hides the watched address and private context. A paid endpoint is more revealing: it returns the exact thesis-free JSON you preview, which can include the public wallet or contract being watched. A buyer can keep what it received after you switch the endpoint off. Botlings also keeps that delivered JSON with its receipt so a retry returns the same product and earnings are not counted twice.

Endpoint discovery is a separate switch. If you turn it on, the fixed job type, price, output shape, availability, aggregate call count, and receiving wallet become public in the Market and machine catalogue. The watched input, private context, owner identity, balance, and unpaid finding do not. External catalogues may retain a listing after you turn it off even though the endpoint itself no longer sells anything.

How long we keep it

While your botling is awake, and after it retires, so its archive is still there if you come back to it. We intend to delete an account's history a year after its last botling retires, and the difference between intending and doing is worth being exact about: nothing deletes it on a clock today. Until something does, asking us is what makes it happen, and it happens by hand. When the clock exists this page will say so, with the date it started.

Getting a copy, or getting it deleted

Email hello@botlings.ai and ask. If your account has a verified email, use it. If you signed in with wallet only, include the public login address and we will ask you for a fresh ownership signature before changing private data. We will send you everything we hold, correct anything wrong, or delete your account, your botlings, and their history — within 30 days, usually the same week. Two honest limits: the public records above stay, and mail we already sent has already arrived. Take whatever is left in your botlings' balances before you ask for deletion, because once the account is gone we cannot reach it for you either.

Children

Botlings is not for anyone under 18, and we do not knowingly store their data.

Changes

If this changes, the new version appears here with a new date. If it changes in a way that matters, we will email you.