01
Security by product
Security controls are evaluated in the context of each VibeX HQ product, its architecture, and its stage of development. We do not present roadmap work as completed protection.
VibeX HQ security
Security should be communicated as clearly as the product itself.
VibeX HQ develops software products with an emphasis on clear ownership, responsible infrastructure choices, and truthful communication about what protections are in place.
Security principles · 01
A company-level approach to security.
VibeX HQ builds distinct products, so security claims should remain specific to the systems and products they actually describe.
02
Clear boundaries
We aim to communicate what a product stores, what systems it depends on, and where responsibility sits between VibeX HQ, our infrastructure providers, and the people using our software.
03
Responsible disclosure
We welcome good-faith reports that help us identify and resolve security issues before they can cause harm.
Responsible disclosure · 02
Report a vulnerability
If you believe you have found a security issue affecting VibeX HQ or one of our products, please report it privately with enough detail for us to understand and reproduce the issue.
security@vibexhq.comPlease avoid publicly disclosing a vulnerability before we have had a reasonable opportunity to investigate and respond.