Privacy Policy

Effective October 8, 2026

Kite is made by GlueGroups, Inc. (“Kite,” “we,” “us”), which also runs the website at kite.bot. Questions about this policy go to hello@kite.bot.

Kite is a home for your personal agents. It runs mostly on your own devices, so we hold very little of your data. This policy explains what we do collect, why, and what happens to everything else. It covers the kite.bot website and the Kite apps for Mac and iPhone during our alpha program.

The short version

Your chats, projects, memory, routines, and attachments stay on your devices. We don’t run a Kite server that stores them, and we can’t read them.
When you chat with a bot, your messages go to the AI provider you set up for that bot, using your own key or sign-in. That is between you and the provider.
We collect your name and email when you request access, and diagnostic data (crashes, errors, usage counts) from the apps so we can fix problems.
By default, the diagnostics we send do not include the text of your prompts or replies.
We don’t sell your data and we don’t show ads.

What we collect

1. When you request access

The form on kite.bot collects your name and email address. We record them, with the time of your request, as an issue in Linear, our project-management tool, so we can review your request and email you about the alpha. We use them to reply to you, grant access, send alpha updates, and ask for feedback.

2. Diagnostics from the Kite apps

The distributed Mac and iPhone apps (and the helper program the Mac app runs) send diagnostic data to Sentry, our error-monitoring provider. This includes:

Crash and error reports, with stack traces (function names and file names, not file paths or variable values).
Performance and usage measurements: how long things take, counts of events, which model and provider a bot used, token counts, error categories, app version, and operating-system and device information.
A random install ID. This is a pseudonymous identifier generated when you first run Kite. It is not linked to your name or email, and it lets us tell whether many reports come from one install. You can see it in Settings under Diagnostics.
Connection identifiers for pairing a phone with a Mac, shortened so they can’t be used to connect to your device.

What we work to keep out of diagnostics: the text of your messages and the bot’s replies, your files, and your credentials. Before anything is sent, we mask text in error messages (file paths in your home folder become ~/…, and quoted strings are replaced by their length) and strip things that look like API keys, tokens, passwords, and cookies. Sending prompt and response text with diagnostics is switched off. These are safeguards, not guarantees; an error message could occasionally include something we didn’t anticipate.

Local builds and test builds don’t send diagnostics. Only the distributed app does.

3. Feedback you send us

If you use Send Feedback, we receive what you choose to include: your message, an optional email address, and any screenshots or logs you attach. Logs are scrubbed when they are created, but screenshots are sent exactly as you attach them, so check them before you send. Feedback also goes through Sentry. A bot can also send feedback on your behalf using the same feature; you will see it before it goes.

4. Website and update traffic

kite.bot is hosted on Vercel, and our update and download files are hosted on Amazon Web Services. These providers log standard request data such as IP address, browser or app version, and time. The Mac app checks for updates and downloads its on-device routing model from updates.kite.bot, which creates the same kind of log entry. The website loads its font from Google Fonts, which means Google receives your IP address when you view the page. We don’t use advertising or analytics cookies on the site.

5. Community

If you join our Discord, Discord’s own privacy policy applies, and we can see what you post there.

What stays on your devices

Kite stores chats, projects, routines, drafts, attachments, and memory files on your Mac, and keeps a read-only copy of that data on a phone you’ve paired. Provider keys and sign-ins you add are kept in your device’s Keychain. Voice input is transcribed on your device, and we don’t keep the audio. None of this is sent to us.

What goes to other companies, because you set it up

Kite doesn’t ship with its own AI provider keys. Each bot talks to a provider or agent system that you configure.

AI providers. Your messages, attachments you send, and any content a bot reads while doing a task are sent to the provider behind that bot (for example Anthropic, via the bundled Claude Code or your API key). The provider’s terms and privacy policy govern that data. Kite does not see it.
Web search. When a bot searches or reads the web, the query or URL goes to our search provider, Parallel.
Tools and connections you enable. If you let a bot use a third-party tool (such as an MCP or plugin connection), the information the bot sends there goes to that service.
Your Mac. Bots can act on your Mac, including opening apps, reading the screen, running commands, and, if you grant access, reading Contacts, Calendar, Notes, Reminders, and files. Kite asks for these permissions at first use, and you can turn them off. Anything a bot reads can be included in what it sends to its provider.

Please don’t give a bot access to information you aren’t comfortable sharing with its provider.

Connecting your phone and Mac

Your phone and Mac connect to each other through an encrypted peer-to-peer connection (iroh). When a direct connection isn’t possible, traffic passes through relay servers that can see that a connection exists but not its contents. Push notifications are sent through our notification relay and Apple’s push service. Notification text is encrypted on your Mac and can only be opened on your phone; our relay does not store anything and cannot read it. Apple’s push service sees device tokens and delivery timing.

How we use data

We use data to run the alpha, respond to you, find and fix bugs, measure reliability and cost, improve Kite, keep it secure, and meet legal obligations. We don’t use your chats to train models. We have no access to them.

Only service providers that help us run Kite, under their own terms: Sentry (diagnostics and feedback), Linear (access requests), Vercel and Amazon Web Services (hosting and updates), Apple (TestFlight and push notifications), Google (fonts), Parallel (web search), and Discord (community). We may disclose data if the law requires it or to protect people’s safety or our rights, and to a successor if we are acquired. We don’t sell or “share” personal information as those terms are used in privacy laws, for advertising.

How long we keep it

Access requests: while you’re in the alpha or until you ask us to delete them, and up to 12 months after the program ends.
Diagnostics: according to Sentry’s retention settings for our project, currently 90 days.
Feedback: as long as we need to act on it, then deleted or de-identified.
Everything on your devices: until you delete it. Removing the app and its data folder removes it.

Your choices and rights

You can ask us to access, correct, or delete the personal data we hold about you, or to stop emailing you, by writing to hello@kite.bot. To find your diagnostic data, include your install ID from Settings. Depending on where you live (for example the EEA, UK, or California), you may have additional rights, including to object to or restrict processing and to complain to your regulator. We won’t discriminate against you for using them. Where GDPR applies, our bases for processing are your request (access requests), our legitimate interest in running and securing the product (diagnostics), and your consent (feedback you submit).

You can turn off Kite’s access to your Mac in settings, and you can revoke permissions in macOS or iOS System Settings.

Children

Kite is not for anyone under 16, and we don’t knowingly collect their data.

International transfers

We and our providers are based in the United States and other countries. If you’re elsewhere, your data will be transferred there. Where required, we rely on safeguards such as the European Commission’s Standard Contractual Clauses.

Security

We use encryption in transit and limit what we collect. No system is perfectly secure, and we will tell you promptly about a breach that affects your data as the law requires.

Changes

If we change this policy in a material way, we’ll post the new version here with a new effective date and, during the alpha, email active testers.

Contact

GlueGroups, Inc., 855 Front St, San Francisco, CA
hello@kite.bot