What leaves your computer

Hanyx keeps your memory, chats, tasks and settings in files on your Mac. This page lists every server the app can contact, why, what is sent, and when. Nothing else is contacted: the app's own window can only talk to the Hanyx process on your Mac (its content security policy refuses every other address), and all outbound requests are made by the Hanyx core or, for updates, the app shell.

You can check this yourself at any time: Settings → Privacy lists every request, with the time, the host, the reason and the size, and shows the exact context sent to Claude. The list is kept on your Mac for 30 days and has a Clear button. This page is checked against the code by a test (packages/core/src/data-flow.test.ts), so a new host can't be added without being listed here.

There is no Hanyx server that receives your data, no analytics and no crash reporting. The only Hanyx-operated host is download.hanyx.app, which serves downloads and update information (a sync server is also offered by default if your build was made with one; see "Only if you turn on sync").

Always, once you use the app

Host	Why	What is sent	When
api.anthropic.com	Claude answers your chats, triages pasted messages, drafts replies, and extracts and tidies your memory.	Your API key (as the request's credential); a system prompt; your profile; memory facts retrieved for the message; the text you typed or pasted, including quoted selections from quick capture; earlier turns of the chat; results returned by connected tools; tool definitions.	Whenever you chat or triage, a few minutes after a chat goes quiet (memory extraction), and once a day (the daily summary). Nothing is sent while you don't use Hanyx.
download.hanyx.app	Checks whether a newer version exists, and downloads it if you choose.	A plain request for latest.json, with no account and no identifiers (like any web request, the server sees your IP address). Downloads are signed; the app refuses an update that isn't.	About 15 seconds after launch, then every 6 hours, and when you press "Check for updates". The download happens only when you click "Restart to update".

If you use a different model provider (Settings → Model provider) the requests above go to that provider instead of api.anthropic.com; they carry the same content.

Only if you choose another model provider

Host	Why	What is sent	When
bedrock-mantle.{region}.api.aws	Claude through your company's Amazon Bedrock.	Same as the Claude request above, signed with your Bedrock API key.	Only for spaces set to Amazon Bedrock.
{region}-aiplatform.googleapis.com	Claude through your company's Google Vertex AI.	Same as the Claude request above, with a Google access token.	Only for spaces set to Google Vertex AI.
oauth2.googleapis.com	Vertex AI: exchanges your service-account key for a short-lived access token.	A signed assertion made from your service-account key. The key itself stays on your Mac.	Only for spaces set to Google Vertex AI, when a token is needed.
inference.do-ai.run	Claude and other models through DigitalOcean.	Same as the Claude request above, with your model access key.	Only for spaces set to DigitalOcean.

Only if you turn on a connector

Connectors are off until you add a token or sign in. They only ever contact the hosts below; the app refuses any other address, including redirects.

Host	Why	What is sent	When
api.github.com	Reads a pasted GitHub link (issue, pull request); when you click Run on a proposed action, creates a comment, release or similar.	Your GitHub token; the link's repository and number; for a write, exactly the arguments shown on the card you approved.	When you paste a GitHub link, and when Hanyx prepares or runs an action for a connected GitHub account. Writes only after your click.
github.com	"Sign in with GitHub" (device flow).	The app's client ID and a device code. No password.	Only while you sign in.
<your-site>.atlassian.net	Reads Jira issues from pasted links; moves, comments or assigns tickets after your click.	Your Jira email and API token; the issue key; for a write, the arguments on the approved card.	Only for the Jira site you entered.
api.figma.com	Reads comments on a pasted Figma link.	Your Figma token; the file key.	When you paste a Figma link.
gmail.googleapis.com	Reads a pasted Gmail thread (read-only).	A Google access token; the thread id.	When you paste a Gmail link.
oauth2.googleapis.com	Gmail sign-in and token refresh.	The one-time sign-in code or your refresh token, and the app's Google client.	When you sign in to Gmail and when its access token expires.
accounts.google.com	Opens Google's sign-in page in your browser.	Nothing is sent by Hanyx: your browser loads the page.	Only while you sign in to Gmail.
mcp.atlassian.com, mcp.linear.app, mcp.notion.com, gitlab.com, mcp.asana.com, mcp.sentry.dev, mcp.monday.com, mcp.intercom.com, mcp.box.com, mcp.canva.com	One-click connectors from the directory in Settings → Connectors (MCP servers). Their tools become available in chat.	The sign-in exchange with that service, and the arguments of each tool call. Tools that change anything wait for your Allow.	Only for services you connected, and only when a chat or action uses their tools.
Any address you add as a custom connector	A custom MCP server you add yourself.	Same as above.	Only after you add it and sign in. The sign-in service named by that server's own metadata is contacted too and then pinned.

Only if you turn on sync

Host	Why	What is sent	When
The sync server you choose (Settings → Sync & Devices; https only)	Shares memory, chats, tasks and appearance between your Macs.	Your email address (for sign-in codes), this Mac's name and public key, and encrypted batches. Everything about your content is encrypted on your Mac before it is sent; the server holds only ciphertext and cannot read it. The server can see when you sync, how much, and your IP address.	Only after you sign in and turn on a space. Then continuously while Hanyx is open, plus a live connection (WebSocket) that tells your Macs to fetch changes.

Links that open in your browser

Some buttons open a web page in your default browser (for example console.anthropic.com to create an API key, or the sign-in page of a service). Hanyx sends nothing in these cases; your browser loads the page. Links inside pasted content open only when you click them, and only http and https links open.

What is never sent

• Passwords and API keys are stored in the macOS Keychain. Keys are sent only to the service they belong to, as that request's credential.
• Your memory database and chat history are not uploaded anywhere, except as encrypted batches if you turn on sync.
• Demo mode (a hidden mode for recordings) never reads your real data or keys.

Not shown in Settings → Privacy

• Update checks are made by the app shell and are written into the same list, but their size isn't known.
• The live sync connection is listed when it opens; messages inside it are not.
• Vertex AI's token request (oauth2.googleapis.com) is made by Google's library and is not listed.
• Pages opened in your browser are loaded by the browser.