Privacy Policy

Last updated October 10, 2026

Keel is an early-stage, pilot-phase project built and operated by me, Cord Slatton. Catsylvania Software is the name I use for this work; it is not a separate registered company. This policy describes what happens with your information when you ask for access to Keel, sign in, and use it. Keel is still a small pilot, so this policy is written plainly and will change as the product does. If you are a returning user, check the date above.

What Keel collects

• Access requests. If you ask for access through the form on this site, Keel stores your email address, the message you typed, and whether the request was approved.
• Account details. Your name, email address and a sign-in identifier from AWS Cognito. If you sign in with Google, Google provides the name and email. If you sign in with an email and password, Cognito holds the password; Keel never sees it.
• Setup conversations. What you tell Keel while describing a goal or a business is saved on the server as you go, so you can pick the conversation up again. Conversations are deleted seven days after their last activity. The details you confirm at the end become a project profile and are kept.
• Your projects and the work Keel does. Project profiles, the goals (requests) you give Keel, the plans it writes, your replies and decisions on each step, drafts of content or code, a record of each call Keel made to one of your systems and what came back, and a plain-language log of each change that was made.
• Files you attach. Up to ten files and 30 MB per request. They stay with the request and are re-read by later AI work on that request.
• Credentials for your systems. API keys, tokens and logins you give Keel so it can act on a system you connect. They are encrypted at rest (AES-256-GCM) and decrypted only for the moment a call is made. Keel never shows them back to you in full.
• Your own Anthropic API key, if you add one under Usage. It is stored encrypted; only the last four characters are ever shown again. You can remove it at any time.
• Usage records. For each AI call Keel makes for you: the purpose, the model, token counts, and which project and request it was for. These enforce the usage allowance and caps on your account.
• Connected apps. If you connect Keel to Claude, Keel stores the connection's name, hashed access tokens, and when it was last used.
• Problem reports. When you use "Report a problem": your message, the page you were on, the app version, your email address, and any screenshots or files you attach (up to 25 MB per report). Attachments are stored in Keel's database and deleted after 90 days.
• In your browser. A session cookie that keeps you signed in, and unsent text you have typed, kept in your browser's local storage for up to seven days so a reload does not lose it. That text never leaves your device until you send it.
• Server logs. Standard web server request logs.

Keel uses no analytics or advertising trackers.

How it's used

To run your account, to do the work you ask Keel to do, to enforce usage limits, and to find and fix problems. As the operator, I can read the data above through Keel's admin area and its database when I need to run the service or look into a problem you reported. Keel does not sell your information, does not use it for advertising, and does not use it to train AI models.

Who it's shared with

• Anthropic (maker of Claude) does the thinking. Everything you tell Keel and every file you attach can be sent to Anthropic's API: setup conversations, goals, plans, plan chat, drafts, the content of steps Keel carries out, and what your connected systems return when Keel reads them. Some tasks also use Anthropic's web search, so search queries drawn from your request go out too. Calls run under Keel's Anthropic account, or under your own key if you add one. Anthropic handles this data under its commercial terms and privacy policy.
• Your connected systems. When you approve a step, Keel sends what that step needs to the system you connected, using the credentials you gave it. Nothing is sent to a system before you approve the step that sends it.
• Claude, if you connect it. If you connect Keel to your own Claude account, your projects, requests and plans become available to Claude in that account, and Anthropic handles them under the terms of your Claude account. You can disconnect at any time under Connected apps.
• Amazon Web Services runs sign-in (Cognito): your name, email address and, for email sign-in, your password.
• DigitalOcean hosts the server and database Keel runs on, in San Francisco, USA.
• ntfy.sh sends a push notification to my phone when a new access request, problem report or unapproved sign-in attempt arrives. The notification says only that one arrived; it carries no names, emails or message text.
• GitHub receives a copy of each problem report as an issue in Keel's private repository, so no report is lost: your email address, the page, the app version and your message. Attachments stay in Keel; the issue only links to them behind an admin login.
• Google learns that you signed in if you choose "Continue with Google". The pages on this marketing site, including this one, load fonts from Google Fonts, so Google sees the ordinary details of that request (your IP address and browser).

No other sharing, and never a sale of your information to anyone.

Data retention and deletion

Setup conversations are deleted seven days after their last activity; problem-report attachments after 90 days; drafts in your browser after seven days. Everything else is kept while your account exists.

You can archive or permanently delete any project yourself from inside Keel, which removes its goals, plans, work records and stored credentials. You can remove your own Anthropic key and disconnect connected apps at any time.

If you want your whole account gone, ask me (see Contact). I will remove your account, projects, requests, plans, stored credentials and keys, usage records, conversations and problem reports from Keel's database, and your sign-in from Cognito, within 30 days. Some copies are outside Keel's reach or take longer: problem reports already filed as GitHub issues, which I will delete or strip of your details on request; data already sent to Anthropic, which Anthropic keeps under its own retention policy; and server logs, which rotate on their own schedule.

Security

Sign-in is handled by AWS Cognito, not a homemade login system. Everything travels over HTTPS. Credentials for your systems and your own API key are encrypted at rest and are not written into application code. Access to the server and database is limited to me.

Changes to this policy

Material changes will be called out here with a new "last updated" date. The October 2026 update added the access-request form, stored setup conversations, attachments, your own API key, connected apps, and the full list of who receives what.

Contact

Questions, corrections or deletion requests: send a message through the form on keel.catsylvania.com, which reaches me directly, or use "Report a problem" inside Keel if you are signed in.