Security Policy
From Zacess main at 9d13dfb. Edit this page on GitHub
Zacess keeps people's documents, notes, recordings and reading profiles on their own devices. A flaw that exposes that material or lets a document run code is treated as urgent.
Reporting a vulnerability
Important
Report privately, never in a public issue or discussion. Email security@zacess.com with details and reproduction steps. Once the code is public in zacesshq/zacess, GitHub private vulnerability reporting on that repository is the preferred route.
Supported versions
Zacess has not had its first release yet. Once it has, security fixes go to the latest release.