The default backend uses an unofficial Doubao web protocol; the optional backend uses the official Volcengine Seed ASR API with a user-supplied key. The app also requests broad keyboard device access for global triggers. Use a normal user, never root. Review input group membership and /dev/uinput permissions before installation.

Recordings are sent to the selected provider for recognition; the microphone-only check stays local. Volcengine API usage and data handling follow the user's account and provider terms. The application does not intentionally retain recordings or transcripts on disk. The clipboard and target application may retain text. Older development logs can contain transcript excerpts: never attach them without review.

When optional voice polishing is enabled, recognized text is sent to the OpenAI-compatible endpoint selected by the user. This includes provisional text submitted after a pause while recording is still active. The endpoint operator's retention, training and privacy terms apply. Doubao Say does not log the text or include the polishing API key in diagnostics.

The application checks the fixed public GitHub Releases endpoint at most once every 24 hours. GitHub receives normal HTTPS connection metadata. The local owner-only cache contains only the check time and public release tag. The check does not send settings, account data, transcripts or a device identifier, and it does not download or install an update.

Sign-in cookies and the optional Volcengine API key are stored locally in separate, unencrypted files. New saves are atomic and mode 0600; loading valid older credentials restricts their permissions. Neither credential is included in diagnostics. Anyone with access to your account or root privileges may still read them. Uninstall preserves credentials, settings and runtime deliberately; it is not account revocation.

Report ordinary bugs through Doubao Say Issues. Include the affected version, sanitized reproduction steps and impact. Remove API keys, cookies, personal transcripts and device identifiers before posting. Report vulnerabilities through the repository's private vulnerability-reporting form when it is available. Otherwise, open a sanitized issue asking the maintainer for a private contact channel. Do not publish exploit details or sensitive attachments in an issue.

Local bundles are unsigned. Their file manifests/SHA256 sums detect changes only when obtained through a trusted channel; they do not establish publisher identity. Run make marketplace-check with Gitleaks on PATH to repeat a redacted scan of all locally available Git refs and the Git-visible working tree. It requires a full clone. Scanning is not proof that all sensitive information is absent; review historical screenshots and personal data separately before publication. No independent penetration test or complete dependency license audit has been completed. Before release, review the exact dependency notices and complete the clean-system installation and live desktop acceptance described in packaging/INSTALL.md. Source provenance and inherited licensing are documented in NOTICE.