Security Policy

As part of Crext Investments' commitment to keeping your account and information safe and secure, we appreciate your comments if you suspect a potential security issue with any of our services. Please contact us right away at


Crext Investments believes that working with skilled security researchers across the globe is crucial in identifying weaknesses in any technology. If you have discovered a security vulnerability in our systems or in one of our product/services, we appreciate your help in disclosing it to us in a responsible manner. We'll work with you to make sure that we understand the scope of the issue, and that we fully address your concerns. We consider vulnerability disclosures our highest priority and we will try to address any issue as quickly as possible.

Disclosure Policy

While researching, we'd like to ask you to refrain from:
  • Denial of service
  • Spamming
  • Social engineering (including phishing) of Crext Investments staff or contractors, or users
  • Any physical attempts against Crext Investments property or data centres
  • Any interaction or unauthorised access to data
  • Missing best practices (we require evidence of a security vulnerability)
  • Use of a known-vulnerable library (without evidence of exploitability)


  • Let us know as soon as possible upon discovery of a potential security issue, and we'll make every effort to quickly resolve the issue.
  • Provide us a reasonable amount of time to resolve the issue before any disclosure to the public or a third-party.
  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our service. Only interact with accounts you own.

Out of Scope

  • Reports from automated tools or scans
  • Missing cookie flags on non-sensitive cookies
  • Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner).
  • Exposure of non-sensitive data on mobile devices
  • Missing security headers which do not lead directly to a vulnerability, including CSP

Third-party bugs

If issues reported to our program affect a third-party library, external project, or another vendor, we reserve the right to forward details of the issue to that party without further discussion with the researcher. We will do our best to coordinate and communicate with researchers through this process, and we will not share your name with third parties without your approval.

Reporting a vulnerability

We accept and discuss vulnerability reports via email at Please encrypt your findings using our PGP key to prevent this critical information from falling into the wrong hands.

Reports should include

  • A Description of the location and potential impact of the vulnerability
  • A detailed description of the steps required to reproduce the vulnerability. Proof of concept (POC) scripts, screenshots, and screen captures are all helpful. Please use extreme care to properly label and protect any exploit code.
  • Any technical information and related materials we would need to reproduce the issue
  • Your name/handle for recognition in our Hall of Fame (optional)
  • Please keep your vulnerability reports current by sending us any new information as it becomes available.

Safe Harbor

Any activities conducted in a manner consistent with this policy will be considered authorized conduct and we will not initiate legal action against you. If legal action is initiated by a third party against you in connection with activities conducted under this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.