What kn0t holds, and what it never sees.
kn0t is designed to know less. This policy says, in plain English, what data Habgood Holdings Ltd, trading as kn0t, processes, why, and what stays on your machine by design. Where this page and the product could ever disagree, the narrower reading wins: we do not collect what this page does not name.
Who we are
Habgood Holdings Ltd, trading as kn0t, is the data controller for the kn0t website, the kn0t applications and the kn0t service. Registered in England and Wales, company number 15358425; registered office 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ. Contact: hello@kn0t.ai.
What stays on your machine
The desktop app runs the coordination engine locally. The following never leaves your machine and is never transmitted to us:
- Your code, diffs, file contents, prompts and agent transcripts.
- The record, kn0t's local cross-session memory, including its search index.
- Decisions about your agents’ changes. A conflicting change is held on your machine; nothing in our cloud sits between your agent and your files.
Working solo with no account signed in, nothing goes up at all: the Map, the decisions and the record all run locally.
What we process, and why
Account data. Username, email address and a password when you register (the password is held only by our identity service, hashed, and optional second factors such as an authenticator seed or a passkey's public key live there too). Legal basis: performing our contract with you.
Billing data. Payments are handled by Stripe. Your card details go to Stripe directly and never touch kn0t's servers; we store your Stripe customer and subscription identifiers and the resulting plan state. Legal basis: performing our contract, and legal obligations around billing records.
Team coordination data. On a team plan, coordination signals only: who is working, which repository, which file paths are claimed, and the agents' negotiation messages. The team view keeps the history of what was contracted: who agreed what, and when. Never the code it was about. Legal basis: performing our contract with the team.
Seat posture. On managed teams, whether a machine's policy wiring is in place, as a fingerprint and a per-seat status. Posture describes the seat, never a person's activity or output. Legal basis: our and the team's legitimate interest in knowing governance is in place.
Device records. A per-machine credential and a name for it, so you can see and revoke your own machines. Legal basis: performing our contract and keeping accounts secure.
Early-access sign-ups. If you join the list on this website we store the email address you give us and which plan you were interested in, and use it to contact you about kn0t. Legal basis: consent; unsubscribe by replying or writing to hello@kn0t.ai.
Service logs. Our servers and content delivery network keep short-lived operational logs (request paths, timestamps, status codes and network addresses) to run and defend the service. Legal basis: legitimate interest in operating securely.
What we do not do
- We do not sell personal data, and we do not share it for advertising.
- This website runs no third-party analytics or advertising trackers.
- We do not train models on your data. Your code is not ours to learn from.
Who processes data for us
Amazon Web Services hosts the service in the London region (eu-west-2). Stripe processes payments; Stripe's own processing may involve transfers outside the UK under its published safeguards. We use no other subprocessors for personal data.
Retention
Account and team data is kept while the account or team exists and deleted on request or closure, except where billing records must be retained by law. Early-access emails are kept until you unsubscribe or we launch past the list. Operational logs are short-lived.
Your rights
Under UK data protection law you can ask for access to, correction of, or deletion of your personal data, object to or restrict processing, and take your data with you. Write to hello@kn0t.ai and we will answer within a month. You can also complain to the Information Commissioner's Office (ico.org.uk).
Changes
If this policy changes, the effective date above moves and material changes are called out to account holders. The boundary claims themselves are a product contract, not small print: weakening them would be a product change, announced as one.