Add SECURITY.md to define vulnerability reporting and data security policy

[K-dev01]

hello @Gov-10 ,
The project handles sensitive legal documents and claims strong security/privacy features (encryption, secure storage, GDPR compliance, no third-party sharing). However, the repository currently does not include a SECURITY.md file that explains how security vulnerabilities should be reported.

Proposed Change:

Add a SECURITY.md file including:

Private process for reporting vulnerabilities (avoid public issues)

Preferred contact channel for disclosures

Responsible disclosure guidelines and response timeline

Scope of security concerns (document data, storage, auth, API)

Why this is important:

Provides a safe path for reporting vulnerabilities responsibly

Strengthens trust for startups/entrepreneurs using the platform

Aligns the project with GitHub/open-source security best practices

I’m a SWoC’26 contributor and would be happy to work on this if assigned.

[Amangp]

Hi @Gov-10 👋
I’d like to work on this issue under Social Winter of Code 2026 (SWoC’26).

I can add a well-structured SECURITY.md file following GitHub’s recommended security policy format, clearly outlining the vulnerability reporting process, preferred contact channels, responsible disclosure guidelines, and response timelines—aligned with the project’s security and privacy goals.

Please assign this issue to me if it’s available. Thank you!

[K-dev01]

@Amangp I hv clearly mentioned I m a contributor and I would like to work on this issue . You have been asking in the issues that raised by me and to assign to you