VWO Logo
Request Demo

Responsible Disclosure Policy

Wingify takes the security of its systems seriously and values the security community. The responsible disclosure of security vulnerabilities helps Wingify in ensuring the security and privacy of its users.


Wingify requires all researchers to:

  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction of data during security testing;
  • Perform research only within the scope set out below;
  • Use the identified communication channels to report vulnerability information to us; and
  • Any information you receive or collect about Wingify, its Customers or any of their visitors, or employees or agents in connection with this policy (“Confidential Information”) must be kept confidential. You shall not use, disclose, publish, or distribute any such Confidential Information or the vulnerability details, without Wingify’s prior written authorization.

If you follow these guidelines when reporting an issue to Wingify, then Wingify commits to:

  • Not pursue or support any legal action related to your research;
  • Work with you to understand and resolve the issue quickly (including an initial confirmation of your report within 72 working hours of submission); and
  • Recognize your contribution on our Security Researcher Hall of Fame (currently under construction), if you are the first to report the issue and we make a code or configuration change based on the issue.


  • vwo.com
  • app.vwo.com

Out of scope

Any services hosted by third-party providers and services are excluded from the scope.

In the interest of the safety of Wingify’s users, staff, the Internet at large, and you as a security researcher, the following test types are excluded from the scope:

  • Denial of service
  • Spamming
  • Social engineering (including phishing) of VWO staff or contractors
  • Any physical attempts against VWO property or data centers
  • Content spoofing / text injection
  • Self-XSS [to be valid, cross-site scripting issues must be exploitable in reflected, stored or DOM-based types]
  • Logout and other instances of low-severity Cross-Site Request Forgery
  • Open redirects with low security impact (exceptions are those cases where the impact is higher such as stealing oauth tokens)
  • Missing http security headers
  • Missing cookie flags on non-sensitive cookies
  • Password and account recovery policies, such as reset link expiration or password complexity
  • Invalid or missing SPF (Sender Policy Framework) records (Incomplete or missing SPF/DKIM)
  • SSL/TLS best practices
  • Clickjacking/UI redressing with no practical security impact
  • Username / email enumeration via Login Page or Forgot Password Page error messages

Things Wingify does not want to receive

  • Personally identifiable information (PII)
  • Credit card holder data

How to report a security vulnerability?

If you believe you’ve found a security vulnerability in one of Wingify’s products or platforms, please send it to us by emailing security@wingify.com. Please include the following details with your report:

  • Description of the location and potential impact of the vulnerability;
  • A detailed description of the steps required to reproduce the vulnerability (POC scripts, screenshots, and compressed screen captures are all helpful to us); and
  • Your name/handle and a link for recognition in our Hall of Fame.

If you’d like to encrypt the information, please use our PGP key.

Hall of Fame

At Wingify, we use our Hall of Fame program to recognize people who have responsibly shared one or more security vulnerabilities in our products, enabling us to serve our customers better. Please refer to Security Hall of Fame for details.