TeamKit was built around two things worth protecting: what a company knows, and the privacy of the people using it.
Everything is encrypted before it reaches the database. The key is generated per document and becomes part of the link you share with the others.
That key is never stored on the server, which means neither the people who wrote this application nor whoever runs it can read what is inside your tool.
A link can end up in the wrong hands, so there is a simple answer to that: a PIN. It stops anyone reaching the page, even holding a link with the key in it.
You can set or change the PIN whenever you like. Anyone opening the tool for the first time has to enter it.
Data that sits around for months and years does sometimes end up with intruders. For anything important, set a date for the tool to delete itself — a week, a month, whatever fits.
TeamKit also prints, and downloads as a Markdown file. Either way you keep the conclusions and can be sure they end up nowhere else.
Only what was typed into the tool, plus a little metadata: which tool it is, and when it deletes itself. None of that is personal data, unless you type personal data into the tool yourself.
TeamKit has no accounts and no sign-in, so there is no e-mail address, first name or surname to give.
There are no trackers and no analytics, so there is nothing else here that could leak anything about you.
TeamKit is open source and you can run your own copy — on your own server or on a local network. The instructions are in the project repository, along with the source.