HEETCH is committed to ensuring the security and privacy of all passenger and drivers by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.
This policy describes what systems and types of research are covered, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.
We encourage you to contact us to report potential vulnerabilities in our systems or application.
Heetch commit not to prosecute parties who submit vulnerability reports following the this program if the declarant(s):
- Do not use automated vulnerability discovery tools (ex: scanners)
- Perform security research without harming Heetch or its customers, employees or service providers
- Do not use, disclose or modify any of the data obtained as part of this research
- Do not carry out any action that affects the proper functioning of the services
- Do not perform a denial of service attack
- Under this policy, “research” means activities in which you:
- Notify us as soon as possible after you discover a real or potential security issue.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
- Only use exploits to the extent necessary to confirm vulnerabilities presence. Do not use an exploit to compromise or exfiltrate data, establish persistence or use the exploit to pivot to other systems.
- Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.
The following test methods are not authorized:
- Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
- Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing, whether it is on Heetch customers (passengers), drivers or employees.
- Automated scans
This policy applies to the following systems and services:
- Source code on Github public repos
- IOS Applications
- Android applications
Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from any vendor that Heetch uses services and/or tools fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact us before starting your research.
Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.
Reporting a vulnerability
We accept vulnerability reports via email@example.com. Reports may be submitted anonymously. For more information about response time, please read "What you can expect from us".
For Sensitive reports, you can send us encrypted messages using our PGP Key below :
-----BEGIN PGP PUBLIC KEY BLOCK-----mDMEY0mAhxYJKwYBBAHaRw8BAQdAwmytnMZv86x0w7jWAyl2XGZO6Fw1sabLYcvzwUKRc8e0Kk
-----END PGP PUBLIC KEY BLOCK-----
Bounty program / Rewards
We do not conduct bounty programs.
By default we do not rewards for vulnerability report, however if you request it and if the vulnerability is confirmed, we can publicly commit about your disclosure on our Hall of Fame.
Please note that we can consider exceptional rewards in case of confirmed critical unknown vulnerabilities.
What we would like to see from you
In order to help us triage and prioritize submissions, we recommend that your reports:
- Describe the location the vulnerability was discovered and the potential impact of exploitation.
- Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
- Be in English, if possible.
What you can expect from us
When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.
- Within 3 business days, we will acknowledge that your report has been received.
- To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
- We will maintain an open dialogue to discuss issues.
Questions regarding this policy may be sent to firstname.lastname@example.org. We also invite you to contact us with suggestions for improving this policy.