Responsible Disclosure Policy

uConnect believes that the disclosure of vulnerabilities is essential to improving the quality of our products and services. uConnect values the insights of the security research community and welcomes disclosure and collaboration.

Through our responsible disclosure process, uConnect will work with security researchers and other vulnerability investigators to make our products and services more secure by providing a mechanism to privately report vulnerabilities with legitimacy and integrity. Responsible disclosure ensures that security infrastructure is tested and proven reliable. This process allows us to work collaboratively with the researchers to identify and mitigate vulnerabilities quickly in an ever-changing security environment.

The following is uConnect responsible disclosure policy:

  • uConnect will disclose known vulnerabilities and their fixes to its customers in a manner that protects the end-users of our products. Disclosures made by uConnect will include credit to the person who first identified the vulnerability unless they request otherwise.
  • uConnect is open to communication and working with security researchers who come to uConnect with a shared interest to improve security and coordinate the distribution of information, including both the vulnerability and the solution that addresses it.
  • uConnect does not have a bounty program nor a monetary award for the researcher, however, uConnect will provide credit and publicly acknowledge in a written advisory, the work of a security researcher who privately brings the company valid information about a vulnerability and then works with uConnect to coordinate the public announcement after a fix or patch has been developed and tested.
  • Security researchers are allowed to post a link to the uConnect advisory on their own websites as recognition for helping minimize risks and helping end-users protect themselves.

We ask the security researcher community to work with uConnect to coordinate the public disclosure of a vulnerability. Prematurely revealing a vulnerability publicly without first notifying uConnect could hurt end-users, exposing sensitive information and putting people and organizations in danger of malicious attacks.

To that end, uConnect strongly advocates a two-step process: first, private disclosure of a potential vulnerability to uConnect. Once the vulnerability is validated and resolved, uConnect coordinates the public disclosure, which includes the recognition of the security researcher’s discovery, confirming that credit is given to the right person(s).

We ask that researchers recognize that our actions to investigate, validate and remediate reported vulnerabilities vary based on complexity and severity. We will communicate expected timelines, changes and collaborate where possible.  Additionally, we request that researchers not utilize Denial of Service tools or compromise uConnect user infrastructure or personal; information while performing testing or evaluation.  If this kind of testing is necessary, we request they contact us, so that we may provide testable products in a non-production environment for such purposes where reasonably possible.

Like other leading companies, uConnect applies industry best practices for coordinated disclosure of vulnerabilities to protect the security ecosystem, ensuring that customers get the highest quality information, drive public discourse about ways to improve products, protocols, methodologies, standards, and solutions.

As part of its responsible disclosure program, uConnect is seeking relationships with security researchers who adhere to a coordinated, shared responsibility approach to publicly disclosing a vulnerability. uConnect invites security researchers and other vulnerability investigators to join us in this effort.

If you believe you have discovered a vulnerability, please email us at and include as much of the following:

Please include, if possible, the information below in your email report:

  • Any contact details (i.e., Signal, WhatsApp, or other communications account)
  • Company name
  • Preferred email contact
  • General description of the vulnerability
  • The product containing vulnerability 
  • Document instructions to reproduce the event
  • Sample code, proof of concept, or executable used to produce the event
  • Definition of how the vulnerability will impact a user
  • Affected product
  • System Details 
  • Technical description and steps to reproduce
  • PoC (link)
  • Other parties and products involved
  • Disclosure plans/dates/drivers
  • What was the purpose and scope of research being performed when found (context)?