Privacy Policy

I. The Short Version

• We do not collect, receive, or store your personal information. We have no servers that could receive it.
• Your conversations with AI agents, your files, your code, your terminal output, your commands, your repository and branch names, and your prompts never leave your computer through Agentty.
• The only data that reaches anyone because of Agentty itself is a small set of anonymous usage statistics sent to Google Analytics. They contain no personal information and no content, they do not identify you personally, and you can switch them off. Section IV describes exactly what is in them.
• The AI agents you run are not us. Claude Code talks to Anthropic, Codex talks to OpenAI, and any other tool talks to its own provider — directly from your computer, under your own account with that company, exactly as in any other terminal. That exchange is governed by that provider's terms and privacy policy. Agentty does not read it, does not receive a copy of it, and is not a party to it. Section VI separates what Agentty itself connects to from what it does not.

II. Where Your Data Lives

Agentty organizes work that happens on your machine. Everything it shows you is read from, and written to, your own disk:

• Workspaces, tabs, splits, themes and preferences are stored in a folder in your home directory: ~/.agentty on macOS and Linux, %USERPROFILE%\.agentty on Windows.
• Session lists, conversation search, AI usage numbers, cost and token statistics are computed by reading the transcript files that the agent CLIs (Claude Code, Codex and others) already wrote on your computer. We never upload them, and we never copy them off your machine.
• Handoff and context documents created by Session Flow or by migrating a conversation between agents are files in your home directory.
• Git operations, working trees, branches and diffs act on your local repositories.
• Files created with a file-system permission that restricts them to your own user account where the operating system supports it.

Deleting the application's folder deletes everything Agentty kept.

III. Information We Collect

We collect no personal information.

We do not ask for your name, email address, phone number, payment details, or any account credentials. There is no registration, no login to Agentty, and no profile. Because we operate no server, database, or analytics infrastructure of our own, there is no place where information about you could accumulate on our side.

In particular, the following never leave your computer through Agentty: prompts and AI responses, transcripts and conversation content, file contents, file paths and folder names, commands you type, terminal output, repository names, branch names, commit messages, environment variables, API keys and other credentials, and the contents of the pages you open in the in-app browser.

The only exception is the anonymous usage statistics described in Section IV.

IV. Anonymous Usage Analytics

Google Analytics is the only channel through which anything reaches us, and it is used both by the Agentty desktop application and by the agentty.run website. Its purpose is narrow: to understand roughly how many people use Agentty, on which platforms, and which features are worth continuing to build. It is aggregate product measurement, not user tracking — we do not build profiles, we do not advertise, and we do not attempt to identify anyone.

In the desktop application, the statistics are sent from release builds to Google Analytics 4 through its Measurement Protocol.

What is sent

Counts, essentially: anonymous, non-identifying tallies of moving around the application and starting things in it — a window opened, a pane started, an area of the application used. They exist to show where people run into friction while using Agentty, and nothing in them describes you or your work.

Each event also carries the application version, the operating system version and a random installation identifier. That is all.

Events come from a fixed, closed list inside the application, and their names and properties are checked against an allow-list before anything is sent; whatever is not on that list is discarded rather than transmitted. Events are queued locally and sent at most once a minute.

What is never sent

No paths, file names, folder names, commands, prompts, AI output, conversation content, repository names, branch names, project names, environment values, credentials, IP-based location chosen by us, or any identifier that we could connect to you as a person.

About the installation identifier

The installation identifier is a random value generated on first use and stored in a file inside the application's folder on your computer (~/.agentty/install_id, or %USERPROFILE%\.agentty\install_id on Windows). It is not derived from your hardware, your user name, your email address, or anything else about you, and it is not linked to any other identifier. It allows a rough count of distinct installations rather than repeat launches. Deleting that file resets it, and it is never shared with anyone other than the analytics provider described below.

Because this identifier is persistent, we describe these events as anonymous in the sense that they contain no personal information and cannot be traced back to you by us. Some privacy laws treat a persistent device-scoped identifier as pseudonymous rather than strictly anonymous, so we state plainly that it exists rather than claiming otherwise.

Google as the analytics provider

The statistics are delivered to Google, which acts as our analytics provider and processes them under the Google Privacy Policy and its Google Analytics terms.

Stated in the terms of Korean data protection law, this is an entrusted processing arrangement with a transfer abroad:

• Processor entrusted: Google LLC
• Work entrusted: collection and analysis of anonymous usage statistics
• Country of transfer: the United States
• When and how: transmitted over the network at the moment an event occurs
• Retention: for the retention period configured on the analytics property, after which Google deletes the data As with any request made over the internet, the network connection that delivers an event exposes your IP address to the receiving service. We do not ask Google for, look at, or store IP addresses, and we do not use them to identify anyone.

On the website

The agentty.run website uses Google Analytics for the same purpose and in the same spirit: aggregate visit statistics. It does not ask for or receive any information you type, and it has no account or profile to attach a visit to. Google Analytics may set its own cookie or equivalent browser storage to count a return visit; apart from that, the site stores only your chosen language, and it runs no advertising, no remarketing, and no other tracking technology.

