Privacy
Your email is held by Buttondown only to send you Banquish's updates. You can unsubscribe any time.
The site's analytics set no cookies.
Each visit to the home page, each read of banquish.space/agent.md and each download of Banquish is counted with the tag of the link it came from, such as ref=x in https://banquish.space/?ref=x. The count holds only that tag and whether a browser asked for it: no IP address, no cookie and nothing else from the request.
The Banquish app
Banquish sends one anonymous count a day to ping.banquish.space, one more the first time an agent connects to it, one as you first reach each setup step before that, and one when you answer or skip its question about where you heard of it, with exactly these fields:
- a random install id, made when Banquish first opens
- the app version
- the macOS version
- how many Workspaces agents finished since the last count
- how many Workspaces you kept and opened again since the last count
- whether an agent connected to Banquish since the last count
- which kinds of agent connected since the last count: Claude Code, Codex, Claude Desktop, ChatGPT, Claude on the web or phone, or another
- once, your answer to "Where did you hear about Banquish?", which Banquish asks after an agent first connects, or that you skipped it
- until an agent first connects, the setup steps reached since the last count, each once: which of Claude Code, Codex, Claude Desktop, Cursor, VS Code, Gemini CLI or pi Banquish found on your Mac, or none, and whether you chose Add or Undo, copied the first question, the configuration or the agent.md line, opened Connect for a chat app, were shown a Pairing code, paired a chat app, made a Panel yourself, chose Not now, or continued from there at a later launch
It never sends sites, page addresses, titles, content, or an agent's name, version or account, and the count is stored without your IP address.
To turn it off, uncheck Send Anonymous Usage Count in the Banquish menu. While it's off, Banquish counts and sends nothing.
From its first launch until an agent finishes your first Workspace, Banquish shows an Example Workspace, which loads two public pages without signing in: Windy's wind map (embed.windy.com) and TradingView's Bitcoin chart (s.tradingview.com). Loading them sends those sites what any page load does, such as your IP address. Banquish sends them nothing else.
If you choose Open this when I log in to my Mac after your first Workspace, Banquish adds itself to your Mac's login items, and when you log in it opens and shows that Workspace. It sends nothing for this. To stop it, uncheck Open at Login in the Banquish menu, or remove Banquish in System Settings, General, Login Items.
Send to Banquish
Send to Banquish, Banquish's extension for Chrome, does nothing until you press its button or its menu item, and then only on that tab, where it reads the page to show you its parts.
When you press Add Panel, it sends that page's address and the parts you picked to the Banquish app on the same Mac, over Chrome's native messaging, and nowhere else. Nothing goes to Banquish's servers.
Banquish uses them only to make that Panel. They're never sold, shared or used for anything else.
The use of information received from Send to Banquish adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Shares
Nothing becomes a share until you choose Share Workspace… and then Create Link. A share lets anyone with its link open a copy of the Workspace in their own Banquish, and holds exactly:
- an image of the Workspace as it was on screen, with Panels from Private sites covered
- the Workspace's name
- its Notes in full, links included, and where each one sits
- the Prompt, if you leave one in the Share sheet
- each Panel's page address and page title, in full, as the Share sheet lists them
- where each Panel sits, which parts of its page it shows, and how they're shown
- what finds those parts on the page again: their headings, labels, ids, link addresses and the words around them, without the values they showed, such as prices or counts
- the clicks that bring back what each Panel shows, such as opening a tab or a section
Panels from Private sites are left out entirely. A share holds nothing you typed or chose in a form, no cookies, and none of a page's saved state.
Anyone with the link can see the share, including every shared page's address and title, and can open a copy in their own Banquish, where each page loads in their own sign-ins. It isn't listed anywhere, and search engines are told not to index it.
The server keeps the share, a hash of your install's share key, and the times: when the share was made and deleted, and when your share key was first used. The share key is made the first time you share, and it's separate from the usage count's install id.
Uploading a share is the only time Banquish's servers read your IP address. It's used only to limit how many shares one address can upload a minute, and it's never stored or logged.
A share is kept until you delete it or it's taken down. To delete one, choose Shared Links… in the Workspace menu, then Delete. Its link stops working at once: the page, its images and its Workspace data answer 410 Gone. Copies already opened in someone's Banquish are theirs, and deleting the share doesn't change them.
To report a share, use the Report link on its page, or write to hello@banquish.space with its link. To have a share deleted when you no longer have the Banquish that made it, write to the same address.
Sites that showed a preview of the link, such as X, Slack or iMessage, may keep their own copy of the image and name. Deleting the share can't reach those copies.
The Relay
When you pair ChatGPT or Claude on the web with Banquish, their agents reach Banquish on your Mac through the Relay at mcp.banquish.space. They get what agents on your Mac get, signed-in pages included, and Private sites stay hidden from them as from every agent.
Banquish connects to the Relay only while you have a Pairing or a Pairing code is showing. With neither, nothing goes to the Relay.
The Relay stores no call content. It passes each call through in memory, and keeps only:
- your Mac: its id, and a hash of the secret Banquish made for it
- each Pairing: its token records, your Mac's id, the chat app, when it was paired and last used, and how many calls it made this minute and this day
- each Pairing code: a hash of it, your Mac's id, the chat app it's for, when it expires and whether it was used, until a day after it expires
- each network address that enters a code on the Pairing page: when it tried, and how many wrong codes each sign-in entered, until an hour after its last try
- counts and sizes of calls, and counts of Pairings, errors and limit hits: by day for 90 days, and for the current hour, for an alert when errors climb
- whether the review code, for app directory reviewers, works now
The Prompt a chat app passes to Banquish goes through the Relay to your Mac and stays there, unless you share the Workspace.
To end a Pairing, choose Unpair in Banquish's Connect menu. Its access ends at once. A Pairing you haven't used for 90 days ends by itself.
Who handles it
Cloudflare runs the site, the downloads, the Relay, shares and the counts above, and stores what they keep. Buttondown holds your email address and sends the updates. Nobody else receives any of it, and none of it is sold.
The site's visit and download counts and the app's daily counts are kept for three months, then deleted.
Banquish is made by GeonHyeok Boo. For a question about your data, or to have it deleted, write to hello@banquish.space.