Zivame’s responsible disclosure policy
Zivame takes the security of our systems seriously, and it is our constant endeavor to make our website a safe place for our customers to browse. However, in the rare case when some security researcher or member of the general public identifies a vulnerability in our systems, and responsibly shares the details of it with us, we will appreciate their contribution, and work closely with them to address such issues with urgency. We would be glad to also publicly acknowledge their contribution.
How to report an issue?
If you happen to have identified a vulnerability on any of our properties, we request you to follow the steps outlined below:
- Please contact us immediately by sending an email to firstname.lastname@example.org with the necessary details to recreate the vulnerability scenario. This may include screenshots, videos or simple text instructions.
- Please share with us your contact details (email, phone number), so that our security team can reach out to you for further inputs to quickly identify and close the problem.
- Please do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data. This is necessary for us to consider your disclosure as a responsible one. While we appreciate your inputs, we may take legal recourse if the identified vulnerabilities are exploited for unlawful gains or getting access to restricted customer or system information or impairing our systems.
- Please do not reveal the problem to others until it has been resolved. Please give us reasonable time to appropriately fix the problem before making such information public. Our team will work with you to estimate and commit to such a time frame.
We do not have a bounty/cash reward program for such disclosures, but we express our gratitude for your contribution in different ways. For genuine ethical disclosures, we would be glad to publicly acknowledge your contribution in this section on our website. Of course, this will be done if you want a public acknowledgement.
- Shaik Nasreen Fathima (https://www.linkedin.com/in/shaik-nasreen-fathima-727b38197/)
- Mayank Gandhi (https://www.linkedin.com/in/mayank-gandhi-0163ba216/)
- Nikhil Rane (https://www.linkedin.com/in/nikhil-rane-31733a217/ )
- Rohan Badekan (https://www.linkedin.com/in/rohan-badekan )
- RAAJESH.G - Infoziant Security ( https://linkedin.com/in/raajesh-258a93173 )
- PRATIK SURESH KARAN ( https://www.linkedin.com/in/pratik-karan-310b06214/ )
- Suyash Sharma ( https://www.linkedin.com/in/suyash-sharma-394852202/ )
- Pawan Rawat ( https://twitter.com/PawanRa20262178 )
- Upasana Bohra ( https://www.linkedin.com/in/upasana-bohra-8767b9156 )
- Ritu raj choudhary ( https://www.linkedin.com/in/ritu-raj-choudhary-44202620b )
- Goutham A S ( https://www.linkedin.com/in/goutham-a-s-279992164/ )
- Ajay Sharma (https://twitter.com/security_donut)
- Ritu Sardiwal (https://twitter.com/RituSardiwal)
- Mohd Shahbaz Alam (https://www.linkedin.com/in/shahbaz07)
- Harshit Raj Singh (https://www.linkedin.com/in/h4r5h1t-hrs)
- Prasanth R (https://mobile.twitter.com/try_to_hack)
- Raghav Khandelwal (https://www.linkedin.com/in/raghav-khandelwal-902b88203/)
- J.Chandra prakash (https://www.instagram.com/chandra_prakash_j/)
- Gourab Sadhukhan (https://www.linkedin.com/in/gourab-sadhukhan-71158216a)
- Jatin Dhankhar (https://twitter.com/jatindhankhar_)
- Samasree Das (https://www.linkedin.com/in/samasree-das-769651191/)
- Arpita Dey (https://www.linkedin.com/in/arpita-dey-a794551b9/)
- Anjan Neema (https://www.linkedin.com/in/anjanneema/)
- Devansh Gandhi (https://www.linkedin.com/in/gandhidevansh/ )