Plain description of what the product does with your meetings. It is not a substitute for legal advice about recording where you are.
When the notetaker joins a meeting, it captures the live captions Google Meet produces, attributed to the display name each participant is showing. It does not record audio or video, and it does not store one.
We also store the meeting title, its start and end time, the organiser, and the invitee list — all read from the calendar you connect — plus the notes written from the transcript.
The notetaker posts a message in the meeting chat when it joins, naming who it is taking notes for, and it leaves if anyone asks it to. You can change the wording; you cannot turn the announcement off. In several jurisdictions everyone on a call must know it is being recorded, and a silent recorder is your legal problem, not a feature.
Two separate connections, and neither gives us your password. Signing in with Google tells us who you are and nothing else. Connecting a calendar grants read-only access to it — we never write to your calendar.
The account the notetaker joins as is paired by signing in to Google's own page in a browser we run for the length of that sign-in. We keep only the resulting session, encrypted. We never see the password, and the browser is destroyed on a hard timer whether or not anything else behaves.
Transcripts are sent to a model provider to write the notes, and are not used to train anyone's model. Notes are emailed to the meeting's invitees, minus anyone who declined, and posted to Slack if you configure that.
Workspaces are isolated at the database level, not only in application code: every query runs under a policy that returns nothing unless it names the workspace it belongs to.
Deleting a meeting deletes its transcript. Deleting your workspace deletes everything belonging to it, including the paired Google session. Disconnecting the calendar stops any further meetings being picked up.
Ask us at hello@cruq.ai and we will do any of this for you.