Legal

Security and Responsible Disclosure

How to report a suspected vulnerability without harming users or systems.

Last updated 31 Oct 2026

  1. In short

    Report suspected vulnerabilities privately to support@darkhorsestocks.in with the subject “Security report”. Stop if you encounter another person's information or a risk of disruption.

    This policy grants limited permission for non-invasive, good-faith inspection described below. Active testing needs prior written approval. It is not immunity from law or permission to test third-party systems.

  2. Limited standing permission

    You may inspect publicly delivered Fundalysis pages and client-side resources through ordinary use, and report a weakness you observe. You may use only your own authorised account and information if accounts are available. Do not alter permissions or deliberately access information outside that authorisation.

    Obtain written agreement on scope, methods, timing and safeguards before scanning, automated probing or exploitation. This policy does not authorise testing AWS, fund houses, data suppliers, other DARKHORSESTOCKS services or any other third party.

  3. Protect people and availability

    Do not extract data, modify records, establish persistence, use malware, conduct social engineering, guess credentials, deny service or access another person's account. Do not demand payment to keep a vulnerability private.

    If you unexpectedly encounter personal information, stop, avoid further copying and tell us privately. Provide the minimum evidence needed. Agree a secure transfer and deletion process before sharing sensitive evidence.

  4. What to report

    Include the affected address or interface, the time observed, steps sufficient to reproduce safely, expected and actual behaviour, and your contact details if you want a response. Redact credentials and personal information. Ask us for a suitable secure channel before sending sensitive material.

  5. Our response

    We aim to acknowledge a report within two business days, assess its impact and keep the reporter informed where practicable. We prioritise risk to users and service integrity. Acknowledgement is not a promise of a particular fix date or a bounty.

    We will comply with applicable incident-reporting duties without waiting for a coordinated publication date. Please agree a reasonable disclosure timetable with us so users can be protected. This request does not prohibit disclosures protected or required by law.

  6. Our limited safe-harbour commitment

    For good-faith activity within this policy or a written testing authorisation, we will not bring a civil claim or initiate a criminal complaint merely because you conducted that authorised activity. If asked, we will explain the scope of our authorisation truthfully.

    This commitment binds only us. It cannot bind police, regulators, courts or third-party rights owners, excuse unlawful conduct, or authorise access beyond systems and methods we control. Accidental departures should be reported promptly; we will assess their circumstances fairly.

  7. Security limits

    The existence of this policy does not mean every vulnerability has been found or that the service cannot be compromised. Our reasonable security and legal reporting duties continue regardless of contractual disclaimers. See the Privacy Policy for personal-data incident handling.