榫卯Tenon AI
ServicesProductsPricingBlogAbout
Sign in Sign up

My account

Switch account

Add account
Contact us
Yew Harness/Privacy Policy

Yew Harness Privacy Policy

Version 2.9 · Effective Nov 20, 2026

Yew Harness runs on your own computer, and Yew Harness on your phone (iPhone or Android) connects only to Yew Harness on your own computer; the Android app also checks for new versions, as described below. Tenon AI does not collect or receive your content in Yew Harness, and Yew Harness contains no analytics, telemetry or reporting code.

Data kept on your computer: sessions, messages, tool call records, permissions you granted, letters between sessions, the decisions you make in the approval center, scheduled tasks and settings are stored in a database in Yew Harness's data folder (~/.yew by default); provider API keys, and the access tokens, refresh tokens and client registrations Yew Harness gets when you sign in to an MCP server in your browser, are stored in the system keychain; MCP server settings are kept in mcp.json in the data folder, including keys you enter and the ID and secret of a Google client you created yourself; very long command output is stored in the tmp folder of the data folder; every version of the artifacts sessions save (documents, pages, data and charts) is stored in its artifacts folder. Yew Harness's built-in browser uses your own Chrome by default, through the Playwright extension, and its cookies, cache and history stay in your Chrome; if you choose a separate window in Settings, that window's profile (cookies, cache and history of the sites you signed in to there) is stored in the browser folder of the data folder. When you set Yew Harness to start at login with yew service, its service log (start-up, errors and relay connection lines, without conversation content) is stored in the logs folder of the data folder. When you open the interface in the Mac app, macOS keeps for it, under cn.tenonai.apps.yew.desktop in ~/Library, the cookie that signs you in to Yew Harness (it expires after 30 days without use), a cache of the interface's files, a few local interface settings and the window's position and size, without any session content. This data stays until you delete it. If you set a decision log file in Settings, Yew Harness adds each decision to that file.

