1. Reporting a vulnerability
We welcome good-faith reports of security vulnerabilities in FleetProxy. Email support@fleetproxy.io with “Security vulnerability report” in the subject. Include the affected URL or endpoint, a description of the issue, minimal reproduction steps, potential impact and your contact details. Identify any test accounts you own without sending their passwords.
Redact authentication tokens, proxy credentials, payment details and customer information from screenshots or request samples. Do not email confidential third-party records. If sensitive evidence is necessary, ask us to agree a suitable transfer method first.
2. Systems and boundaries
This policy concerns security issues in FleetProxy’s own applications. It does not grant permission to test supplier infrastructure, third-party integrations, payment services, proxy exit devices, rented IPs or websites reached through our proxies. A redirect, shared IP address or FleetProxy branding does not extend testing permission to another system.
Contact support if you are unsure whether a system or proposed test is covered. Authorization to test a customer’s own system does not extend to FleetProxy or another provider.
3. Responsible testing
- Use only your own accounts and test data. Test account-isolation issues only between accounts you control. Do not attempt to take over another customer’s account.
- Use the minimum non-destructive activity needed to explain the problem. Do not degrade service, perform denial-of-service or load testing, scan at volume, spam, brute-force credentials, install malware, establish persistence or move into other systems.
- Do not use phishing, social engineering or physical access against staff, customers or suppliers.
- Do not create real purchases, deposits, charges, withdrawals, refunds, rentals, extensions or paid IP changes as a proof of concept. Do not change balances, earned commissions or other financial records. Report suspected financial logic flaws without completing the financial action and contact us about a safe way to reproduce them.
- Do not use stolen credentials or secrets found through a vulnerability to explore further. Do not modify or delete another person’s data.
- Stop once you have enough evidence to explain the flaw. If someone else’s data appears unexpectedly, stop immediately, do not explore or copy it further, and report privately with redacted evidence.
4. Our commitments to researchers
We will acknowledge your report and tell you whether we can reproduce it. We will keep you updated while we work on a fix and tell you when it is deployed. We are happy to credit you publicly once the issue is fixed, if you want that.
We will not pursue legal action against you for research carried out in good faith and within this policy, and we will not ask your internet provider or employer to act against you for it. These protections apply despite a general restriction in our Terms of Service or Acceptable Use Policy that would otherwise prohibit the same compliant research.
This commitment covers FleetProxy’s own rights. It cannot authorize activity on third-party systems, bind another organization or authority, or prevent cooperation required by applicable law. Theft, fraud, disruption and activity outside this policy remain prohibited.
5. Coordinated disclosure and rewards
Please report privately and give us a reasonable opportunity to investigate and address the issue before publishing exploit details. Coordinate disclosure with us; this is not an indefinite secrecy requirement.
We do not run a fixed bounty program with published amounts. Reports identifying a real and meaningful issue may be rewarded at our discretion, case by case, based on severity and report quality. No payment amount is promised in advance.
6. Assessing a report
Describe the actual security impact. A missing header, a software version or scanner output alone does not establish a vulnerability. Authentication, authorization and customer-isolation flaws affecting FleetProxy can be security issues.
Ordinary proxy availability, target-site rejection or disagreement about a checker result belongs with customer support. Abuse committed through a proxy should be reported under our Acceptable Use Policy. Findings in third-party services should be reported to their provider.

