Kesami · Legal
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.
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 a summary is generated (automatically when a recording ends, unless you turn that off in settings) or you 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.
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 alone does not grant access to your Gmail, Google Drive files or Calendar events.
Google Calendar permissions
If you connect Google Calendar, Kesami requests Calendar event permissions separately. The integration accesses event details such as titles, times, descriptions, attendees and meeting links to display your schedule and help you join meetings. It can also create an event when you use the event creation feature. OAuth credentials are used to make these authorized requests and renew access where supported.
Calendar information is used for the connected calendar features. Kesami’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not sold or used for advertising or to train general-purpose AI 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 files remain until you delete them. 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 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.