The short version
Denshin does not sell personal data, run advertising, or include third-party analytics SDKs in the mobile app. Remote connections use machines you explicitly pair. Your terminal and agent content is handled on your devices and by your Denshin daemon, using the connection method you select.
If you select Denshin Relay, your connection passes through servers we operate. They carry end-to-end encrypted traffic they cannot read, but they do see connection metadata. That path is described in full below.
The Mac app
The Mac app and its local Denshin service read agent activity, session histories and account state on your Mac. Sessions displays conversation history and terminal output from your installed agent tools and the local service. Account and usage readings are cached locally.
The agent tools you choose can contact their providers for sign-in, account information and model requests, including the prompts you send. Those requests and authentication are subject to the providers' terms and privacy policies. Using Denshin does not make those agents or their models work offline.
The Mac app checks our download channel at files.denshin.dev (denshin-files.t3.tigrisfiles.io for versions released before it) for the latest version and downloads an update when installing it. The download service receives ordinary connection metadata, such as your IP address, connection time and the requested version or file. These update requests do not include project content. The automatic-updates switch controls installation; version checks still run.
Data the app keeps
- Paired machine names, endpoints and pinned machine identity.
- Device credentials in the operating system secure store.
- Local interface state, bounded cached projections and pending messages needed for offline recovery.
- Push notification registration when you enable notifications.
Your paired daemon keeps its own sessions, audit records and terminal state on the machine you control. denshin uninstall removes the host runtime while preserving that state for recovery; denshin uninstall --purge --yes explicitly removes both.
The Chrome extension
The Denshin side panel connects to sessions on your Mac. When you invoke Denshin on a web page, the panel can use the address Chrome grants it to suggest a session for that repository or site.
- Attaching a page. Choose Attach this page to add its title, address and selected text to your next message. The address contains the origin and path. Page text is included only when you ask. The attachment excludes form values and cookies. You can remove it before sending.
- Handing over a tab. A session can read and act in the tabs it opens, tabs you explicitly hand over, and their popups. In those tabs it can see page content and network traffic, including the headers and cookies the tabs send. Taking a tab back keeps it open and ends the session’s access to it.
- Where it goes. The extension contacts no server and carries no account. It talks only to the Denshin app on the same Mac, through Chrome's native messaging, and the app gives your agent what it asks for. Your agent may send that content to the AI provider of its account, as it does with everything else in its session, under that provider's terms. Nothing the extension reads is sent to Denshin.
- What stays on your Mac. Denshin keeps a trace of each session's browser actions, with their time, session, page and command, in files only your user account can read. Typed text, passwords, cookies, authorization headers and secret address parameters are masked before a line is written, and the trace keeps 14 days and 64 MB at most. Requests that would change something on a site are held until the Denshin app decides, and its decisions go to the app's local audit records. A request outside the session’s allowed sites can ask for your approval in the open panel. Without an answer it is refused.
- Your control. While an agent works, Chrome shows that Denshin started debugging the browser. Click Cancel on that bar to stop the agent in its tabs. Removing the extension in Chrome ends its access.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Denshin Relay, operated by us
Denshin Relay is first-party infrastructure, not a third-party service. When you select it, your connection is carried by servers we operate at relay.denshin.dev, and an admission service decides which endpoints may use them. This section describes that path specifically, because it is the one where data reaches infrastructure under our control.
Relay is one of four connection methods offered when you run the canonical denshin connect command on an interactive terminal, and it is the first option presented. It is not silently enabled: a non-interactive install falls back to a local-network mode instead. Tailscale, a direct HTTPS origin of your own, and same-network LAN are the alternatives, and none of them route through our servers. The compatible denshin up command remains for services and runbooks.
What the relay can see
Your terminal and agent traffic is QUIC/TLS 1.3 ciphertext, encrypted end to end between your phone and your own machine. The relay carries that ciphertext and cannot read it. It does observe the metadata any network intermediary observes: your IP address, the endpoint identifier of each side, connection times and traffic volumes.
What the admission service stores, and for how long
- Your IP address is never stored in the clear. It is used to enforce rate limits as a keyed hash, in a counter that expires within two hours for installation requests and within two minutes for endpoint exchanges.
- Endpoint leases, holding an endpoint identifier and a pseudonymous installation identifier, expire after 24 hours by default and can never be issued for longer than 7 days.
- The admission service cannot see terminal content, prompts, agent responses, or the credential your phone uses with your own machine.
This infrastructure runs on Fly.io, including its managed PostgreSQL, which processes the records above on our behalf.
Crash reports
The mobile app reports crashes and unhandled errors to Sentry, a third-party error-reporting service, when its build includes our Sentry project. A report contains only the error type, the stack of code locations, loaded modules, the app version and build, and the time; it carries no account, device name, error message, log, screenshot, terminal or agent content, and Sentry receives the request's IP address as ordinary connection metadata. The app has no setting to turn crash reports off today; uninstalling it stops them. The Mac app does not use Sentry.
Other service providers
Apple and Expo may process device and delivery identifiers when TestFlight, crash delivery infrastructure, or push notifications are used. A chosen network provider, such as Tailscale, processes traffic according to that provider's terms. The public website is hosted by Vercel, which may retain ordinary request logs. Denshin does not ask those providers to use terminal content for advertising.
Control and deletion
Revoke a phone from the machine's device controls to end that device's authority. Remove a paired machine in the app to delete its local record. On mobile, uninstalling the app removes its local app data subject to the operating system's backup behavior. Removing the Mac app bundle leaves provider profiles and Denshin's local state on your Mac. To stop using our relay entirely, select another connection method; nothing on this page's relay section applies once you do. For support or a request concerning data held by Denshin, email privacy@denshin.dev.
Changes
This notice is effective November 19, 2026. This revision adds the Chrome extension: what it reads, where that goes and what stays on your Mac. The October 27 revision clarified conversation and terminal history in the unified Mac app and the local state retained when its bundle is removed, and named Sentry for the mobile app's crash reports. The October 26 revision added the Mac app's local account and session readings and its update download channel.
The July 25, 2026 version replaced the version of July 16, 2026. That earlier version deferred disclosing our relay to a future revision, when the relay had in fact already shipped and was reachable from this site. The July 25 revision corrected that omission. The notice will be updated again before an account system, a payment service, or a materially different data path is offered publicly.