Your privacy controls live in Settings, then Privacy. Account deletion lives in Settings, then Account.
What other people in your workspace can see
Three boundaries, each deliberately narrow:
Workspace owners and admins can see which tools you have connected and whether each connection is live. That is tool names and health only, for example "ClickUp connected, Google expired", never any content from those tools.
When an owner or admin builds or transfers a Binee automation for you, they can always see that automation's configuration and health (its wording, sources, status, and whether it is firing), because they wrote it. They never see what it finds: insights go only to you.
On a shared dashboard, everyone on it sees the same numbers. Cards that read a connected tool use the connection of the person who made them, and ClickUp cards use the dashboard creator's ClickUp connection, private spaces they belong to included: putting a board in front of teammates is choosing to share what it shows. For ClickUp, Binee keeps only the numbers the dashboard displays (counts, 90 days of daily counts, and the task names an overdue card shows), never the tasks themselves. The Binee cards (your insights and automations) always show each viewer their own.
ClickUp is read live, and only ever with your own connection: Binee does not keep a copy of your ClickUp workspace, and like every other tool, what Binee tells you about ClickUp comes from your own ClickUp connection. Chat, your automations, your scheduled reports, and ClickUp Setup read it with your own connection, and Setup builds with it too (its plan-limit check counts all spaces through an owner's or admin's connection, a number only). If your ClickUp connection is missing or expired, these say so and ask you to reconnect instead of using anyone else's. ClickUp's change notifications arrive through one workspace connection, but a change reaches you only when your own connection can open that task: for example, a status change in a private Finance space you are not in never triggers your automations, never appears in your reports or automation tests, and is never named to you. A deleted task can no longer be opened by anyone, and ClickUp tasks can be private even inside a list you can see, so Binee cannot tell who was allowed to see it: deletions never reach anyone's automations or reports. ClickUp content is shared only where a person chooses to share it: a dashboard's ClickUp cards use the connection of the person who made the dashboard, so everyone who can open it sees its numbers as that person sees them, and an automation or report its owner sends to a shared Slack channel shows that channel what the owner's own connection found. What Binee stores about ClickUp: your encrypted connection; the dashboard numbers of each person who made a dashboard, computed with their own connection (chat also uses your own numbers in the background when you have made a dashboard, never a teammate's); short snapshots of the task changes automations react to (for example a status change and the start of a new comment, deleted by a weekly cleanup once 60 days old); ClickUp's raw change notifications (deleted by the same cleanup once 30 days old); links between tasks and the people and companies Binee knows (the task's id and name, used only for matching: before showing you a linked task, Binee opens it with your own connection, so you only ever see tasks you can open, with their current name and status); the restore points ClickUp Setup takes of your structure as you see it (space, folder, and list names with their statuses and task counts; teammates only ever see how many of each a restore point holds); your ClickUp Setup analysis report, saved for you only; and your workspace's ClickUp Setup plans, shared with everyone working on Setup (they name spaces, folders, and lists). The task change snapshots, the raw change notifications, and the task links are kept on Binee's servers only: no member can read them directly, and they reach a member only through the checks above. Anything from ClickUp that becomes part of your own Binee history also stays with it: a chat answer that quotes a task, an insight and the evidence behind it, or the record of an action an automation took, for example the comment it posted.
Nothing else crosses between members: your chats, your insight feed, your memory, and everything Binee reads from your connected tools stay yours.
Training consent
The Improve Binee for everyone toggle controls whether your chats with Binee may be used to make Binee better for everyone. We never share your data with third parties, and nothing Binee reads from your connected tools is ever used for training; only your chats with Binee may be used, and only while the toggle is on. It is off by default everywhere it appears, including the welcome setup page where new users first see it as an unchecked checkbox: nothing is collected unless you turn it on. Consent is recorded at the moment each message is written, so turning the toggle off stops future collection but does not retroactively change what you already agreed to share while it was on.
Chat history retention
The Chat history toggle controls how long conversations are kept:
On (the default): messages are kept until you delete them.
Off: conversations older than 30 days are permanently pruned on a weekly schedule.
There is also a Delete all chat history button that permanently deletes every conversation and message right away. This does not delete your account.
Export your data
The export button downloads a JSON file with your profile, conversations, messages, memories, insights, automations, and preferences. If any part of the export fails, the export fails visibly rather than silently handing you an incomplete file.
Account deletion
Delete your account from Settings, then Account. Deletion is permanent: it removes your workspaces (the ones only you own), your memberships, conversations, memories, connections, and profile. Before anything is deleted, any active paid subscription is cancelled first so you are never charged again; if that cancellation fails, the deletion stops and tells you, rather than deleting the account while billing continues. Your tool connections are also revoked on the provider side, the same as disconnecting each integration yourself. If you own a workspace that still has other active members, Binee refuses the deletion and asks you to transfer ownership first, so a team is never orphaned by accident.