Bug Bounty Program


Keeping user information safe and secure is a top priority and a core company value for us at Left of the Dot Media Inc (Left) and RightMesh AG (RightMesh). We welcome the contribution of external security researchers and look forward to rewarding them for their invaluable input aiding in the security of all users.


Left and RightMesh provide rewards to vulnerability reporters at our discretion. Reward amounts may vary depending upon the severity of the vulnerability reported and the quality of the report. Keep in mind that this is not a contest or competition. There are usual minimum rewards for critical vulnerabilities affecting the core Left and RightMesh applications, websites and servers.

Vunerability Types

  • Remote Code Execution on servers
  • Significant Authentication Bypass
  • Cross Site Request Forgery on critical actions
  • Cross site scripting on left.io, rightmesh.io, developer.rightmesh.io or related sites under the Left or RightMesh brands working on all browsers

We reserve the right to determine the reward amount for a vulnerability or even whether a reward should be granted. We typically reward lower amounts for vulnerabilities that require significant user interaction. We also may pay higher rewards for clever or severe vulnerabilities.

Applications in Scope

For now, the left.io and rightmesh.io websites and associated subdomains are eligible for the bounty program. We may still reward anything with significant impact across our entire security posture, so we encourage you to report such bugs via this program.

Eligibility and Responsible Disclosure

To promote the discovery and reporting of vulnerabilities and increase user safety, we ask that you:

  • Share the security issue with us in detail;
  • Please be respectful of our existing applications. Spamming forms through automated vulnerability scanners will not result in any bounty or award since those are explicitly out of scope;
  • Give us a reasonable time to respond to the issue before making any information about it public;
  • Do not access or modify our data or our users’ data without explicit permission of the owner. Only interact with your own accounts or test accounts for security research purposes;
  • Contact us immediately if you do inadvertently encounter user data. Do not view, alter, save, store, transfer, or otherwise access the data, and immediately purge any local information upon reporting the vulnerability to us;
  • Act in good faith to avoid privacy violations, destruction of data, and interruption or degradation of our services (including denial of service); and
  • Otherwise comply with all applicable laws.

We only reward the first reporter of a vulnerability. Public disclosure of the vulnerability prior to resolution may cancel a pending reward. We reserve the right to disqualify individuals from the program for disrespectful or disruptive behavior.

We will not negotiate in response to duress or threats (e.g., we will not negotiate the payout amount under threat of withholding the vulnerability, threat of releasing the vulnerability or any exposed data to the public, or attacking or threatening to attack our sites, users, employees, or other people or infrastructure associated with our companies or brands).

Out-of-Scope Vulnerabilities

The following issues are outside the scope of our rewards program:

  • Our policies on presence/absence of SPF/DMARC records;
  • Password, email and account policies, such as email id verification, reset link expiration, password complexity;
  • Lack of CSRF tokens (unless there is evidence of actual, sensitive user action not protected by a token);
  • Login/logout CSRF;
  • Attacks requiring physical access to a user's device;
  • Missing security headers which do not lead directly to a demonstrable vulnerability;
  • Missing best practices (we require evidence of a security vulnerability);
  • We will accept reports of XSS on other rightmesh.io, left.io and associated domains and subdomains but will not reward for them;
  • Host header injections unless you can show how they can lead to stealing data;
  • Use of a known-vulnerable library (without evidence of exploitability);
  • Reports from automated tools or scans;
  • Reports of spam (i.e., any report involving ability to send emails without rate limits);
  • Attacks that require attacker app to have the permission to overlay on top of our app (e.g., tapjacking);
  • Vulnerabilities affecting users of outdated browsers or platforms;
  • Social engineering of RightMesh or Left of the Dot Media Inc employees or contractors;
  • Any physical attempts against our property or data centers;
  • Presence of autocomplete attribute on web forms;
  • Missing cookie flags on non-sensitive cookies;
  • Reports of insecure SSL/TLS ciphers (unless you have a working proof of concept, and not just a report from a scanner);
  • Any report that discusses how you can learn whether a given username, email address has an account;
  • Any access to data where the targeted user needs to be operating a rooted mobile device;
  • Content spoofing vulnerabilities (where you can only inject text or an image into a page) are out of scope. We will accept and resolve a spoofing vulnerability where attacker can inject image or rich text (HTML), but it is not eligible for a bounty. Pure text injection is out of scope;
  • Ability to share links without verifying email;
  • Absence of rate limiting, unless related to authentication;
  • Reflected File Download vulnerabilities or any vulnerabilities that let you start a download to the user's computer are out of scope;
  • IP/Port Scanning via RightMesh or Left of the Dot Media Inc services unless you are able to hit private IPs or internal servers;
  • Hyperlink injection or any link injection in emails we send;
  • Phishing risk via unicode/punycode or RTLO issues.

Here are our best practices on how to submit security reports.

Consequences of Complying with This Policy

We will not pursue civil action or initiate a complaint to law enforcement for accidental, good faith violations of this policy. We consider activities conducted consistent with this policy to constitute “authorized” conduct under the Computer Fraud and Abuse Act. To the extent your activities are inconsistent with certain restrictions in our Acceptable Use Policy, we waive those restrictions for the limited purpose of permitting security research under this policy. We will not bring a DMCA claim against you for circumventing the technological measures we have used to protect the applications in scope.

If legal action is initiated by a third party against you and you have complied with our bug bounty policy, we will take steps to make it known that your actions were conducted in compliance with this policy.

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

The Fine Print

You are responsible for paying any taxes associated with rewards. We may modify the terms of this program or terminate this program at any time. We won’t apply any changes we make to these program terms retroactively. Reports from individuals who we are prohibited by law from paying are ineligible for rewards. RightMesh, Left of the Dot Media Inc and related company employees and their family members are not eligible for bounties.

In order to encourage the adoption of bug bounty programs and promote uniform security best practices across the industry, RightMesh and Left of the Dot Media Inc reserves no rights in this bug bounty policy and so you are free to copy and modify it for your own purposes. This bug bounty policy was originally copied and modified from the fine example provided free by Dropbox.

Partner with us

Contact us about partnership opportunities for off-grid connectivity solutions.

Become A Partner