Privacy overview
Meeting context deserves deliberate handling.
Information involved in the service
Account information can include an email address and authentication data needed to provide access. Meeting information can include a title or identifier, participant and speaker context, timestamps, captured audio or video, a transcript, processing status, and AI-generated outputs such as summaries or actions. Technical logs may be used to operate, secure, diagnose, and improve the beta service.
Why the information is used
Kanoe uses information to authenticate users, run a requested meeting capture, create and display meeting records, generate useful meeting context, maintain the application, and respond to support or security questions. Meeting material is intended for the account or workspace that requested it; it is not published through the public marketing pages. Users should review generated output against the source when an exact detail matters.
Recording notice and consent
Laws and organizational policies can require notice or consent before a conversation is recorded or transcribed. The person or organization using Kanoe is responsible for informing participants, identifying the purpose of capture, limiting access appropriately, and satisfying applicable requirements. Kanoe should not be used to secretly record a meeting or to collect information that the user is not authorized to process.
Access, retention, and security
Authenticated application areas separate private meeting records from public product information. Account holders should use unique credentials, share workspace access carefully, and remove access that is no longer needed. Retention needs differ across teams; beta users should not assume that Kanoe replaces their own retention, backup, compliance, or legal-hold procedures. No internet service can promise absolute security.
Questions and requests
Privacy questions can be sent to admin@meetkanoe.com with the subject “Privacy.” Describe the relevant account or workflow without placing passwords, authentication tokens, or private meeting content in the first email. The team may need to verify the requester before acting on a request that concerns account information. This overview may be updated as the beta, its infrastructure, and applicable product terms evolve.