Security · CaptureFlow

Security

Last updated 10 October 2026

How your captures are protected

Reporting a vulnerability

If you've found a security issue in CaptureFlow, the website, the extension, the desktop app, or the hosted service, please email us before telling anyone else. Include what you found, how to reproduce it, and what an attacker could do with it. We'll confirm we've received it and keep you updated while we fix it.

Please report privately rather than opening a public GitHub issue, so the fix can ship before the details are public.

Testing guidelines

We won't take action against good-faith research that:

Self-hosted instances

Vulnerabilities in the CaptureFlow code affect self-hosted instances too, so we want to hear about them. Issues specific to how someone has configured their own instance should go to that instance's operator.

Contact

Report a vulnerability, or ask a security question, at support@captureflow.dev.