Vulnerability disclosure policy

Brand promise

Keeping user information safe and secure is a top priority for us at GmbH, and we welcome the contribution of external security researchers.


If you believe you've found a security issue in any website, service, or software owned or operated by GmbH, we encourage you to notify us.

How to submit a report

To submit a vulnerability report to GmbH, please contact us at Your submission will be reviewed and validated by a member of our security team. Once verified and confirmed you might be eligible for our reward program and will be notified.

Safe harbor GmbH supports safe harbor for security researchers who:

  • Make a good faith effort to avoid privacy violations, destruction of data, and interruption or degradation of our services.
  • Only interact with accounts you own or with explicit permission of the account holder. If you do encounter Personally Identifiable Information (PII) contact us immediately, do not proceed with access, and immediately purge any local information.
  • Provide us with a reasonable amount of time to resolve vulnerabilities prior to any disclosure to the public or a third-party.

We will consider activities conducted consistent with this policy to constitute "authorized" conduct and will not pursue civil action or initiate a complaint to law enforcement. We will help to the extent we can if legal action is initiated by a third party against you.

Please submit a report to us before engaging in conduct that may be inconsistent with or unaddressed by this policy.

Definition of a vulnerablity GmbH considers a security vulnerability to be a weakness in one of our products or infrastructure that could allow an attacker to impact the confidentiality, integrity, or availability of the product or infrastructure.

  • Presence or absence of HTTP headers (X-Frame-Options, CSP, nosniff, etc.). These are considered security best practices and therefore we do not classify them as vulnerabilities.
  • Missing security-related attributes on non-sensitive cookies. We may set certain security-related attributes on cookies used on our applications. The absence of these headers on non-sensitive cookies is not considered a security vulnerability.
  • Exposed stack traces.  We do not consider stack traces by themselves to be a security issue. If you find that a stack trace details personally identifiable information or User-Generated Content, please submit a report detailing the issue.


  • Please provide detailed reports with reproducible steps and a clearly defined impact.
  • Submit one vulnerability per report.
  • Social engineering (e.g. phishing, vishing, smishing) is prohibited.