- What CapKB collects
- Nothing about you and nothing about your images. There is no backend, no account, no login, no analytics, no crash reporting and no update check, so there is no mechanism by which anything could be collected. The one thing CapKB writes about you is a local settings file in its own config folder with three fields: whether to save beside the source, the last output folder you chose, and the last preset you picked.
- Where processing happens
- Every image is decoded, resized and re-encoded in CapKB's own process on your machine. The named exception, stated because an unqualified absolute would be false: HEIC and HEIF decoding is handed to Windows Imaging Component, an operating-system component. That is still local, running in the app's process against a file on your disk, but it is not our code, and it is why the HEIC answer depends on what Windows has installed.
- What leaves your machine
- Your images never leave this PC, and CapKB contains no network code: no HTTP client, no socket, no update check and no licence call. That was measured against the built program on 2026-09-01, not read off the source: CapKB's own process opened no outbound connection in any run, including one that put four photographs through it in six passes. The Windows component that draws its window does talk to Microsoft on its own account. CapKB turns that down as far as the platform allows, and one Microsoft endpoint remains that no setting of ours removes.
- Effective date
- 2026-09-01