*.QuickPing.org
QuickPing.org
Quickping Android Application
QuickPing Apis

Vulnerabilities in our user applications: Especially those vulnerabilities that lead to privilege escalation.
Any unauthorized access to our VPN servers: Any unauthorized access to our VPN servers is a concern.
Vulnerabilities that expose our customers' data to unauthorized access: This includes scenarios that jeopardize the security of our customers' data.
Vulnerabilities that weaken, compromise, or otherwise bypass our VPN communications, putting the traffic of those using our VPN products at risk.
Additionally, any publicly accessible hosts owned or managed by QuickPing not listed above may be considered on a case-by-case basis within the scope of research.
All QuickPing assets are eligible for consideration. However, some testing methodologies are exempt. Specifically, tests that degrade service quality, such as DoS attacks or spam, will not be considered for inclusion.

Adhering to rules: This includes compliance with this policy and any other agreements. In case of any inconsistency between this policy and any other terms, the terms of this policy take precedence.
Report discovered vulnerabilities promptly: Report any vulnerability as soon as it is discovered.
Avoid violating the privacy of others, disrupting our systems, deleting data, and/or harming user experience: Refrain from actions that compromise individuals' privacy or disrupt systems.
Utilize official channels to discuss vulnerability information with us: Use valid and official channels for communicating about vulnerabilities.
Maintain confidentiality of details of any discovered vulnerability until they are resolved, according to the disclosure policy: Keep the details of any vulnerability confidential until it is resolved.
Conduct tests only on systems within the research scope and respect systems and activities that are out of scope: Test only on systems within your research scope.
If a vulnerability provides improper access to data:
Obtain the minimum necessary data to demonstrate the concept of your test.
If you encounter user data during testing, such as Personally Identifiable Information (PII), credit card data, or proprietary information, stop the test immediately and report it.
Interact only with your testing accounts or with explicit permission from the account owner: Interact only with accounts that you own or with explicit permission from the account owner.
Also, keep in mind that the bug you report must be exploitable.
Avoid coercion: Do not resort to coercion under any circumstances.