Privacy Policy - Kyew Docs

Last updated: February 2026

Kyew is operated by Jordan Cauley, an individual developer. This policy explains what data Kyew collects, how it is stored, and what control you have over it.

What data is collected

Authentication data

When you sign in with Google, Kyew receives your email address, display name, and Google account ID. These are used solely for authentication and identifying your account.

Kyew requests only the openid, email, and profile OAuth scopes. It does not request access to Gmail, Google Drive, Google Calendar, or any other Google services.

User-created content

Everything you create through Kyew's MCP tools is stored on your behalf:

Memories -- observations, notes, and context you store via the remember tool
Skills -- reusable patterns and knowledge you create or approve
Custom tools -- HTTP proxy tools, transform tools, chain tools, and code tools you define
Connections -- external API configurations you set up for custom tools

Request metadata

Kyew logs basic request metadata (timestamps, request counts) for rate limiting enforcement. This data is not tied to the content of your requests and is not used for analytics or tracking.

How data is stored

Infrastructure

Database: Cloudflare D1 (SQLite-compatible), encrypted at rest by Cloudflare
Sessions: Cloudflare KV, used for OAuth session management
Processing: Cloudflare Workers on Cloudflare's global edge network

User isolation

All data is scoped per user using your unique userId (derived from your Google account ID). The storage layer enforces this scoping on every database query. There is no mechanism for one user to access another user's data.

Cookies

Kyew uses a single cookie:

mcp_session -- an HttpOnly, Secure cookie used for authentication. It contains your session identifier and is set with SameSite=Lax. No tracking cookies, advertising cookies, or third-party cookies are used.

Kyew does not share your data with third parties. Your memories, skills, tools, and other content are not sold, rented, or provided to anyone else.

If you create custom tools that call external APIs, those requests are initiated by you and go directly to the external service. Kyew acts as a proxy but does not retain or share the data from those requests beyond executing them on your behalf.

Data export

You can export all of your data at any time using the export MCP tool. This returns a complete JSON export of your memories, skills, and related data.

Data deletion

Individual memories: Use the forget tool to soft-delete specific memories.
Full account deletion: Contact jordan@cauley.co to request complete deletion of your account and all associated data.

Data retention

Memories and skills persist until you delete them.
Sessions expire after 30 days of inactivity.
OAuth state tokens expire after 10 minutes (used only during the sign-in flow).

Data location

Your data is processed and stored on Cloudflare's global network. Cloudflare may replicate data across its edge locations for performance and reliability. See Cloudflare's privacy policy for details on their infrastructure.

Analytics and tracking

Kyew collects anonymized usage data for internal product improvement purposes. This includes:

Tool usage frequency -- which MCP tools are called and how often (not the content of those calls)
Feature adoption -- which capabilities are being used across the user base
Error rates -- aggregate failure patterns to identify and fix issues
Request volume -- request counts used for rate limiting and capacity planning

This data is aggregated and anonymized. It does not include the content of your memories, skills, prompts, or any other user-created data. No third-party analytics services, tracking pixels, or behavioral profiling tools are used.

Changes to this policy

Changes to this privacy policy will be posted on this page with an updated date. If significant changes are made, we will make reasonable efforts to notify active users.

Contact

For questions about this privacy policy or your data, contact jordan@cauley.co.