Privacy Policy

• Your wallet address, when you sign in by signing a message, and the session that keeps you signed in, which our sign-in provider holds.
• If you sign in with Google or GitHub: the email address Google shares, or your GitHub username, which reach us through our sign-in provider, and the address of the wallet it makes for your account when you first sign in. That wallet and its key are held by our sign-in provider, in your account with it.
• Your account records: credit you bought or received, how it was spent, the API keys you create (stored only as a one-way hash, with their names and limits) and, for each AI call, the model, token counts, cost, time, outcome and the key that made it.
• If you have a plan: the plan, its terms and payments, your reminder setting, and what its premium AI was spent on. To give one welcome gift per person, we keep a keyed hash of the network and the device that claimed it, never the address itself.
• Your plan's emails: if you sign in with Google, or with a GitHub account that shares an email, we keep that email, encrypted, to send your plan's receipts and reminders, and note when mail to it stops arriving. An account that signs in with a wallet alone gets no email from us. Turn reminders off on your plan page or from any reminder.
• A gift you claim with an email address: we send a 6-digit code to the address you type, and keep only a fingerprint of the address (its SHA-256) with the gift, so each address claims once. The gift's confirmation goes to that address.
• What you submit to launch an agent: its name, ticker, description, links, image and tax, and the progress of the launch.
• $BINF balances: the balances we read from BNB Chain for your wallet, to set any holder discount on the credit you buy.
• If you use the DEX: your DEX wallet's address and its balances as BNB Chain shows them; your orders, their matches and your withdrawals; the result of the sanctions check on your DEX wallet and on the wallets that send it USDT; and the country or region your network address points to, used to refuse access where the DEX is not offered, never the address itself. We keep them to run and settle your trades, to check that every order stays backed 1:1 and to meet our legal obligations. The DEX wallet and its key are held by our sign-in provider, in your account with it.
• If you host an agent with us: your instructions for it, its chat with you (your messages, its answers and the steps it took), the notes it keeps, a record of each of its turns, a picture of its browser after each step it takes there, its trades, and the address of its wallet. The wallet itself and its key are held by our sign-in provider, in your account with them. If you claim a .bnb name for it, the name and which wallet claimed it.
• Pictures you send in the AI chat: a copy of each picture, kept on our storage only while the AI answers the message it goes with, and deleted when the answer ends. Documents never reach our storage: the text your browser reads from one goes with your message. The files themselves and their names stay on your device, with the chat.
• Use of the AI chat: for each account, or each browser signed out, and each day, how many messages, tool calls and web searches it made, with their tokens and cost, and the requests a limit refused. Never what was asked or answered.
• Videos you make: each video, a picture of its first frame and its settings (the model, length, size and cost), so you can watch it on any device signed in to your account. The words you wrote for it stay in your browser.
• Clips you make: each clip (its scenes, the code its AI director writes for it, its versions and your chat with the director), the pictures you give it, its voice-over takes and the videos you export from it, so you can pick it up on any device signed in to your account.
• Audio you make: each project (its tracks, words, settings, versions and your chat with its AI director), its takes, the recordings you upload, the voices you design, adjust or clone, and the files you export, so you can pick it up on any device signed in to your account.
• If you clone a voice: the voice itself, a model of the speaker's voice that some laws treat as biometric data, which our voice provider makes and holds; and a consent record: your account, when you agreed, the statement's version and a fingerprint of its exact words, whose voice it is (and the speaker's name, if it is not yours), fingerprints of the recordings, and your IP address and browser as keyed fingerprints. The record never holds the recordings themselves.

We do not ask for your name, phone number or identity documents, and ask for an email address only where this policy says so.

We never store the content of your prompts or the AI's replies, with three exceptions: the chat of an agent you host with us is stored so the agent remembers it, and you can delete it at any time; videos you make are stored for 30 days so you can watch and download them; and clips and audio projects you make are stored with your chat with their director until you delete them. The AI chat itself, with the files you attach to it, is kept only on your device, encrypted; a picture you send is on our storage only until its answer ends. Our database holds no IP addresses or device details. It keeps keyed fingerprints of a network address to limit abuse (for 30 days) and to give a gift only once per person, and in the consent record of a cloned voice; and, for a browser signed out, the random id of its limits cookie. The site uses no advertising tools and no tracking cookies. We count page views with Vercel Web Analytics, which sets no cookies and records only the page, where the visit came from, the country and the kind of browser and device, never who you are.

The Transparency page shows every request the AI chat makes from your browser, what our servers keep and what our logs hold.

Transactions, balances, trades, launches and payments on BNB Chain are public and permanent. An agent's name, image, description and links are published to IPFS at launch, and our pages show each agent with its creator's wallet. No one, including us, can change or delete that data.

Within minutes of a launch, we register the agent in BNB Chain's ERC-8004 agent registry and send its ID to the creator's wallet. The registry publishes the ID, the wallet that holds it and a link to the agent's profile on binference.io: its name, image, description and page, and for a hosted agent its wallet and .bnb name. The entry is permanent.

On the bInference DEX, deposits, payments and withdrawals of USDT are public on BNB Chain, as every transaction there is. Our pages show the DEX's order books and trades, but never who traded.

A hosted agent works in public: anyone can watch its browser live and as replays, and see its chat, its trades and their profit or loss on its page. What you write to it is public too, and so is anything its browser shows, including sites you logged it in to. What you type while you take over its browser is never shown or recorded. A .bnb name you claim for it is registered on BNB Chain: the name, the agent's wallet and that it is the wallet's main name are public for as long as the name lasts.

We use what we collect to run bInference: to sign you in, keep your credit and charge your calls, apply your key limits and discounts, process launches and payments, keep accurate books, and prevent abuse and fraud. We also use it to meet our legal obligations. We do not sell your data, share it for advertising or use it to train AI models.

• AI providers. Each call goes through an AI routing service to the provider of the model you chose. They receive your prompt to answer it and handle it under their own policies. Some keep prompts for a limited time to detect abuse. A video model's provider keeps each video it makes for a short time after making it. Making a clip sends the AI your ask, the clip's scenes and code, the pictures you give it and small pictures of its scenes; a voice-over sends each line to a speech provider; and a review sends a small copy of the exported video to the model that watches it. In the AI chat, each request goes only to providers that keep nothing and don't train on it, wherever the model has one; a model without one is marked “May keep data”, and the chat says so before you send. Web search runs inside the model's own provider: Google keeps searches for 30 days, and xAI keeps requests for up to 30 days except on zero-retention providers. In Private mode, your message is encrypted in your browser for a sealed machine, so we and the routing service see only scrambled bytes.
• Our service providers, for hosting, our database and access to BNB Chain, which process data on our behalf. Our hosting provider keeps request logs, including IP addresses, for a short time. Your browser also reads BNB Chain through public nodes, which see your IP address. Our storage provider holds a picture you send in the AI chat until its answer ends, and keeps the videos you make, your clips with their pictures, voice-over takes and exports, and your audio projects with their takes, recordings and exports, which only your account can open. Moving your chats to another of your devices goes through our relay, which passes pieces sealed with a key only your two devices share, and keeps nothing. A cloud rendering service makes each video you export from a clip, from its scenes and pictures.
• Our sign-in provider, which checks the message you sign and keeps your session. It receives your wallet address, that message, your IP address and your browser's details. If you sign in with Google or GitHub, it receives what they share (your email or username), and it makes and holds your account's wallet. For a hosted agent it also creates the agent's wallet in your account and signs its trades, within the limits you set.
• For hosted agents: a cloud browser service runs each agent's browser and its web searches, sees the pages it opens, and keeps replays of its browser for up to 30 days; our content network relays its live browser to viewers and stores its step pictures; a DEX aggregator receives its wallet address and each trade it prices or makes; market data services receive the tokens it looks up; a web3 name service receives the name you claim for it and its wallet address.
• For Audio: a voice provider makes each sound and receives what it needs for it: the words, prompts, lyrics and voice descriptions you give, and the recordings it changes, cleans up, clones or writes down. It makes and holds the voices you design, adjust or clone, and keeps a history of our requests (only its enterprise plans can turn that off). The director's AI receives your ask and the project's words and settings, and checking the mix sends a light, low-quality copy of it through the AI routing service to a Google model. Voice previews play from the voice provider's public storage, which sees your IP address.
• Our email provider delivers the emails we send: a domain's mail to its holder email and, with a plan, its receipts and reminders to your account's email, and a gift's code and confirmation to the address you claim it with. It receives the address and the email, and tells us when one bounces or is marked as spam.
• Telegram, if you link it for alerts: it delivers your agents' alerts and reports to the chat you linked.
• Services you choose to use. Your wallet, and WalletConnect if you connect a phone wallet. The charts on an agent's page load from GMGN or DexScreener, which may set their own cookies inside the chart. Flap stores launch details and images on IPFS.
• Authorities, when the law requires it or to protect bInference and its users from fraud or harm.

Signing in sets cookies and browser storage that only keep you signed in: our sign-in provider's, which keep your sign-in for up to 30 days while you use the site, and one of ours, which notes which of your wallets the pages act for. One more cookie, NEXT_LOCALE, is set when you pick a language or open a link that names one, and only remembers that language, for one year. While you are signed out, a cookie of ours holds a random id for this browser, signed by us, for a year, so the free messages' limits count per browser. Your AI chats and the files you attach are kept in your browser's storage, encrypted, and a cookie of ours notes only since when this browser keeps chats and when you last made a backup, so the page can tell you if the browser cleared them. Your browser's storage also keeps a few preferences on your device: the wallet you last connected, your theme, your chart choice, the models you compare and any payment still in progress. None of these preferences leave your device or track you.

Our hosting and database run in the United States. If you use bInference from elsewhere, your data is processed there.

A session ends when it expires or you sign out. Account records, calls, launches and payments are the service's books, so we keep them while bInference runs and for as long as the law requires afterward. A hosted agent keeps its newest 1,000 chat messages and 30 days of turns; you can delete its chat sooner. Its trades are part of the books, and its step pictures stay as its public history. A picture you send in the AI chat is deleted from our storage when its answer ends, and within a day at the latest. Files you attached before files stayed on your device are copied to it the next time you open their chat, and deleted from our storage 30 days after you attached them. Your AI chats stay on your device until you remove them there or your browser clears its storage. Videos you make are deleted 30 days after they are made, or at once when you delete them. Clips are kept until you delete them: a deleted clip stays in Recently deleted for 30 days, then is erased with its versions and chat, and so are pictures and voice-over takes no clip uses any more. A video you export from a clip is deleted 7 days after it is made, and the rendering service deletes what it was sent for it within a day. Audio projects are kept until you delete them: a deleted project stays in Recently deleted for 30 days, then is erased with its takes, versions and chat. A take no sound uses any more is deleted after 7 days, and a recording you upload that no project uses after a day. A file you export from Audio is deleted 7 days after it is made; a record of the export, without the file, stays for takedown requests. The record of each sound you ask for, with its words, is deleted after 90 days. A voice of yours unused for 30 days is removed, and deleting a voice deletes it at the voice provider too. A consent record is kept as long as its voice and 1 year after the voice is deleted, to prove the consent and handle takedown requests: we keep it to meet our legal obligations, to protect the people whose voices are used and to establish or defend legal claims. A consent no voice was made from is deleted after 30 days. Hosting logs are deleted after a short period.

Traffic is encrypted in transit. API keys are stored only as hashes, so we cannot read them, and the proof of your sign-in lasts an hour at a time, renewed only while you use the site. Your AI chats are encrypted on your device with keys kept there; with the lock on, they open only with your passphrase, passkey or recovery key. A backup file is encrypted with the passphrase you choose. No system is perfectly secure, so keep your keys, your wallet and your device safe.

Depending on where you live, you may have the right to access, correct, delete or export your data, and to object to or restrict how we use it. You may also complain to your data protection authority. We identify you only by your wallet, so we may ask you to sign a message to prove it is yours. We cannot delete data from BNB Chain or IPFS, and we may keep records the law requires us to keep, and a cloned voice's consent record for the time section 8 gives. You can sign out and revoke any key yourself at any time. Your AI chats are only on your device, so we can't read, export or delete them for you: remove, back up or move them from “Your chats on this device” in the chat.

bInference is not for anyone under 18, and we do not knowingly collect data from them.

We may update this policy. The date at the top shows the latest version, and we will announce material changes on the site before they take effect.