Most plans get 2x until Dec 7.

See plans
Bond

Privacy Policy

Last updated 6 November 2026

Bond is a Discord bot that administers a server from a plain-language request.

1. Introduction

This policy says what reaches Bond ("we", "our", or "the Service"), what we store, who else sees any of it, and how to have it deleted.

2. Information we collect

Discord data. Bond receives your Discord user ID and username, the ID of the server it is used in, and the ID of the channel a request came from.

Bond uses the text of a message in three cases:

  • You mention Bond, or reply to one of its messages. That message is your request to it
  • An automation a server admin built reacts to messages in that server
  • A member asks Bond to read a channel they can already open. One read call returns at most 100 messages, and a channel the person asking cannot open is refused

Discord delivers every message in every channel Bond can see. Bond keeps nothing from a message, and sends nothing from it anywhere, unless one of those three cases applies to it. Nothing else opens a channel to Bond, and it cannot read a server it has not been added to.

Stored data. We store:

  • Your conversations with Bond, in Discord, in the dashboard and through an AI app you connected, including what Bond read from the server to answer you
  • Memories Bond keeps about a server, and the instructions an admin writes for it
  • Automations: the flows and custom slash commands a server builds, and the data those automations write to their own stores
  • A log of recent automation runs, capped per automation and pruned as newer runs arrive. It can include the message that set a run off
  • For each deleted flow: its name, when it was deleted, from where, and the Discord ID of whoever asked, so Bond can say what happened to it
  • Tool permissions you have granted per server
  • Server subscription status and token pack balances
  • Usage counts for allowances and rate limits, plus analytics events recording which features get used
  • When you open this website, the kind of site that sent you (a category such as a search engine, not the full address), the utm_source tag, which page you landed on, and whether a browser or an automated tool opened it, once per visit and with no account or address attached. When you click an install link, the same again with the page you clicked from. Neither sets a cookie or stores anything in your browser
  • Payment history, as transaction IDs rather than payment details
  • If you cancel a plan or remove Bond from a server you paid for, a record that Bond asked why: which plan or server it was about and whether the DM reached you, kept even if you never answer. If you do, the reason you pick and anything you type under Other. We keep it with the payment records
  • Images Bond generates, in object storage, and the prompt that made each one, shortened to 180 characters
  • Server logs of what Bond did, which we read to fix errors
  • Your Discord sign-in session, if you use the dashboard
  • A record that you ran /opt-out, that a direct message went out, and that Bond relayed a message for someone. None of those three holds any message text
  • If you connect ChatGPT, an encrypted OpenAI authorization credential, account email, plan type and selected model
  • If you connect an AI app to Bond's MCP server (Claude, ChatGPT or another MCP client): the app's name, what you allowed it to do, when you connected it and when it was last used, the list of your servers Discord gave Bond when you signed in, and the tokens Bond gave the app, stored only as hashes. For each call the app makes, a log row with your Discord ID, the server, the tool's name, the app and the outcome. That row holds no arguments, no results and no message text
  • If a server runs a custom bot: the encrypted bot token its owner gave us, the agreement they accepted, and the dates the custom bot served the server

3. How we use your information

  • To carry out your server management requests
  • To keep your permission preferences across sessions
  • To enforce weekly allowances and server safety limits
  • To take subscription payments through Polar.sh
  • To make Bond's answers better

We review conversations with Bond, with help from an AI model, to find and fix bugs. Those copies leave out the channel messages Bond read. The review files bug reports, and a bug report may quote what a member asked Bond.

We do not review conversations from servers that run a custom bot. Nothing from those servers goes into our analytics of how Bond is used or into our tests.

We do not sell any of this, and we do not share it with advertisers or data brokers.

Bond also refuses to profile a member. It will summarize a channel, find what someone said on a topic, count who posted most, or show one member's posts so an admin can review their conduct. It will not write a personality profile, guess at someone's beliefs or private traits, or work out who is close to whom.

4. Third-party services

Bond sends data to these companies:

  • Discord, which the bot runs on
  • OpenAI, Anthropic and OpenRouter, for the requests Bond makes to the language model to answer you. The model is OpenAI's or, for some requests, Anthropic's Claude; each request goes to OpenAI or Anthropic directly or through OpenRouter, which limits it to model hosts that do not train on what they receive. Neither OpenAI nor Anthropic trains on what Bond sends it. A host may keep a request for a short time to watch for abuse, under its own policy; for OpenAI and Anthropic that is up to 30 days. We do not train any model on Discord data
  • Image generation, which is separate and which the no-training limit above does not cover, because we cannot yet confirm it for the hosts of these models. Bond generates pictures through OpenRouter (Google's Gemini 3 Pro Image and OpenAI's GPT Image 2), and, for age-restricted models, through Venice AI, Replicate and TAMS. An image prompt is written by Bond, in a run that may have read a channel first, so it can carry text drawn from messages
  • Tavily, which runs Bond's web searches. It receives the search query Bond writes, and nothing else
  • Anthropic, whose Claude model helps review conversations with Bond to find bugs, as section 3 describes, and never for servers that run a custom bot
  • Polar.sh, for subscriptions and payments
  • OpenAI, if you turn on the optional ChatGPT connection: your prompts and the relevant conversation context go to OpenAI through Codex and count against your own ChatGPT allowance. If you connect your own ChatGPT account, OpenAI's retention and training settings for that account apply instead
  • An AI app you connect, if you connect one to Bond's MCP server. It receives what each tool it calls returns: what your own Discord permissions already let you see in that server, and Bond's own data for it. The app never gets your Discord token. What the app does with what it receives is under that app's privacy policy, not this one
  • Cloudflare, whose R2 storage holds the images Bond generates
  • Our hosting provider, for the server and the database