Phone access: when you turn on phone access on your computer, Yew Harness on the computer connects to a relay, and Yew Harness on your phone talks to it through the relay. The default relay is run by Tenon AI; you can also run your own. The two ends are encrypted end to end: the relay only passes ciphertext along and can neither read nor keep the content. For network security, the relay run by Tenon AI keeps a connection log: the time, the IP address, the path requested (which carries your computer's identifier, a hash of its public key) and the status, without content, deleted automatically after 184 days. The relay server is in mainland China. Yew Harness on the computer records each paired phone: its name, public key, when it was paired and when it last connected. Yew Harness on iPhone keeps the pairing and its own key in the iOS keychain, on that device only. With notifications on, Yew Harness on iPhone gives the push token it got from Apple to your computer over the encrypted channel, and the computer keeps it; the computer encrypts what a notification says for that iPhone and hands it to Apple's push service through the relay. The relay and Apple handle the push token and the ciphertext, and cannot read what the notification says. Yew Harness on Android keeps the pairing and its own key in a private file of the app, encrypted with a key in the Android Keystore, on that device only; it is left out of system backups and device transfers. Yew Harness on Android uses no push service and has no push token: with notifications on, a foreground service keeps a connection to the relay open in the background, and the computer sends what a notification says to the phone over the end-to-end encrypted channel; the relay only passes ciphertext along. Android shows a standing notification for this connection, and notifications do not arrive while the system has stopped Yew Harness. Scanning the pairing QR code uses the camera; the picture is read on the phone and is neither kept nor sent. The phone also remembers whether notifications are on and the ids of the items it has already seen, without their content.

Data sent to third parties: the model provider you choose for a session receives the conversation sent to it, including files the session read, command output, what MCP tools return (such as the emails, events and files in a mailbox, calendar or drive you connected), and the page content and screenshots a session obtains when it uses the browser and computer control tools; a screenshot captures whatever is on the screen at that moment, including other apps' windows; with your own Chrome, a session can open sites you are signed in to and read their pages, in the tabs you give it and the tabs it opens, and a script it runs in a page can also read the cookies that site lets scripts read, all of which goes to the provider as well; that provider's privacy policy applies. The default provider, DeepSeek, is a service of the Chinese company DeepSeek; how it handles and stores this content is set out in its privacy policy. If you choose a provider outside mainland China, this content goes abroad. When a session fetches a web page, opens one in the built-in browser or has your default browser open an address, that site receives the request; a site you signed in to in those browsers (the built-in browser uses your own Chrome by default) receives requests that carry your sign-in. When a session searches the web, the search service it uses receives only the query: Bocha, Tavily or Brave if you saved a key for one of them, and otherwise DeepSeek, with the DeepSeek key you saved; that service's privacy policy applies, and with a search service outside mainland China (Tavily, Brave), the query goes abroad. By default Yew Harness starts two open-source MCP servers: a browser (Microsoft's Playwright MCP) and computer control (computer-use-mcp). They run on your computer, and you can turn them off in Settings. Yew Harness downloads and installs these two, and the common servers you add with one click that run on your computer, from npm the first time it uses them; npm receives the download request. Yew Harness installed globally with npm asks the registry your npm uses (by default registry.npmjs.org, outside mainland China) once a day for the newest version number of @tenonai/yew, and the Android app asks Gitee once a day for its newest release; the request carries only the version of Yew Harness or of the app, the registry or Gitee sees your IP address, and its privacy policy applies; both checks are on by default and can be turned off under About. When you click Update, npm downloads the new version from the same registry. An MCP server you add (it is written in mcp.json) receives what a session passes to its tools, and a service you signed in to in your browser receives requests made with your account. These services' own privacy policies apply; with a service outside mainland China (such as Google, Linear or Vercel), what is passed to it goes abroad. In the Default permission mode, these tools ask you before each call, until you choose Always allow for a tool; the clicks, typing and key presses of computer control, and the browser's actions on pages when it uses your own Chrome (clicking, typing, opening addresses, running scripts and the like), cannot be set to Always allow and ask every time. In the Auto mode, what would be asked goes first to a separate check by the model: when it finds that you asked for the step, the step runs, and otherwise you are asked; the check sends what you wrote in that session, the session's role and the step to the provider chosen for the session, without web pages, files or what tools returned. In the Skip mode, you are not asked, and risky calls are marked in the record. Computer control is not asked about either, and it can click anything on the screen, including the buttons in Yew Harness that wait for your approval. MCP tools that Yew Harness recognizes as sending, publishing or deleting something, and decisions that are yours, such as publishing, sending data out, connecting to remote machines and deleting files outside the workspace, ask you first in all three modes. Commands you set in hooks.json in the data folder run when a session starts, when you send a message, before and after a tool call and when a session stops, and receive what is at hand then (what you wrote, and a tool's name, arguments and result); what they do with it is up to those commands. Their output when a session starts and when you send a message is added to the conversation and goes to the model provider like the rest of it.

Access, export and deletion: you can look at the files in the data folder directly. To delete a provider's key, delete it in Settings or run yew key delete; to remove a paired phone, remove it under Phone access on the computer, or unpair on the phone; to sign out of an MCP server, choose Sign out under MCP servers: where the service supports it, Yew Harness first asks it to cancel the tokens, then deletes the ones kept on this computer; to make sure the access you granted is revoked, check or remove it in that service's account settings; to disconnect the built-in browser from your Chrome, click the Playwright extension's icon in Chrome and disconnect it, or remove the extension; to clear the separate window's sign-ins, delete the browser folder in the data folder; to clear what the Mac app keeps, quit it and delete the items starting with cn.tenonai.apps.yew.desktop in the WebKit, Caches, HTTPStorages and Preferences folders of ~/Library; to delete everything, stop yew serve and delete the data folder and, if you used the Mac app, those items too.

Contact: support@tenonai.cn.

榫卯Tenon AI

Enterprise digital and AI transformation

Services

Move work onlineData integration and reportingAI agent implementationAI agent deploymentAI model gateway deploymentAI infrastructureOpen-source customization and deploymentSoftware developmentAI coding adoptionTechnical consulting

Products

AgentHubIntent CLIIntHubCaretYew HarnessWeSaidPassBy

Company

AboutPricingBlogFounder profile

Support

Contact usSecurity and dataTenon Account

Legal

Terms of ServicePrivacy PolicyCookie PolicyAcceptable use

Follow

XLinkedInTikTokGitHubDouyinXiaohongshuPersonal blogRSS
© 2026 榫卯 Tenon AILegal湘ICP备2026054319号-1湘公网安备43010202002408号

We only use essential cookiesThey keep you signed in and remember your appearance and language. No analytics or ad tracking.

Cookie Policy