All Collections
Security Bulletins
Responsible disclosure policy
Responsible disclosure policy

How we work with security researchers to identify vulnerabilities and protect our users' data

Bertel Torp avatar
Written by Bertel Torp
Updated over a week ago

Security is core to our values, and we value the input of security researchers acting in good faith to help us maintain a high standard for the security and privacy for our users.

This includes encouraging responsible vulnerability research and disclosure. This policy sets out our definition of good-faith in the context of finding and reporting vulnerabilities, as well as what you can expect from us in return.

  • Work with you to understand and validate your report, including a timely initial response to the submission.

  • Work to remediate discovered vulnerabilities in a timely manner.

  • Recognize your contribution to improving our security if you are the first to report a unique vulnerability, and your report triggers a code or configuration change. Scope Any service on our domains *, but not services that are hosted by third parties. Examples of 3rd party services may include, but are not limited to, Cloudflare, AWS and GCloud. If you have any questions about scope, please contact us via: [email protected]

When reporting vulnerabilities, please consider (1) attack scenario / exploitability, and (2) security impact of the bug.


The following issues are considered out of scope:

  • Attacks requiring MITM or physical access to a user’s device.

  • Previously known vulnerable libraries without a working Proof of Concept.

  • Missing best practices in SSL/TLS configuration (yep, we're also waiting for Azure to support TLS 1.3)

  • Any activity that could lead to the disruption of our service (DoS).

  • Content spoofing and text injection issues without showing an attack vector/without being able to modify HTML/CSS.

  • Rate limiting or bruteforce issues on non-authentication endpoints.

  • Missing best practices in Content Security Policy.

  • Missing HttpOnly or Secure flags on cookies that are not sensitive (e.g. missing flags on authentication cookies are in scope).

  • Vulnerabilities only affecting users of outdated or unpatched browsers (eg. only mainstream browsers less than 2 stable versions behind the latest released stable version in scope).

  • Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.


We do not offer money or swag as rewards, but we will give you a place in our Security Hall of Fame. Reports need to meet the following criteria to qualify:

  • Severity medium or above (severity is to be determined by Ulobby)

  • Our security team is able to reproduce and verify the issue

  • The issue is not previously known or already reported

How to contact us

Our official communication channel is via email to:

Safe Harbour

When conducting vulnerability research according to this policy, we consider this research conducted under this policy to be:

  • Authorized in view of any applicable anti-hacking laws, and we will not initiate or support legal action against you for accidental, good-faith violations of this policy.

  • Authorized in view of relevant anti-circumvention laws, and we will not bring a claim against you for circumvention of technology controls.

  • Exempt from restrictions in our Acceptable Usage Policy that would interfere with conducting security research, and we waive those restrictions on a limited basis.

  • Lawful, helpful to the overall security of the Internet, and conducted in good faith.

You are expected, as always, to comply with all applicable laws. If legal action is initiated by a third party against you and you have complied with this policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please submit a report through one of our official channels before going any further.

Hall of Fame

  • Shivam Khambe, Security Researcher

Did this answer your question?