When Bond asks you to approve an action, it also sends your recent request text, the tool name and the action's details to a scoring model, under the same no-training limit. It never sends tool results, fetched messages or search results. We store the score beside your answer and use it to work out when Bond needs to ask at all.

5. Data retention

We keep what section 2 lists until it is deleted. The automation run log is the exception: it holds only recent runs and drops the rest as newer ones arrive.

The record of a deleted flow is deleted after 30 days.

When Bond deletes or replaces a memory on its own, we keep a copy for 30 days so it can be restored. When you delete a memory, it is gone at once.

Run /clear in a channel to delete your conversation with Bond in that channel, including what Bond read to answer you. It leaves your conversations in other channels alone, and it never touches anyone else's.

Remove Bond from a server and it stops receiving anything from that server. We keep that server's automations and settings so a re-invite restores them, so removal is not deletion. Ask us and we will delete them.

There is no delete-my-account button. Email contact@bondbot.gg and we will delete what you ask us to.

If you connect ChatGPT, we keep the encrypted authorization credential while the connection is off or your Bond plan is inactive, so you do not have to sign in again after resubscribing. Disconnecting ChatGPT deletes it.

If you connect an AI app to Bond's MCP server, the log row for each call is deleted after 30 days. Disconnect the app from Connected apps in the dashboard and its access ends at once. We keep the record of the connection, marked as ended, until you ask us to delete it.

When a custom bot stops for good, we delete its token once it has left the server, and delete what we received through it within 7 days. The custom bots section below says what we keep.

6. Data security

The database listens on the server's loopback address only, so nothing on the network can reach it. The dashboard and the API are served over HTTPS. We encrypt a stored ChatGPT credential with AES-256-GCM before it reaches the database, under a key the database does not hold, and the decrypted copy lives only for the length of one request. A custom bot's token is encrypted with AES-256-GCM before it reaches the database, under a key the database does not hold, and is never shown back. The dashboard signs you in through Discord; our internal admin pages are limited to the bot's owner. No method of transmission over the internet is completely secure.

7. Your rights

You have the right to:

  • Ask for a copy of your stored data
  • Ask us to delete your data
  • Revoke tool permissions at any time with the /permissions commands
  • Remove Bond from your server, which stops it receiving anything from there, and ask us to delete what that server left behind
  • Disconnect ChatGPT at any time, which deletes the stored credential
  • Disconnect an AI app you connected to Bond at any time, from Connected apps in the dashboard

Message content. Run /opt-out and Bond stops reading your messages for any AI request. Wherever Bond reads a channel after that, your messages arrive without their text, attachments or embeds. Bond also skips any write that would copy that text, or a phrase or long word from it, into a log, a value in an automation's data store, a memory, or a run it has scheduled for later. That check looks for copies, so an automation an admin built that splits a message into single words first, a word counter for example, can still keep those words. Writes that do not carry your message text still happen: an automation can add one to a tally of your posts and keep your XP, your level and your name, because none of those is your message. Three things do not change. Rules an admin set up for the server still check your posts, so opting out is not a way around them. Bond still reads a message where you mention it or reply to it, because that message is your own request. And an automation an admin built can still repost one of your messages inside Discord, to a log channel for example, where the same people could already see it.

/opt-out covers every server Bond, or a custom bot powered by Bond, runs in, not just the one you run it in. Only you can undo it, with /opt-in. No admin, and no part of Bond, can opt you back in. Both commands work in a DM with Bond as well as in a server, and neither needs a Discord permission. Messages Bond read before you opted out stay in those conversations until they are cleared.

To exercise these rights, contact us at contact@bondbot.gg.

8. Children's privacy

Bond is for people aged 13 and over, or older where Discord sets a higher minimum. We do not knowingly collect information from children.

9. Changes to this policy

We may update this policy. We will tell users about significant changes through our Discord server, and we will update the date above.

10. Contact us

If you have questions about this policy, contact us at contact@bondbot.gg or join our Discord server.

Custom bots

Some servers run Bond under their own Discord application, called a custom bot. The server's owner created that application and gave us its bot token, and we run it for them as their service provider under Discord's Developer Terms. Everything in this policy applies to a custom bot, with these differences.

  • We use what reaches us through a custom bot only to run that bot for its owner. We do not review those conversations, count them in our product analytics, or use them in our tests
  • The owner may turn on Discord's Message Content setting for their bot. With it on, the bot reads messages in the channels it can see, in the cases section 2 lists. With it off, the bot reads only messages that mention it or reply to it, and DMs
  • /opt-out works the same way on a custom bot, and covers every server Bond or a custom bot powered by Bond runs in
  • We do not train any model on what a custom bot receives. Requests to the language model go to OpenAI or Anthropic, directly or through OpenRouter, under the same no-training limit as Bond's own. Image generation, web search and the optional ChatGPT connection work as section 4 describes
  • If a member connects an outside AI app to Bond through MCP, what it reads in a custom-bot server goes to that app under the app's own terms. With Message Content on, that can include channel text
  • When a custom bot stops, we delete its token once it has left the server and delete what it received within 7 days. We keep the server's automations and settings if its owner told us to, opt-out records, and safety logs that hold only IDs and expire within 30 days
  • To have a custom bot's data deleted, ask the server's owner, or email contact@bondbot.gg

The owner's agreement with us is the Custom Bot Service Provider Agreement.