How this works on the website:

• On your first visit, wherever you are, a notice tells you that the site counts visits this way and links to this Policy.
• Where the law that applies to you gives you the right to opt out — in the European Union, the European Economic Area and the United Kingdom — the site footer carries a switch that turns analytics off and keeps it off on later visits. Elsewhere that switch is not offered, and the notice above is how the site tells you what it does.
• If your browser sends a Global Privacy Control signal, analytics stays off wherever you are, whatever the footer says.
• Your choice is kept in your own browser. It is not sent to a server, and it is not linked to anything else.

How to turn it off

In the desktop application, open Settings → General and switch off Share anonymous usage statistics. It is on by default; switching it off stops collection immediately, and anything already queued is discarded rather than sent. Setting the environment variable DO_NOT_TRACK to 1 turns it off as well, regardless of the setting. Builds that were not produced with analytics credentials — builds you compile yourself from source, and development builds — send nothing under any circumstances.

On the website, you can block analytics through your browser's privacy settings or content blocker, or install the Google Analytics opt-out browser add-on.

V. The agentty.run Website

The website has no accounts, no sign-up, no contact forms, and no comment system. It asks you for nothing, and there is nothing you can submit to it. Apart from the aggregate analytics described in Section IV, there are no tracking scripts, no advertising pixels, and no profiling of visitors.

Your chosen language is kept in the browser's local storage so the site opens in that language on your next visit. It never leaves your browser.

Three pieces of infrastructure are involved in serving the site, and although we collect nothing through them ourselves, they see ordinary web request data:

• The site is hosted on Vercel, which processes standard server request logs, including IP addresses, as its hosting infrastructure.
• The download link redirects to the release files hosted on GitHub, so GitHub receives the IP address and browser user agent of the request that downloads the file. We do not count or record downloads ourselves.
• One web font is loaded from the jsDelivr content delivery network, so that network receives the IP address of the request that fetches the font.

Each of these companies handles that data under its own privacy policy.

VI. Connections: Ours and Not Ours

Traffic leaving your computer while you use Agentty comes from two different places, and they should not be confused. This section separates them.

What Agentty itself connects to

The application makes these connections on its own. They carry none of your content:

• Update checks — at launch and periodically, the application asks the public GitHub release repository whether a newer version exists, and downloads the installer from GitHub when you choose to update. Only GitHub-hosted addresses are ever downloaded from, and downloads are verified against a published checksum.
• Service status — the application reads the public status pages of the AI services your agents depend on, so it can warn you when one of them is degraded while you work.
• Usage statistics — the anonymous events described in Section IV. This is the only connection through which anything reaches us at all.

That is the complete list.

What Agentty does not connect to

Everything else that leaves your machine belongs to a program you chose to run, or to a service you configured. Agentty starts the program and shows you what it prints. It does not read, decrypt, store or process what those connections carry, it never receives a copy, and none of it reaches us. We are neither the controller nor the processor of that data.

One feature is a deliberate exception, and only while you switch it on: the capture proxy described in Section VIII. Tabs you open while it is running are routed through a proxy on your own machine, so it can record which host each tab reached, how much it sent and for how long. It never records the content — encrypted traffic passes through without being decrypted — and the records stay in memory on your computer.

• AI agents. When you open a Claude Code, Codex or other agent pane, that tool runs on your computer, signed in with your own account with that provider, and talks to that provider directly — Anthropic for Claude Code, OpenAI for Codex, and the corresponding company for any other agent — exactly as it would in any other terminal. Your prompts, the files it reads and the conversation it produces travel between your computer and that provider. The handling of that data, including retention, use for model training, and deletion, is governed by that provider's own terms and privacy policy, and any question about it is between you and that company. Agentty is not a party to it.
• MCP servers and API connectors — servers and HTTP APIs you configured yourself are contacted directly from your machine with the credentials you supplied. Whoever operates each of those endpoints is responsible for what it does with what it receives.
• In-app browser — the pages you open are requested by your computer from those websites, as in any browser.
• Chat notifications — if you configure Slack, Discord or Telegram notifications, the message you asked for is sent from your computer directly to that service under its terms. The application adds no paths, prompts or conversation content of its own.
• Plugins — plugins run as separate processes on your computer and may only do what their declared permissions allow, which is shown to you before installation. The bundled Launch plugin signs you in to GitHub, Vercel and, when your project uses one, Supabase through those companies' own official command line tools and their own sign-in pages; the resulting tokens stay with those tools on your machine, what you publish goes to those companies under their terms, and none of it reaches us. The bundled Cosmica plugin talks only to the Cosmica application on your own computer.

VII. Credentials and Secrets

Credentials you give to Agentty — API connector secrets, notification webhook URLs, chat bot tokens, and agent sign-in credentials — are stored in the credential store your operating system provides: the Keychain on macOS, Credential Manager on Windows, or the Secret Service on Linux. Where no such service exists, they are written to a private file readable only by your user account.

