Coordinated vulnerability disclosure

At Return, we consider the security of our systems a top priority. However, no matter how much effort we put into system security, there can still be vulnerabilities present.

If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.

Please do the following:

  • Submit your findings to security@return.energy.
  • Do not take advantage of the vulnerability or problem you have discovered, for example, by downloading more data than necessary to demonstrate the vulnerability or by deleting or modifying other people's data.
  • Do not reveal the problem to others until it has been resolved.
  • Do not use attacks on physical security, social engineering, distributed denial of service, spam, or applications of third parties.
  • Do provide sufficient information to reproduce the problem so we can resolve it as quickly as possible. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient, but complex vulnerabilities may require further explanation.

What we promise:

  • We will respond to your report within five business days with our evaluation of the report and an expected resolution date.
  • If you have followed the instructions above, we will not take any legal action against you regarding the report.
  • We will not pass on your personal details to third parties without your permission.
  • We will keep you informed of the progress in resolving the problem.
  • In the public information concerning the reported problem, we will give your name as the discoverer of the issue (unless you prefer otherwise).

Issues you do not have to report:

  • SPF, DKIM, or DMARC issues.
  • Missing security headers (HSTS, CSP, X-Frame-Options, etc).
  • SSL/TLS issues that score above B on SSL Labs.
  • Self-XSS vulnerabilities.
  • Clickjacking on non-sensitive pages.
  • Brute force attacks on login forms.
  • Reports from automated vulnerability scanners.
  • Issues in third-party applications or dependencies that are already reported to the vendor.

We strive to resolve all problems as quickly as possible, and we would like to play an active role in the final publication on the issue after it is resolved.