Please do not open a public Issue for a vulnerability involving capture contents, local file access, permissions, or unintended data disclosure.
Report security issues privately through GitHub Security Advisories for this repository. Include the affected revision, reproduction steps, and expected impact. Remove personal screen contents, tokens, and credentials from logs or sample files.
kiri is local-first and does not upload captures automatically. A change that transfers capture contents or other user data must make the destination and user action explicit.
Editable annotation documents are treated as untrusted local input. Kiri validates their schema and bounds, verifies the source and flattened-image hashes, and refuses stale editor saves instead of pairing a document with a different image revision. Native Save panels issue a one-time destination authorization; unrestricted filesystem paths are not exposed to the WebView.
Recording or explicit GIF conversion may download the FFmpeg executable once when no usable local copy is available. This dependency request contains no capture contents, filenames, library metadata, credentials, or account identifier. The executable is cached locally and all media encoding remains on the device. Automatic downloads use platform-specific, version-pinned archives; Kiri verifies the archive SHA-256 before extraction and validates the executable before use.
- macOS: FFmpeg 9.0 from
ffmpeg.martin-riedl.de - Windows x64: FFmpeg 9.0.1 from the
GyanD/codexffmpegrelease repository ongithub.com
Optional remote OCR follows that rule per image. The app prepares only the selected region locally, discloses the configured provider origin, model, and image size, and sends it only after the user activates a visible Send or Retry action. Return uses local OCR for that image. Failed requests are never retried, rerouted, or uploaded through a fallback provider automatically.
Remote OCR API keys are write-only inputs stored in macOS Keychain or Windows Credential Manager. They must not appear in profile JSON, IPC responses, logs, screenshots, crash reports, fixtures, or environment-variable fallbacks.