Vulnerability Disclosure Policy

Introduction

Neocles is committed to ensuring the security of our users 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, 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 Neocles will not recommend or pursue legal action related to your research.

Should legal action be initiated by a third party against you for activities 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), 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:

• All domains under neocles.io (including subdomains), unless specifically excluded.

Any service not expressly listed above, such as connected third-party services, is excluded from scope and not authorized for testing. Vulnerabilities found in vendor systems fall outside of this policy and should be reported directly to the vendor under their disclosure policy (if any).

If you are unsure whether a system is in scope, please contact us at info@neocles.io before starting your research.

Reporting a vulnerability

We accept vulnerability reports via email at info@neocles.io. Reports may be submitted anonymously.

To help us investigate, please include:

• A description of the vulnerability, its location, and potential impact.

• Steps required to reproduce the vulnerability (proof-of-concept, scripts, or screenshots are helpful).

• Your contact details (optional, if you wish to receive updates).

We will use information submitted under this policy for defensive purposes only – to mitigate or remediate vulnerabilities.

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 in English, if possible.

What you can expect from us

If you share your contact details, we commit to:

• Acknowledging receipt of your report within 3 business days.

• Confirming the existence of the vulnerability, where possible, and keeping you informed about remediation progress.

• Maintaining an open dialogue throughout the process.

Questions

Questions regarding this policy may be sent to info@neocles.io. We also welcome suggestions for improving this policy.

Document change history

Version: 1.0
Date: October 1st 2025
Description: First issuance.