Your voice stays yours. Here is exactly how.

This policy applies to the Chitchat Buddy desktop application, the Buddy limited-access proxy, and this website. The responsible developer is Aliaksei Osipau. Chitchat Buddy is open-source software; third-party services have their own policies.

Buddy stores recordings, pause-cut playback audio, editable transcripts, dialog history, generated titles, pronunciation feedback, waveform data, preferences, and downloaded model files in your operating-system user profile. On Windows, the application data is under %LOCALAPPDATA%\Buddy.

Microphone capture, voice-activity detection, Whisper transcription, pronunciation analysis, silence removal, waveform creation, and Kokoro voice generation run locally. Buddy does not upload microphone audio as part of an AI dialog, monologue improvement, word definition, or recording-title request.

Buddy accesses the microphone only for features you start, such as a mic recording, dialog, monologue, or input test. A recording indicator is shown while capture is active. You control permission through your operating system and can stop recording at any time.

Buddy downloads speech and local-AI model files only after you start setup or activate the relevant option. Files may come from project release hosting or Hugging Face. Those hosts receive ordinary request information such as your IP address, user agent, time, and requested file. Buddy verifies expected file hashes where provided.

Hugging Face privacy policy ↗

The feedback form sends your message and, only if you attach it, one screenshot through the Buddy proxy to the developer's Telegram account. It also includes basic context needed to diagnose and route the report, such as app version, interface and dialog languages, a feedback identifier, and the trial-code display prefix. Audio and transcripts are never attached automatically.

Telegram processes the submitted material under its own policy. Review screenshots for private information before sending. There is currently no automatic expiry promise for delivered Telegram feedback; request deletion by quoting the feedback reference.

Telegram Privacy Policy ↗

The site stores your chosen display language in browser local storage and may request public release metadata from the GitHub Releases API to resolve download links. It has no advertising or third-party analytics. GitHub Pages and GitHub's API receive standard web-request data under GitHub's policy.

GitHub General Privacy Statement ↗

Buddy uses HTTPS for remote requests, operating-system secure storage for API keys, bounded upload sizes, and hashed trial codes on the proxy. No system is perfectly secure. Keep your device account protected and do not share provider keys.

Information is disclosed only to a service you select, to providers needed to deliver a feature you invoke, where required by law, or to protect the service from abuse. Buddy does not sell personal data.

Local recordings and text remain until you delete them or reset Buddy's local state. Uninstalling an application may leave its user-data folder, so remove it separately if you want a complete local deletion. Saved provider credentials can be removed in Settings.

Proxy usage rows remain while needed to enforce the issued code's quota and operate the service; no automatic expiry is currently promised. Third-party providers control their own retention. Contact us about proxy or feedback records and include the visible code prefix or feedback reference without sending the full secret key.

• Deny or revoke microphone permission.
• Use recordings, transcription, and local speech without a cloud account.
• Select local Qwen where it is available, or avoid cloud AI actions.
• Edit text before requesting an improvement.
• Remove saved API keys, recordings, transcripts, and local model files.
• Ask for access, correction, or deletion of feedback or identifiable proxy records where applicable.

Buddy is not directed to children under 13. Cloud services may impose a higher minimum age in your country. We may revise this policy as the product or providers change; the effective date above identifies the current version.