Meeting notes for Infomaniak kMeet

    You chose kMeet because you wanted your conversations to run on Swiss servers. For meeting notes, that leaves you with a problem the platform did not cause: the widely used AI notetakers are built around Google Meet, Microsoft Teams and Zoom. None of them lists kMeet.

    Book a call

    A bot that joins kMeet

    My notetaker joins kMeet sessions through the normal meeting link. It records and transcribes on a server you own, or on one you can cancel without copies staying behind. The transcript then goes into an automation layer on the same infrastructure. Only there is the summary written, and only there do you decide which language model writes it.

    How it works

    1. 1

      You set up the meeting in kMeet as usual.

    2. 2

      The meeting link goes to the bot, either by hand or automatically through your calendar.

    3. 3

      The bot joins and announces what is being recorded, where it is stored and how long it stays. If anyone objects, it stops.

    4. 4

      After the meeting the summary lands where you want it: file storage, task list, CRM.

    kMeet can record and summarise on its own

    kMeet has a built-in recording feature. The recording runs on Infomaniak's servers, is saved as a video to your kDrive and is limited to three hours. On a paid kDrive plan, Infomaniak's AI Euria also writes a summary of it. Recording requires an Infomaniak account and does not work with end-to-end encryption.

    If that is enough for you, you do not need my bot. The difference is where the data sits and who decides. With the built-in option, recording and summary sit with Infomaniak, and Infomaniak picks the language model. With my setup, recording and transcript sit on your server, you pick the model, and the summary goes straight on to your file storage, task list or CRM.

    With the waiting room on, someone has to let the bot in

    kMeet can hold participants in a waiting room. The bot is then an external guest like any other and waits until someone admits it. That is not a workaround. It is exactly the control the waiting room is there for.

    End-to-end encryption shuts the bot out

    kMeet encrypts meetings by default and also offers end-to-end encryption, which you can switch on when you create a meeting. Once it is on, nobody without the key can follow what is said – my notetaker included.

    That is the right order of priorities, not a shortcoming. Sessions that are meant to be minuted run without it. Sessions that nobody outside the room should ever read run with it and are not minuted. You make that call for each meeting, not once and for all.

    What you need

    A server in Europe or in Switzerland with a provider that has no US parent company, either your own or one at your existing host. That is where the setup runs. No subscription, no licence, no tie to me: the software is open source, and I am paid for my time.

    Recording is only allowed with everyone's knowledge

    Before you start, say what the recording is for, where it is stored and how long it stays. A voice counts as particularly sensitive personal data, and in Switzerland secretly recording a non-public conversation is a criminal matter on top of that. I describe the framework; your legal advisers have to assess it. The bot makes the announcement when it joins.