Vulnerability Disclosure Program

This Vulnerability Disclosure Program was last updated on August, 2019.

Committed to Coordination

If you have information related to security vulnerabilities of Float Mobility products or services, we want to hear from you. Please submit a report in accordance with the guidelines below. We value the positive impact of your work and thank you in advance for your contribution.


Float Mobility agrees to not pursue civil claims against researchers related to the disclosures submitted through this website who:

Out of Scope

  1. Reports from automated tools or scans
  2. Issues without clearly identified security impact (such as clickjacking on a static website), missing security headers, or descriptive error messages
  3. Missing best practices, information disclosures, use of a known-vulnerable libraries or descriptive / verbose / unique error pages (without substantive information indicating exploitability)
  4. Speculative reports about theoretical damage without concrete evidence or some substantive information indicating exploitability
  5. Forms missing CSRF tokens without evidence of the actual CSRF vulnerability
  6. Self-exploitation (e.g., cookie reuse)
  7. Reports of insecure SSL / TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner such as SSL Labs)
  8. Our policies on presence/absence of SPF / DMARC records
  9. Password complexity requirements, account/e-mail enumeration, or any report that discusses how you can learn whether a given username or email address has a Float Mobility-related account
  10. Missing security-related HTTP headers which do not lead directly to a vulnerability
  11. Self Cross-site Scripting vulnerabilities without evidence on how the vulnerability can be used to attack another user
  12. Social engineering of Float Mobility employees or contractors
  13. Any physical attempt against Float Mobility property or data centers
  14. Presence of autocomplete attribute on web forms
  15. Missing secure cookie flags on non-sensitive cookies
  16. Denial of Service Attacks
  17. Banner identification issues (e.g., identifying what web server version is used)
  18. Open ports which do not lead directly to a vulnerability
  19. Open redirect vulnerabilities
  20. Publicly accessible login panels
  21. Clickjacking
  22. Content spoofing / text injection

Safe Harbor

Float Mobility agrees not to pursue civil action against researchers who comply with Float Mobility's policies regarding this vulnerability disclosure program. We consider activities conducted consistent with the Float Mobility Policy Terms to constitute "authorized" conduct under the Computer Fraud and Abuse Act. Also, if you comply with the Float Mobility Policy Terms, we will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.


If legal action is initiated by a third party against you and you have complied with the Float Mobility Policy Terms, we will, if asked, state that your actions were conducted in compliance with this policy.


By contacting us, you consent to Your Information being transferred to and stored in the United States and acknowledge that you have read and accepted the Terms, Privacy Policy and Disclosure Guidelines presented to you when you created your account.

You may contact us as follows: