Vulnerability Disclosure Policy


Fleet Complete is committed to ensuring the security of its customers by protecting their sensitive information in accordance with applicable law. 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 under this policy, how to send us vulnerability reports.


We encourage you to contact us to report potential vulnerabilities in Our Systems (as defined in the “Scope” section below).


If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized, we will work with you to understand and resolve the issue quickly, and Fleet Complete will not recommend or pursue civil legal action related to your research.


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 a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Do not submit a high volume of low-quality reports (e.g., submitting vulnerabilities that we cannot reproduce or accept and submissions with inadequate information).
  • Agree not to disclose your findings to anyone else.


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.

Test methods

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.
  • Exploiting identified vulnerabilities in a manner that risks the confidentiality, integrity, and/or availability of any resources not explicitly owned by you during testing processes.
  • Using your findings or pursue vulnerabilities discovered to phish, spam, social engineer, or otherwise defraud anyone while testing to gain more access.


This policy applies to the following systems and services available here:

  • https://*
  • https://*
  • https://*


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 our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any).

(collectively “Our Systems“)


If you aren’t sure whether a system is in scope or not, contact us at


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 may increase the scope of this policy over time.

Reporting a vulnerability

Information submitted under this policy will be used for defensive purposes only – to mitigate or remediate vulnerabilities.  Unless required by applicable law, we will not share your name or contact information without express permission.


We accept vulnerability reports at Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within five (5) business days.


By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against Fleet Complete related to your submission.


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 five (5) business days, we will acknowledge that your report has been received.
  • We will attempt to 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 We also invite you to contact

With Fleet Complete, you’ll experience your real-time fleet data transformed into actionable insights.

With this knowledge, you can make informed decisions about not only the efficiency of your fleet, but its safety, compliance, and sustainability.