They are never written into configuration files, never written into logs or error messages, never included in analytics, and never transmitted to us. Where the interface has to show a value that may contain a secret, it is redacted first.

VIII. Network Capture and Monitoring Features

Agentty includes an optional capture proxy that shows which hosts your tabs talk to. When you turn it on, it records the host, port, byte counts and timing of connections. Encrypted HTTPS traffic is tunnelled without being decrypted; no certificate is installed and no content is read. For plain HTTP requests, the method, path and status are recorded, never headers or bodies. All of these records are kept in memory only, are bounded in number, are never written to disk, and disappear when the application quits. Nothing from this feature is transmitted anywhere.

IX. Retention and Destruction

We hold no personal data on any system of ours, so there is nothing about you for us to retain or destroy. What exists, where it is kept, how long it is kept and how it is destroyed:

• On your computer — Retention: until you delete it. Destruction: remove the application's folder in your home directory and everything Agentty stored is gone. Transcripts written by the agent CLIs belong to those tools and live in their own folders.
• Analytics statistics — Retention: the retention period configured on the analytics property. Destruction: Google deletes the data once that period has passed. They contain no personal information.
• Installation identifier — Retention: until you remove it. Destruction: deleting the identifier file on your computer resets it immediately.

X. Your Rights

Depending on where you live, you may have rights under laws such as the Korean Personal Information Protection Act, the EU and UK General Data Protection Regulation, or the California Consumer Privacy Act, including rights of access, correction, deletion, portability, and restriction of processing.

We are able to honor these rights in a simple way: we hold no personal information about you, so there is nothing to disclose, correct, export, or erase on our side. We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not profile you or make automated decisions about you.

For the analytics described in Section IV, you can stop collection at any time as described there, and you can reset the installation identifier yourself. If you believe we hold information about you and want to exercise a right, contact us as described in Section XVI or Section XVII and we will respond.

XI. Children's Privacy

Agentty is a developer tool and is not directed at children. The Service is intended for people aged 14 or older, as stated in our Terms of Service. We do not knowingly collect information from children, and in fact do not knowingly collect information from anyone.

XII. Security

Agentty is designed so that sensitive material stays on your machine and under your operating system's protection: secrets in the system credential store, conversation and handoff files created with owner-only permissions where the operating system supports it, agent status communication over a private local socket restricted to your user account, HTTPS connections verified against trusted certificate authorities, and update downloads restricted to the official release host and verified against a published checksum.

No system is perfectly secure, and we cannot guarantee the security of your device or your network. Because Agentty runs with your own user account and can start programs, agents you run in it can read and change your files; treat agent permissions with the care you would apply to any program running as you.

XIII. International Transfers

Because we collect no personal information, there is no international transfer of your personal data by us. The analytics described in Section IV are processed by Google, which operates globally, and the infrastructure providers named in Section V operate globally as well.

When an AI agent you run sends your prompts to its provider, that transfer is made by that tool between you and that company, under the arrangements described in that provider's own privacy policy. It is not a transfer by us, and we have no role in it.

XIV. Changes to This Policy

We may update this Policy as Agentty changes. When we make a material change — in particular, if we ever begin collecting anything that was not collected before — we will update the effective date above and describe the change on this page before or at the time it takes effect. Continued use after a change means you accept the updated Policy.

XV. Governing Law

This Policy is governed by and construed in accordance with the laws of the Republic of Korea, without regard to its conflict of law provisions. Any dispute arising out of or in connection with this Policy shall be submitted to the jurisdiction of the Seoul Central District Court. If you are a consumer, you may instead bring an action before any court having jurisdiction under the applicable law, and this Policy does not deprive you of the protection of mandatory consumer law in your country of residence.

XVI. Data Protection Officer and Remedies

Data protection officer: RayLee — yongyongdev@gmail.com

Requests to access, correct, delete or stop the processing of your personal information are received at that address, as are questions and complaints about privacy in Agentty. We answer them ourselves; there is no separate department in between.

If you are not satisfied with our answer, or your rights have been infringed, the following Korean bodies handle dispute resolution and reports. They operate in Korean; the Korean name is given so you can find them:

• Personal Information Dispute Mediation Committee (개인정보분쟁조정위원회) — 1833-6972 — www.kopico.go.kr
• Privacy Infringement Report Center (개인정보침해신고센터) — 118 (no area code) — privacy.kisa.or.kr
• Supreme Prosecutors' Office (대검찰청) — 1301 (no area code) — www.spo.go.kr
• National Police Agency (경찰청) — 182 (no area code) — ecrm.police.go.kr

Under Articles 35 to 37 of the Personal Information Protection Act you may also request access, correction, deletion or suspension of processing directly, and under Article 35-4 you may appeal a decision. Where you are covered by the GDPR or the UK GDPR, you may lodge a complaint with your local supervisory authority.

XVII. Contact Us

Questions about this Policy, or about privacy in Agentty, can be sent to RayLee at yongyongdev@gmail.com.

Security vulnerabilities should be reported privately through GitHub's private vulnerability reporting on the Agentty repository rather than by opening a public issue.