Kucedr Cloud waitlist
If you join the Kucedr Cloud waitlist on this website, your email address is sent through our signup endpoint and stored as a contact in Resend, our mailing list service. Your email address will be used only to send updates about Kucedr Cloud. This signup is separate from the local data stored by the Kucedr desktop application.
You can unsubscribe through the link in our emails or contact harald.bregu@kucedr.com to request removal from the waitlist. We retain your email address while you are on the list; an unsubscribe status may remain in Resend to prevent further mailings.
Information handled by Kucedr
This Privacy Policy describes how the Kucedr desktop application handles your information, including data used by its optional integrations. Kucedr is designed to run locally. Conversation history, memory, project data, generated media, settings, and integration configuration are stored in the application data on your computer. Kucedr does not require an online account for these features.
When you configure an AI, search, media, messaging, or other provider, Kucedr sends the information needed for the action to the provider you select. The provider's own terms and privacy policy govern its processing and retention. Review those terms and the provider's settings before sending sensitive information.
Google user data
Google integrations are optional. If you connect one, Kucedr requests the permissions shown by Google for that service. Depending on the connection, Kucedr may access Gmail messages, drafts, message headers, labels, basic settings, and filters; Google Calendar calendars, events, properties, subscriptions, and sharing permissions; Google Drive files and metadata, including recordings and transcripts created or edited by Google Meet and available in Drive; and Google Photos photos, videos, and albums. Kucedr uses this access to perform the tasks you request through the desktop assistant.
Kucedr uses Google data only to provide the connected features and carry out your requests, including reviewing and organizing email, preparing replies, managing calendars and events, working with Drive files, reviewing meeting materials, and consulting photos, videos, and albums. The available operations depend on the permissions you grant and the tools provided by the connected service.
Google data and tool results are handled on your computer as part of your request. Relevant content, such as an email conversation or a document you ask Kucedr to summarize, may be sent to your selected AI provider to process that request. Any such transfer is limited to providing the requested assistance and is subject to the same restrictions on advertising, sale of data, and development, improvement, or training of non-personalized AI or machine-learning models. The provider’s terms, retention settings, and privacy policy also apply to its processing; they do not override these restrictions on Google data.
Kucedr does not use or transfer Google user data for advertising, sale of data, or the development, improvement, or training of generalized or non-personalized AI or machine-learning models. Google data is used exclusively for the user-facing features and requests described here. Use of information received from Google Workspace adheres to the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace User Data and Developer Policy.
OAuth access and refresh tokens are kept in Kucedr's local application data. Kucedr uses Electron's operating-system-backed safe storage to encrypt stored integration secrets when it is available; if it is unavailable, secrets are held in memory for the current session rather than written unencrypted to disk. Requests to Google and selected AI providers are transmitted over their HTTPS endpoints. No additional Kucedr server receives Google content as part of these requests.
Kucedr does not operate a server-side database of Google content. Google content may remain in local conversation history, memory, project files, or other local data if you choose to save or use it there; it is then subject to the retention and deletion controls for that local feature. OAuth tokens remain stored until you disconnect or remove the integration, clear Kucedr's application data, or revoke access in your Google Account. Disconnecting prevents future access through that connection but does not remove content you previously saved in conversations or files, nor data already received by Google or an AI provider. Delete those items in Kucedr and separately review or revoke third-party access in your Google Account as needed.
Why Kucedr uses Google data
Google Calendar: Kucedr uses calendars and events to help you review your schedule and organize activities. At your request, it can consult or manage calendars and events, create secondary calendars, change calendar properties and subscriptions, and manage sharing permissions. Reading access supports schedule review; editing access is needed when you ask Kucedr to make changes.
Gmail: Kucedr searches and reads email, including message headers and labels, so it can help you find information, summarize conversations, and prepare replies. At your request, it can read, create, update, permanently delete, and send drafts, and send messages on your behalf. It can also organize mail by applying labels, archiving messages, or changing their read status, and consult or manage basic Gmail settings and filters according to your instructions. Access to existing messages provides the context for your request; draft, sending, and editing permissions support the changes and communications you ask it to perform.
Google Drive: Kucedr searches, reads, and downloads files to find and use documents already in your account for the tasks you request. It can create and upload content, modify or delete files, and read or update file metadata according to your instructions. Metadata, such as file names and folder locations, helps it identify and organize the relevant documents. Access to existing files supports work on materials you have already stored in Drive; editing access supports the file changes you request.
Google Meet files in Drive: Kucedr retrieves files created or edited by Google Meet, including recordings and transcripts available in Drive, when you ask it to review meeting materials, summarize their contents, or prepare a follow-up. These files supply the meeting context needed for that request.
Google Photos: Kucedr uses access to photos, videos, and albums to help you view media and use relevant visual content in tasks you request. The media supplies context for the requested assistance.
Your choices and security
You choose which providers to connect, which Google integrations to enable, what data to make available, and which actions to request or approve. You can disconnect an integration in Kucedr and revoke its access in your Google Account. You can remove locally stored application data using the relevant Kucedr controls or by removing the application's data from your computer.
Protect your computer, operating-system account, backups, provider credentials, and connected services. Local storage and operating-system-backed credential protection do not protect data from someone who can access your unlocked computer or account. Do not send personal or confidential information to a provider unless you understand how it processes that information.
Third-party services
When you connect third-party services in the Kucedr desktop app, those services process the information needed to perform the actions you request. Google, AI providers, and other connected services operate independently under their own policies. Kucedr does not control their systems or retention practices.
Children and contact
The Kucedr desktop application is not intended for children under 13.
For privacy questions, contact Harald Bregu at harald.bregu@kucedr.com. If Kucedr changes how it accesses, uses, stores, or shares Google user data, this policy will be updated and users will be notified before the new use begins and asked to consent where required. Last updated: October 9, 2026.