Documents and evidence
The documents on hosting, processing and leaving are public. You can read them before you create an account.
Notes and documents are stored in your workspace. The agreement specifies hosting at Hetzner in Nuremberg. You can use the knowledge store independently of your chosen AI tool.
A connected tool requests knowledge with its own access token. knowmind returns the matching excerpts with their source. The rights of that token decide which content it reaches.
Your tool processes the retrieved excerpts with its own model. What happens to them there is set out in the terms of your tool and model provider.
A key of an AI provider that you store in knowmind is kept encrypted; your content is not sent to that provider over this key.
Several independent layers of protection work together. This section states what each one does and where its limit lies.
Everything exchanged between your browser or AI tool and knowmind is encrypted in transit (TLS). All we hold of your password is a checksum that cannot be turned back into the password. The same holds for your access keys.
Your memories and documents sit on the server in plain text. They are protected by the fact that nobody reaches them without permission: every request has to identify itself, and every workspace is separated from all others in the database.
The separation of workspaces sits in the database itself, one layer below the software. If the software had a fault and asked for content from another workspace, the database would still not hand it over.
You sign in with a sign-in link we send you by email; it is valid for 24 hours and can be redeemed only once. If you prefer a password, you set one in your profile. From the Business plan on, your people sign in through your company directory; you set that up yourself in the Cockpit. The server limits how many sign-in attempts and how many questions are possible in a short time.
For write operations from the browser, knowmind checks that they come from its own interface. Manipulated links and forms planted on other websites therefore have no effect. Access through the API is protected by the access token.
The access log records sign-ins, the issuing and revoking of access tokens, changes of plan and new workspaces. You read it in the Cockpit and download it as a file. Retention depends on the plan: 30 days on Private, 90 days on Pro, 12 months on Team, 24 months on Business and 5 years on Enterprise.
knowmind is operated by Johann Jörgen Schübeler, Schübeler Consulting. The legal notice gives the address and contact; the data processing agreement names the data centre and the service providers involved.
Hetzner publishes the ISO 27001 certification scope of its infrastructure. The link takes you directly to the hosting provider’s information.
The security documentation explains access, the separation between workspaces and the data paths.
For company use, we agree on access, retention and the evidence you need before you start.
A free workspace is enough for your own test. For company use, we discuss scope, data and acceptance criteria with you first.
