Policy For: Twomile Heavy Industries, Inc. and affiliated platform “Review Star” Policy updated: November 13, 2025

⚠️ ATTENTION! WE HAVE ENDED OUR BUG BOUNTY PROGRAM. SEE “BUG BOUNTY” SECTION BELOW, FOR DETAILS. ⚠️

Introduction

Twomile appreciates and encourages the active participation of the cybersecurity research community in helping us secure our infrastructure and applications. Our full list of security research credits and appreciation located on the Security Credits page.

Twomile Heavy Industries, Inc. is committed to ensuring the security of our customers by protecting their information. This policy is intended to give security researchers clear guidelines for conducting vulnerability discovery activities and to convey our preferences in how to submit discovered vulnerabilities to us.

This policy describes what systems and types of research are covered under this policy, how to send us vulnerability reports, and how long we ask security researchers to wait before publicly disclosing vulnerabilities.

We encourage you to contact us to report potential vulnerabilities in our systems.

Authorization

If you make a good faith effort to comply with this policy during your security research, we will consider your research to be authorized we will work with you to understand and resolve the issue quickly, and Twomile Heavy Industries, Inc. will not recommend or pursue legal action related to your research. Should legal action be initiated by a third party against you for activities that were conducted in accordance with this policy, we will make this authorization known.

Guidelines

Under this policy, “research” means activities in which you:

  • Notify us as soon as possible after you discover a real or potential security issue.
  • Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems, and destruction or manipulation of data.
  • Only use exploits to the extent necessary to confirm a vulnerability’s presence. Do not use an exploit to compromise or exfiltrate data, establish persistent command line access, or use the exploit to pivot to other systems.
  • Provide us a reasonable amount of time to resolve the issue before you disclose it publicly.
  • Do not submit a high volume of low-quality reports.

Once you’ve established that a vulnerability exists or encounter any sensitive data (including personally identifiable information, financial information, or proprietary information or trade secrets of any party), you must stop your test, notify us immediately, and not disclose this data to anyone else.

Test methods

The following test methods are not authorized:

  • Network denial of service (DoS or DDoS) tests or other tests that impair access to or damage a system or data
  • Physical testing (e.g. office access, open doors, tailgating), social engineering (e.g. phishing, vishing), or any other non-technical vulnerability testing

Scope

This policy applies to the following systems and services:

  • *.twomile.com
  • *.reviewstar.io

Any service not expressly listed above, such as any connected services, are excluded from scope and are not authorized for testing. Additionally, vulnerabilities found in systems from our vendors fall outside of this policy’s scope and should be reported directly to the vendor according to their disclosure policy (if any). If you aren’t sure whether a system is in scope or not, contact us before starting your research.

Though we develop and maintain other internet-accessible systems or services, we ask that active research and testing only be conducted on the systems and services covered by the scope of this document. If there is a particular system not in scope that you think merits testing, please contact us to discuss it first. We will increase the scope of this policy over time.

Reporting a vulnerability

⚠️ ATTENTION! WE HAVE ENDED OUR BUG BOUNTY PROGRAM. SEE “BUG BOUNTY” SECTION BELOW, FOR DETAILS. ⚠️

Information submitted under this policy will be used for defensive purposes only — to mitigate or remediate vulnerabilities. If your findings include newly discovered vulnerabilities that affect all users of a product or service and not solely Twomile Heavy Industries, Inc., we may share your report with the Cybersecurity and Infrastructure Security Agency, where it will be handled under their coordinated vulnerability disclosure process. We will not share your name or contact information without express permission.

We accept vulnerability reports via security@twomile.com, or LinkedIn. Reports may be submitted anonymously. If you share contact information, we will acknowledge receipt of your report within 3 business days.

We do not currently support reporting via PGP-encrypted emails or keybase.io. If you need to securely submit sensitive information please initiate contact via security@twomile.com and we will arrange a secure information drop.

NOTE: By submitting a vulnerability, you acknowledge that you have no expectation of payment and that you expressly waive any future pay claims against Twomile Heavy Industries, Inc. related to your submission.

What we would like to see from you

In order to help us triage and prioritize submissions, we recommend that your reports:

  • Describe the location the vulnerability was discovered and the potential impact of exploitation.
  • Offer a detailed description of the steps needed to reproduce the vulnerability (proof of concept scripts or screenshots are helpful).
  • Be written in English, if possible.

What you can expect from us

When you choose to share your contact information with us, we commit to coordinating with you as openly and as quickly as possible.

  • Within 3 business days, we will acknowledge that your report has been received.
  • To the best of our ability, we will confirm the existence of the vulnerability to you and be as transparent as possible about what steps we are taking during the remediation process, including on issues or challenges that may delay resolution.
  • We will maintain an open dialogue to discuss issues.

Bug Bounty

⚠️ ATTENTION! WE HAVE ENDED OUR BUG BOUNTY PROGRAM. DO NOT SUBMIT SECURITY REPORTS IF YOU ARE SEEKING PAYMENT. ⚠️

We offered an experimental bug bounty program for a few months during 2024 as a trial with three goals: A) engage with the infosec community, B) assess the effort and cost required to support a bug bounty program, and C) improve the security of our systems. We are a small company with a small staff, funded 100% by customers. We do not have venture capital money or Big Company money to devote to experimental programs.

While the bug bounty program provided us with a number of useful reports and overall improvements to the security posture of our infrastructure, the effort required to process and verify new security reports was substantial and took us away from other important tasks in running the business. While some reports were very useful, we often received duplicates from multiple sources, especially for low-risk findings that we chose to live with (e.g., “your HTML doesn’t make use of X-FRAME-OPTIONS so someone might iframe you”). Regardless of quality, many security reports take a great deal of time to investigate and assess.

There’s a lot of tooling to automate vulnerability scanning and reporting now, so the effort for a researcher to submit an lengthy report can be quite small. AI has supercharged this problem. Security research remains an honored and valuable endeavour, but the red team industry is drowning in individuals and companies who have automated the process to maximize reporting and bounty income (frequently, with little or no interest in benefitting the report recipients). As a result, small organizations with bug bounty programs must endure a flood of low quality or useless reports, in order to identify and make use of the good ones. Additionally, we found bounty payment to countries outside the US to be very challenging, particularly when paying a bounty to a freelance individual.

It is a far better use of our limited time and money to occasionally hire a security audit in a formal engagement. The process is significantly more efficient, the signal to noise ratio is better, and while it tends to require a larger financial commitment, the time savings and clarity are worth the extra cost.

Questions

Questions regarding this policy may be sent via our contact page. We also invite you to contact us with suggestions for improving this policy.

Acknowledgements

See our credits and appreciation page.