Skip to content
LimoVibesRequest a Quote
LimoVibes

Security and Vulnerability Disclosure Policy

Authorized reporting, safe-harbor boundaries, response and prohibited testing.

← All policies and disclosures

Version 1 Effective

Report a suspected security problem

Send a report to security@limovibes.com or use the security report form. This channel is for suspected vulnerabilities, unauthorized access, information exposure, or other platform-security concerns. For ordinary account or billing assistance, contact policy@limovibes.com.

Useful report details

Include the affected page or feature, when the issue occurred, what you expected, what you observed, and safe steps that let us understand the problem. Provide your contact details if you want a reply. Remove passwords, session tokens, verification codes, full payment information, and unrelated personal data from screenshots or logs.

If you unexpectedly encounter another person's information, stop accessing it. Do not download, copy, change, disclose, or seek additional records to demonstrate the issue. Describe the type of exposure and its location without sending the exposed information through ordinary email or the form.

Reporting is not permission for intrusive testing

This policy does not authorize bypassing access controls, accessing another account, extracting data, modifying records, social engineering, denial-of-service activity, malware, mass scanning, or tests that disrupt users or services. Do not test payment processors, hosting services, provider websites, or other third-party systems under this policy. Obtain specific written authorization before undertaking testing beyond normal permitted use.

Review and communication

Reports are reviewed to determine relevance, impact, and appropriate action. We may request clarification or coordinate with an affected service provider. Please avoid public disclosure of details that expose personal information or enable immediate harm while the report is being assessed. Do not use a report to demand payment or threaten users.

There is no public bug-bounty program or automatic reward, recognition, legal safe-harbor, or response-time guarantee under this policy. Nothing here requires a waiver of rights or changes obligations imposed by applicable law. Security controls reduce risk but cannot guarantee that every incident will be prevented.

About this version

Explains how to report suspected security problems using the monitored security channel, while prohibiting intrusive testing and avoiding bounty, safe-harbor or absolute-security promises.

Document history and reference

Content reference: 6712922821ea02c4af0fdf317a450f313e42ce3667994c9181a3d34821ff0214

Questions or need assistance? All policies and disclosures