&noscript=1""/>

Responsible Disclosure Policy

Last Update: December 2020

At Lark the security of our systems, and our users data, is a top priority. No matter how much effort we put into system security, there might still be vulnerabilities present. If you do discover a vulnerability, we want to know about it so we can take the correct steps to address it as quickly as possible. We’re asking for your help to protect our customers and our systems.

If you discover a vulnerability in the Lark mobile app, 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 email your findings to security@lark.com in a manner that safeguards the confidentiality of the report so that others do not gain access to the information (we suggest encrypting  your findings/email using Virtru or other encryption tool  to prevent this critical information from falling into the wrong hands,  Follow the guidelines below:

Dos:

  • Do provide sufficient information to reproduce the problem, so we will be able to 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.
  • Do report the vulnerability as quickly as is reasonably possible, to minimize the risk of hostile actors finding it and taking advantage of it.
  • Do provide sufficient information to reproduce the problem, so we will be able to resolve it. Usually, the IP address or the URL of the affected system and a description of the vulnerability will be sufficient. However, complex vulnerabilities may require further explanation.

Don’ts:

  • Don’t reveal the vulnerability or problem to others until it is resolved.
  • Don’t build your own backdoor in an information system with the intention of then using it to demonstrate the vulnerability, because doing so can cause additional damage and create unnecessary security risks.
  • Don’t utilise a vulnerability further than necessary to establish its existence.
  • Don’t copy, modify or delete data on the system. An alternative for doing so is making a directory listing of the system.
  • Don’t make changes to the system.
  • Don’t repeatedly gain access to the system or share access with others.
  • Don’t use brute force attacks, attacks on physical security, social engineering, distributed denial of service, spam or applications of third parties to gain access to the system.

The following areas are considered out of scope:

  • Vulnerabilities that require access to an already compromised account (unless access to an account exposes other accounts)
  • Policies as opposed to implementations – email verification, password length or reuse, etc.
  • Missing security headers or ‘best practices’ (except if you are able to demonstrate a vulnerability that makes use of their absence)
  • Vulnerabilities in our open source software (unless you have a proof of concept of how the specific vulnerability can be used on the Lark app)
  • Distributed Denial of Service attacks (DDoS)
  • Social engineering attacks
  • Third party applications we make use of, but do not control (e.g. a blog or newsletter hosted on an external service.)
  • Integrations and extensions created by third party developers using our APIs.

What we promise:

  • We will respond to your report within 5 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 in regard to the report,
  • We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission,
  • We will keep you informed of the progress towards resolving the problem,
  • In the public information concerning the problem reported, we will give your name as the discoverer of the problem (unless you desire otherwise), and
  • As a token of our gratitude for your assistance, we offer a reward for every report of a security problem that was not yet known to us. The amount of the reward will be determined based on the severity of the leak and the quality of the report. The minimum reward will be a $100 gift certificate.

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