Privacy

What we hold about a founder

You sign in with Google, so Keel never sees a password and never stores one. Google tells us who you are, and we keep four things from that: the identifier Google uses for your account, your email address, your name and your profile picture, if you have one. We also keep the moment your account was made and the moment you last signed in.

That is the whole of it. We do not ask for a company, an address, a phone number or a card, because there is nothing to bill.

If you send us feedback from inside Keel, we keep what you wrote, the page you were on and your account, and read it by hand.

What we hold about a person you ask

What they wrote and what they picked, and the name you typed when you made their link.

We never ask them for their name. The name on their row is your own note, so you can keep track of who you asked — it is not something we collected from them.

Before they answer a single question, their page tells them, in these words: “Keel is storing what you write here and sharing it with the founder who invited you. There is no way to delete it once you send it.” That is true, and it is why it is on their page and on this one.

Who can see it

A person's answers are readable by the founder who invited them, and by nobody else. Every read of a project is checked against the account that owns it; a request from any other account is answered as though the project were not there.

We do not sell anything, we do not advertise, and we do not share your project or anyone's answers with a third party.

What your own AI sees, and what we never see

Every judgement Keel makes runs as your own Claude Code, Copilot CLI or Codex, on your own machine, under your own subscription. Keel holds no AI key at all and never calls a model.

The runtime passes your CLI's own credentials to your CLI and nothing else. They never reach us.

What is on your machine and not on ours

The runtime keeps a small folder of its own: the credential your browser approved, stored with owner-only permissions or in your operating system's own keychain; a small file saying it is running; a launch log; and one working folder per job, made for that job.

None of that is sent to us. “keel disconnect”, or Ctrl-C, stops the runtime; the credential stays where it is until you remove it.

Where it lives, and for how long

One server in Amazon Web Services' us-east-1 region, with one database on it. A copy of the database is taken every night, encrypted, and deleted after thirty days.

Your project and its answers stay until you ask us to remove them.

Cookies, and counting

One cookie: the one that remembers you are signed in. Nothing else is set, and the participant's page sets none at all — their link is the whole of their credential.

We count page views with a privacy-friendly counter that sets no cookie, follows nobody between sites and collects nothing about a person. There is no advertising tag on this site.

Asking us to delete something

Write to contact@keeldiscovery.com and say what you want removed. We will remove your account and your projects, and tell you when it is done.

One honest limit: a person you asked cannot delete their own answers from inside the product, because Keel has no path that does it. Their page says so before they answer. If they write to us, we will remove them by hand.

If this changes

The date at the top changes with it, and the change is in the public history of this page's own repository. If a change means Keel holds something new, it will be said here before it is true.