Laméco welcomes reports of security researchers and experts on possible vulnerabilities

If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. Help us to better protect our users by sending our security team a report containing information and detailed instructions on how to reproduce the problem.

Please do the following:

  • E-mail your findings to
  • 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 deleting or modifying other people's data, do not harm our company or our users with your findings
  • 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, and
  • 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.

What we promise:

  • We will respond to your report within 6 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 in our 'hall of fame / Recognition of Security Researchers' .

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.

The security impact will be categorised in:

  • Low: Vulnerabilities that would improve overall security if configured differently but cannot be used directly for malicious action,
  • High: when there is a vulnerability that opens up an exploit to limit the normal functioning of the application (think no rate limiting on login that could cause you to spam),
  • Critical: when, for example, data becomes available that can normally only be accessed via login or if (part of) content or something in that sense can be adjusted without having the correct authorization for this.

Standard tooling:
Vulnerabilities issues found with standard tooling (f.e. DMARC settings) are not rewarded.

Hall of fame:

  • Akash Patil
  • Meenu Kumari
  • Sayeed Shaik
  • Girish B O
  • Meenu Kumari
  • Max Raams