Security is central to how Vijnara is built. If you believe you've found a vulnerability in our platform or website, please report it to security@vijnara.com. We commit to acknowledging your report, investigating promptly, and keeping you informed.
We value the work of the security community and believe coordinated, responsible disclosure makes everyone safer. We will investigate all legitimate reports in good faith, work to remediate confirmed issues in a timely manner, and recognize researchers who help us improve — while protecting our customers' data throughout.
Email security@vijnara.com with enough detail for us to reproduce and assess the issue. A helpful report typically includes:
For sensitive reports, request our PGP key and we'll provide an encrypted channel.
To keep testing safe and lawful, we ask that you:
We will not pursue legal action against researchers who act in good faith and comply with these guidelines, including the scope and conduct expectations above. We consider activity conducted consistently with this policy to be authorized, and will work with you to understand and resolve issues quickly. If legal action is initiated by a third party against you for activity that complied with this policy, we will make this authorization known.
We aim to confirm receipt of your report within two business days.
We triage, validate and assess severity, and may follow up for more detail.
We fix confirmed issues based on severity and keep you updated on progress.
With your consent, we're happy to credit you once the issue is resolved.
Vijnara is built with security at its core: permission-aware retrieval, encryption in transit and at rest, role- and department-based access controls, audit logging, multi-tenant isolation, and least-privilege internal access. Our architecture is designed to align with frameworks such as SOC 2, ISO 27001, GDPR and HIPAA; specific certifications depend on deployment configuration. For deployment-specific documentation, contact our team.
Report a vulnerability or request our security documentation: