Privacy — Kaoru

Privacy notice updated: September 21, 2026. Website translation: September 21, 2026.

This notice describes the information the Kaoru desktop application may process, where it is stored, when it may leave your device and the controls available to you. The existing Spanish notice was prepared with reference to Mexico’s Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP). It describes the implementation and does not replace a professional legal review for a specific distribution or activity. The Spanish version is the canonical text.

Kaoru does not operate a central conversation storage server. Memory, embeddings, preferences and telemetry are stored locally. It is not necessarily offline: selected messages and context may reach your AI provider; speech synthesis uses Microsoft; integrations, websites and plugins you enable may receive data needed for a task.

1. Operator and contact

Kaoru is an independent project developed by Dregxmoon, based in Tijuana, Baja California, Mexico. Send privacy requests and questions to dregxmoon@gmail.com. Dregxmoon does not automatically receive a copy of your local database or configured keys.

2. Data and purposes

Category	Examples and purpose
Conversation and selected files	Messages, attachments, workspace excerpts and tool results used to respond, plan, execute and verify your task.
Memory and sessions	Stated facts, preferences, episodes, conversation history, intentions and inferred beliefs labeled as such, used for continuity, semantic retrieval and personalization.
System context	Active application or window, idle time, resource use, Git/LSP signals, error titles, reminders and technical clipboard content when enabled; used for context and policy-based suggestions.
Automation	Accessibility trees, windows, screenshots, temporary coordinates, process names/IDs and action results, used to operate and check interfaces you request.
Integrations	Content from enabled Google Workspace, GitHub, websites or plugins, used for the selected tool or integration.
Local diagnostics	Duration, tool, outcome, failure category and technical logs, used for debugging, security and local metrics.
Credentials	API keys, OAuth tokens and provider settings used to authenticate your configured connections.

Responding and maintaining a session are core functions. Persistent memory, proactivity, sensors, voice, Google/GitHub, automation and plugins are functions you choose to configure or use. Avoid unnecessary sensitive data and third-party information you are not authorized to process.

3. Transfers and third parties

Your active LLM provider receives the prompt needed to respond. It may contain messages, retrieved memory, system context, file or connected-service content, tool results, terminal output you explicitly attach and send, and JPEG/PNG screenshots for a visual task. Kaoru supports integrated providers and compatible endpoints, including local endpoints. The application’s selector shows the available catalog.

Chosen LLM provider: its contract, region, retention and data policy apply. Review them before adding a key or endpoint.
Microsoft Edge TTS: receives the text to synthesize. The current interface does not offer microphone input.
Google and GitHub: receive direct calls from your device when you connect and use those accounts.
Websites and browsing: sites receive requests, your IP address and submitted data; their cookies and policies apply.
Plugins: third-party extensions may receive context or execute code according to their implementation. Review their origins and permissions.
Catalog and updates: Kaoru may query public model metadata at models.dev and releases on GitHub; those queries do not need to include your conversation.

Dregxmoon does not sell personal data or use it for behavioral advertising. Configured third-party requests travel directly from your device and are also subject to the recipient’s terms and policies.

Provider references: OpenAI, Google, Microsoft and GitHub. Review the policy of any other provider you connect.

4. Google Workspace and Limited Use

The built-in Google Workspace connection is unavailable in the current public version. In older installations where it remains active, you provide the OAuth client and choose services and scopes: Calendar, Gmail, Drive, Docs, Sheets, Tasks or Contacts; read-only or write access where supported. Authorize the minimum scope needed and revoke it when no longer required.

Kaoru’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including Limited Use requirements. Data is used to provide or improve the user-requested visible feature; it is not sold, used for advertising or transferred to people for unrelated purposes. It may reach your chosen LLM provider only when necessary for your requested action, such as summarizing an email.

5. Desktop, browser and permissions

Application, browser, screen, pointer, keyboard, process and camera capabilities have separate switches. Rules can allow, ask or deny. Approval reduces risk but does not guarantee an action’s outcome.

Accessibility: AT-SPI2 on Linux and UI Automation on Windows expose controls. macOS does not yet have equivalent semantic control.
Screenshots and visual clicks: coordinates are linked to a captured image, expire after 30 seconds, are single-use and require a new observation. The image may reach the active vision-capable LLM.
Personal browser: open_website asks the OS to open a URL in your default browser, retaining its session. Kaoru does not directly import its cookies or passwords.
Managed browser: searchable and verifiable flows use a separate persistent Chromium profile. Login cookies remain in Kaoru’s data directory until removed.
Processes: Kaoru can list names and IDs and request termination. Review the target; termination may not have a verified postcondition.
Camera: the current tool checks status or opens the camera app. It does not capture photographs or record video.

6. Storage and security

Memory, sessions, telemetry and configuration are stored in Electron’s local userData directory. Embeddings are computed locally. Credentials preferentially use the OS secure store (Keychain, Credential Manager or Secret Service). If unavailable, supported fallbacks may leave credentials in local configuration or environment files readable by your account. Protect your device, files and backups; local storage does not imply full database encryption.

The language preference (available since v2.3) is stored in the same local configuration. It is not a new telemetry field and does not change which content is sent to your selected provider.

7. Retention and deletion

Data	Retention
Application history	Pruned after 30 days.
Local telemetry	Up to 90 days.
Logs	An active file and one rotation, up to 5 MiB each. Rotation depends on size, not age.
Pointer-linked screenshot	In-memory reference for up to 30 seconds or the first click. Copies sent to providers follow their policies.
Memory and sessions	Until deleted or archived by decay rules. Archiving is logical deletion, not immediate physical erasure.
Managed browser profile and checkpoints	Remain locally until manual cleanup or the corresponding feature removes them.

You can ask Kaoru to forget memories, disconnect integrations, or use Settings → Recovery and local data → Erase all Kaoru data. After explicit confirmation, this removes Kaoru configuration, memory, sessions, permissions, caches, and local credentials; it does not delete projects, Documents, or workspaces. On Windows, the interactive uninstaller also offers this option. System backups, environment variables, and external providers have separate lifecycles.

8. Rights and revocation

You may request access, rectification, cancellation or opposition (ARCO rights), limit use or revoke consent through the contact email. Describe your request sufficiently; reasonable identity verification may be requested. Most data is on your device and can also be inspected or removed locally.

Revoke Google access from Google account permissions and GitHub access from that account’s authorized application settings. Revocation prevents future access but does not automatically erase copies already sent to providers or backups.

9. Authorized use and minors

Use Kaoru only on authorized devices, accounts and workspaces. Do not monitor other people without their knowledge and consent. Respect workplace or educational policies. Kaoru is intended for adults aged 18 or the applicable age of majority and does not intentionally seek to collect children’s data.

10. Changes

This public website stores your light/dark theme choice in browser localStorage. It includes no analytics or forms. Images, styles and scripts are served by the site itself. Hosting processes requests needed to deliver pages; opening an external link also invokes the destination site's practices.

This notice will be updated when capabilities, providers or practices materially change. The date identifies the version. Material changes should be communicated in the repository or application before or when they take effect where reasonably possible.

Legal reference: LFPDPPP published by Mexico’s Chamber of Deputies.