LEGAL / PRIVACY POLICY

Last updated: November 18, 2026

Privacy Policy

How Keo handles your data, local credentials, and automatic updates on macOS.

Keo is built with a strict local-first architecture. We do not operate any telemetry servers, user databases, or analytics pipelines inside the macOS application or the keo command-line tool.

1. Zero Data Collection

Keo runs entirely locally on your Mac. Neither Keo.app nor the keo CLI collects, transmits, or stores any of the following on external servers:

  • Your kiro-cli authentication tokens, session cookies, or OAuth credentials.
  • Your AWS IAM Identity Center (IdC) URLs, AWS Builder ID details, or Social login profiles.
  • Your local SQLite databases (data.sqlite3), conversation histories, or prompt logs.
  • Your ~/.kiro configuration files (steering, skills, settings/mcp.json, or cloud-cache).
  • Telemetry, crash reports, usage analytics, or hardware identifiers.

2. How Credentials & Profiles Are Stored on Your Mac

When you initialize Keo or switch between profiles, all operations happen exclusively on your local filesystem:

  • Sandbox Directory (~/.keo): Each profile’s configuration and session database are stored in ~/.keo/<profile>/.
  • SQLite Vault Permissions (0600): Profile databases (~/.keo/<profile>/kiro-cli/data.sqlite3) are backed up and restored using SQLite’s online backup API (sqlite3_backup) with restrictive POSIX permissions (0600 — readable and writable only by your macOS user account).
  • Direct Authentication via kiro-cli: When you run keo create <profile>, Keo invokes your locally installed kiro-cli binary inside an isolated environment. All authentication flows occur directly between kiro-cli, your web browser, and your identity provider (e.g., AWS or your enterprise IdP).

3. Automatic Updates (Sparkle 2 & Cloudflare R2)

Keo.app uses the open-source Sparkle 2 framework to check for and install signed application updates from our distribution endpoint (https://k-re.coderdiaz.com):

  • When checking for updates or downloading Keo.dmg, standard HTTP request metadata (such as your IP address, macOS version, and current Keo version) is processed by Cloudflare R2 / CDN solely to deliver the update feed (appcast.xml) and installer binary.
  • We do not log, profile, or sell this network metadata.

4. Website Hosting & Analytics

This website (keo.coderdiaz.com) is static and hosted on Vercel:

  • Web Analytics (OpenPanel): We use OpenPanel on this website to collect aggregated, privacy-friendly traffic and usage metrics (such as page views, referrers, browser/OS type, and general geographic region) so we can understand how visitors discover and interact with the site.
  • Hosting Logs & No Ad Tracking: Standard server access logs may be processed by our hosting provider for security and reliability purposes. We do not sell visitor data or use third-party advertising networks.

5. Uninstalling & Deleting Your Local Data

You remain in complete control of your files at all times:

  1. Run keo eject in your terminal to remove Keo’s symbolic links and restore your active profile’s real directories and files into ~/.kiro.
  2. Delete the ~/.keo directory (rm -rf ~/.keo) to permanently remove all local profile sandboxes and backed-up data.sqlite3 vaults.
  3. Move Keo.app from /Applications to the Trash and remove ~/.local/bin/keo.

6. Contact

If you have any questions about this Privacy Policy or Keo’s security model, please reach out on X (@coderdiaz) or via email hey@coderdiaz.com.

Keo

Switch contexts as fast as you switch terminals

Requires macOS 14.0 (Sonoma) or later