Privacy policy
Last updated:
This policy explains how Kesami handles information when you visit this website or use the Kesami desktop meeting assistant.
Meeting recordings and your library
Kesami captures microphone and system audio when you start recording. Screen recordings are captured when you choose that feature. Recordings, transcripts and summaries are saved on your computer, normally in Documents / Kesami Meetings. Local databases also support features such as meeting search and chat history. Signing in does not automatically sync your meeting library to the cloud.
You control what you record. Obtain the permissions and participant consent required for your meeting before recording or sharing it. People using the same Kesami workspace on a computer may have access to the same meeting library.
Optional Google Drive and Dropbox storage
Connecting cloud storage is separate from signing in. If you enable recording uploads or meeting backups, the desktop app sends the selected content directly to your own Google Drive or Dropbox account. Recording uploads contain the media file; full meeting backups can also include meeting details, transcripts, summaries and folder information. These files do not pass through Kesami’s recording servers. They consume your provider account’s storage and are governed by its terms and privacy policy.
Google Drive access uses the drive.file permission, which only reaches files Kesami creates or files you open with Kesami; Kesami cannot see the rest of your Drive. The same permission is used when you export meeting notes as a Google Doc. Dropbox uses a scoped app folder with account identity, file read/write and metadata permissions. OAuth credentials are encrypted through the operating system in the Electron main process and are not provided to the renderer. Cloud playback requests the media ranges needed to play and seek.
Local cleanup is off by default. If you enable it, verified cloud recordings may replace local media after your chosen retention period. Meeting notes remain local. You can keep a recording offline or download it again. Disconnecting or cleaning up a local recording does not delete the cloud copy. Deleting cloud copies requires a separate choice in the meeting deletion dialog.
Personal templates and optional account summaries
Personal note templates, including context and section instructions, are saved to your signed-in account. If you enable account summary storage, new and updated recaps, meeting titles, dates, decisions and action items are also stored in hosted account services. Existing summaries upload only when you choose that action. This summary feature does not upload transcripts, recordings, private notes or follow-up email drafts. Your recap may still contain sensitive information from the meeting.
Publishing a summary link makes the reviewed snapshot readable by anyone holding the link. Later edits do not appear until you publish an update. You can revoke the link or delete its account summary; this does not remove copies recipients already saved. Website analytics is disabled on these shared pages.
Cloud transcription and AI
Local storage does not mean all processing happens on your computer. During live transcription, audio is sent through Kesami’s cloud relay to Sarvam for speech recognition. When you request summary generation or ask an AI question, the meeting transcript or the relevant excerpts and your request are sent for AI processing, including to Google Gemini and, as a fallback, OpenAI. Provider configuration can differ in development builds.
These services receive the content needed to fulfil the requested feature. Their processing and retention are also governed by their applicable service terms and privacy policies. This policy does not promise that external providers never retain data.
Voice typing on macOS
Voice typing is off until you turn it on. While you dictate with Fn, the Kesami Voice Typing helper records your microphone and transcribes it with Apple’s on-device speech recognition, and its optional clean-up pass uses Apple Intelligence’s on-device model, so the audio and the transcript stay on your Mac. Recognising some languages, such as Hindi, first needs a one-time model download from Apple. The helper keeps your latest dictation in memory only and does not save transcripts, instructions or AI results. It saves its settings on your Mac: spoken language, clean-up level, sounds, review preference, custom words, snippets and where you placed the status line; Kesami also saves whether voice typing is on. To insert text, the helper briefly places it on your clipboard, pastes it into the field you are typing in and then restores your previous clipboard, except PDF, rich text with attachments, audio and file-promise contents, and a very large copy may come back only in part; if no field takes it, the text stays on your clipboard. It reads the focused field and, for voice commands, your selected text through macOS accessibility, or by copying the selection when an app does not expose it, in which case editors that copy the current line when nothing is selected send that line; it refuses password fields. When you use a voice command (Fn and Control) or Ask AI, only the selected or dictated text and your instruction are sent to the AI providers described above, and nothing is saved as a meeting. The helper asks macOS for Accessibility, Microphone and Speech Recognition permissions, and for Input Monitoring only if macOS refuses its keyboard shortcut handling; you can remove them at any time in System Settings.
Google sign-in
When you choose Continue with Google, Kesami requests basic account information through the openid, email and profile permissions. This can include your Google account identifier, email address, name and profile picture. Release builds use Supabase Authentication to manage sign-in and sessions. Account and session information is used to identify you, authenticate requests and provide access to hosted features.
Authentication services store account records and session information. The desktop app retains session credentials so you can stay signed in. Signing in requests only these basic permissions. It does not grant access to your Gmail, Google Drive files or Calendar events; Calendar and Drive are each requested separately, only when you choose to connect them.
Google Calendar permissions
Kesami asks for Google Calendar access only when you click Connect for Google Calendar, never at sign-in. It requests the calendar.events permission. With it, Kesami reads events on your primary calendar around the current time: titles, start and end times, descriptions, attendee names and email addresses, and meeting links. It uses them to show your agenda, remind you before a meeting starts and help you join and record it. Kesami also creates an event on your primary calendar, and sends invitations to the guests you add, when you schedule a meeting from New meeting or when you review and approve a follow-up meeting it suggests. It does not change or delete existing events.
When you record a meeting that came from your calendar, the event title and attendee names are saved with that meeting on your computer. They are included in the request sent to the AI providers described above (Google Gemini and, as a fallback, OpenAI) when Kesami generates that meeting’s summary or answers your questions about it. This lets the summary name the right people. Calendar data is not shared with anyone else, except as needed to comply with the law.
Calendar connection credentials are stored on your computer in a file only your user account can read, and they are not provided to the app’s interface. To renew access, the desktop app sends the refresh credential over HTTPS to Kesami’s sign-in relay, which exchanges it with Google and does not store it. Recently fetched events are cached on your computer so your agenda loads quickly. Disconnecting Google Calendar in Kesami deletes the stored credentials and the event cache. You can also revoke access at any time in your Google Account connections. Event details saved with a recorded meeting stay until you delete that meeting.
Google user data and Limited Use
Kesami’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide and improve the user-facing features described in this policy. It is not sold, not used for advertising, retargeting or credit decisions, and not transferred to data brokers. People do not read it unless you ask for support, security requires it, or the law requires it.
Kesami does not use Google Workspace API data, including Calendar and Drive data, to develop, improve or train generalised AI or machine-learning models. When Google user data is part of an AI request, it goes only to providers whose API terms do not allow them to use API inputs to train their models.
Subscriptions and payments
If you purchase a plan, payment providers process your payment information. Kesami uses account identifiers, subscription status and payment references to verify access to paid features. Billing records may be stored locally and in hosted services. Payment providers handle the payment details submitted to their checkout.
Website analytics and preferences
This website uses Vercel hosting and Vercel Web Analytics to understand website visits, including pages visited and general device and browser information. See Vercel’s analytics privacy documentation. The website stores your currency preference in your browser’s local storage. Visiting the website does not upload your desktop meeting library.
Sharing, security and retention
Information is shared with services needed to operate the features you use, including authentication, transcription, AI, hosting and payments. Information may also need to be disclosed to comply with applicable law or address security incidents. Hosted features use encrypted HTTPS or secure WebSocket connections. Local files remain subject to your computer’s permissions, backups and security settings.
Local meeting notes remain until you delete them. Local recordings may also be removed by optional verified cloud cleanup. Cloud copies, backups and exported copies must be managed separately. Account, operational and billing records may remain while needed to provide the service, address security issues or meet legal obligations. Revoking Google access does not itself delete existing local files or hosted account and billing records.
Your controls and privacy requests
You can stop recording, delete meeting files you control, sign out and revoke Kesami’s Google access through your Google Account connections. You can remove microphone and screen recording permissions, and on a Mac the voice typing helper’s accessibility, speech recognition and, if granted, input monitoring permissions, in your operating system’s privacy settings.
For questions about Google account data or requests to delete hosted account information, use the developer contact email displayed on Kesami’s Google consent screen. Do not send recordings, access tokens or other sensitive information in an initial request.
Changes to this policy
Updates will be published on this page with a revised date. If Google data is to be used for a new purpose, the relevant disclosures and consent will be updated before that use begins.
Read the Terms of service for the conditions of using Kesami.