Security reporting route: keep credentials, client documents, databases and captures out of public issues, report vulnerabilities privately via GitHub security advisories with a synthetic reproduction, keep engine and ingest on loopback, treat detailed capture as opt-in confidential, and back up installation state before updates. Read before reporting a vulnerability or handling sensitive data.
Security
Do not include credentials, client documents, native databases or full-content captures in public issues. Report a suspected vulnerability privately using GitHub security advisories. Include a synthetic reproduction and affected revision.
The default setup is local. Keep engine and ingest on loopback. Detailed capture is opt-in and can contain confidential content; store it privately and delete it deliberately when no longer needed. Back up installation state before updates.