• Always conduct testing ethically and legally.
• Do not publicly disclose the vulnerability without obtaining explicit consent from Zerodha Broking Limited.
• Never attempt to access, modify, delete, or store user data.
• If using automated tools or scripts, ensure they do not cause harm or excessive traffic to our platforms.
• Use only your own accounts for testing. Do not interact with or exploit other real users' accounts.
• If you find multiple vulnerabilities, report them sequentially and not simultaneously, giving us time to respond.
• Do not conduct tests that may degrade our services or impact our users.

• Age: Participants must be 18 years or older at the time of entry.
• Affiliation: Individuals affiliated with Zerodha Broking Limited, including employees, contractors, and their immediate families, are not eligible to participate.
• Country of Residence: We accept submissions globally.
• Compliance: Researchers must be in full compliance with all terms and conditions of the Zerodha Broking Limited Bounty Initiative.

• Rate limits bounties are only considered if it causes a loss to business or customer data.
• Email Spoofing (SPF/DKIM/DMARC misconfiguration on domains which we do not use for sending mails)
• Content-Security-Policy configuration opinions
• Clickjacking on pages with no sensitive actions.
• Wordpress related reports including WP-JSON on Varsity or Z-connect.
• SSL Pinning bypass and bypassing root/jailbroken detection
• Known CVE vulnerabilities without proper proof of exploitability
• Cookie handling (e.g., missing HttpOnly/Secure flags) unless clear impact is demonstrated
• Missing HTTP security headers without actual impact POC
• Kite forum (We would soon be moving this portal to Discourse)
• https://developers.kite.trade (Any reports with respect to developers.kite.trade shall not be included, as we are currently undergoing changes on the website & it would only include Kite account based logins.)

• Denial of Service (DoS/DDoS) Attacks: Any attempts to disrupt the service is strictly prohibited.
• Physical Security: Physical attacks against offices, data centers, or any other physical assets.
• Third-party Platforms: Vulnerabilities in third-party components or services used by Zerodha Broking Limited but not under our direct control.
• Unconfirmed Reports: Reports without a clear proof-of-concept or lacking detailed steps to reproduce.
• Social Engineering: This includes spear-phishing, pretexting, baiting, and any other form of obtaining information through deception.
• Issues related to software or protocols not under Zerodha Broking Limited control.

Carefully review and understand the rules and scope of the bug bounty program. Each program has specific guidelines, eligibility criteria, and a defined scope of systems, applications, or services that are in-scope for testing. Focus your efforts on these areas to ensure your findings are eligible for rewards.

When reporting a vulnerability, commit to providing clear and comprehensive details to help the organization reproduce and validate your findings. Include step-by-step instructions, proof-of-concept code if applicable, and any other relevant information that can assist the organization's security team in understanding and verifying the issue.

Engage in professional communication with the organization's security team. Be responsive to any requests for clarification, additional information, or coordination during the vulnerability verification process. Maintain open and respectful communication throughout the entire process, understanding that both parties are working together to improve security.

Always adhere to responsible disclosure practices. When you discover a vulnerability, avoid exploiting it for malicious purposes or sharing it with unauthorized parties. Instead, immediately report the vulnerability to the program organizers following the reporting process outlined in the program guidelines. This allows the organization to address the issue before potential harm can occur.

Researchers participating in our programs are expected to adhere to specific Safe Harbor provisions. They are assured Legal Protection; by complying with all program terms, they're granted a legal safe harbor, ensuring they won't face lawsuits or legal actions for their reported findings. Participants also commit to Responsible Disclosure, providing ample time to address and rectify vulnerabilities and doesn't disclose any findings publically what so ever. Testing should be confined only to systems they have explicit authorization to assess. Furthermore, during the assessment, data access should be minimized, focusing only on what's necessary to validate a vulnerability, and retaining no user data beyond what is absolutely required.