YC
YUCANSOFT.
Security

Vulnerability Disclosure Policy

Last updated: 25 September 2026 · YUCANSOFT Technologies & Consulting Ltd

We take the security of our websites, systems and services seriously, and we welcome responsible security research. This page explains how to report a vulnerability to us, what we ask researchers to do, and the safe-harbour protections that apply to good-faith research.

01 How to Report a Security Vulnerability

If you believe you have discovered a security vulnerability affecting a YUCANSOFT website, system or service, please report it to security@yucansoft.co.uk.

Please do not publicly disclose the vulnerability before giving us a reasonable opportunity to investigate and address it.

When reporting a vulnerability, please provide as much relevant information as possible, including:

Please do not include unnecessary personal data, credentials, secrets or information belonging to other individuals in your report.

02 What We Ask Security Researchers to Do

When conducting security research against YUCANSOFT systems, we ask researchers to:

03 Testing Activities That Are Not Permitted

The following activities are outside the scope of our responsible disclosure process and should not be performed:

If you unintentionally gain access to sensitive information during otherwise responsible testing, please stop testing the relevant functionality and notify us promptly.

04 Scope

This policy applies primarily to publicly accessible YUCANSOFT websites, applications and services operated by YUCANSOFT.

Unless explicitly stated otherwise, third-party services, infrastructure and applications are not considered to be within the scope of this policy.

If you are uncertain whether a particular system or testing activity is within scope, please contact us at security@yucansoft.co.uk before proceeding.

05 Vulnerabilities We Are Interested In

We are particularly interested in reports of vulnerabilities that could have a meaningful security impact, including:

Reports concerning purely theoretical issues or vulnerabilities without a realistic security impact may require additional information before we can investigate them.

06 Issues Generally Considered Low Priority

The following may not normally be treated as security vulnerabilities unless they demonstrate a meaningful security impact:

This does not mean that such reports are ignored. We may review them according to their circumstances and potential impact.

07 Responsible Disclosure

We ask researchers to give YUCANSOFT a reasonable opportunity to investigate and remediate reported vulnerabilities before publicly disclosing technical details.

We recognise that coordinated disclosure timelines may vary depending on the complexity and severity of a vulnerability.

If you believe a vulnerability requires a particular disclosure timeline, please explain your proposed timeline in your report and we will consider it.

We ask researchers not to use a vulnerability to obtain publicity, commercial advantage or access to information unrelated to demonstrating the security issue.

08 Our Response

We will make reasonable efforts to:

Response and remediation times may vary depending on the complexity, severity and affected system. Submission of a report does not guarantee a particular response time, remediation outcome or public acknowledgement.

09 Safe Harbour

YUCANSOFT considers security research conducted in good faith and in accordance with this policy to be authorised activity for the purposes of this vulnerability disclosure process.

Where a researcher makes a good-faith effort to comply with this policy, YUCANSOFT will not seek to initiate or support legal action against the researcher solely for security research activities that fall within the scope of this policy.

This safe-harbour statement applies only to systems and activities within the scope of this policy and does not authorise conduct that violates applicable law, involves malicious intent, causes unnecessary harm, or falls outside the testing boundaries described above.

If you are uncertain whether proposed testing is covered by this policy, please contact us before proceeding.

10 No Compensation

YUCANSOFT does not currently operate a bug bounty or paid vulnerability rewards programme.

Unless explicitly agreed in writing in advance, submitting a vulnerability report does not create an entitlement to financial compensation, employment, contractual engagement or any other reward.

We nevertheless appreciate responsible security research and the time invested by security researchers in helping us improve the security of our services.

11 Third-Party Vulnerabilities

If your research identifies a vulnerability in a third-party product or service used by YUCANSOFT, please report the vulnerability to the relevant vendor where appropriate.

You may also notify YUCANSOFT if the vulnerability creates a security risk to a YUCANSOFT service or environment.

Please do not test or attempt to exploit third-party systems solely through their relationship with YUCANSOFT.

12 Confidentiality and Personal Data

Please minimise the amount of personal or confidential information included in vulnerability reports.

If your investigation accidentally exposes personal data or confidential information belonging to YUCANSOFT, its customers, employees or other individuals, do not copy, retain, distribute or publicly disclose that information.

Notify us promptly and securely so that we can determine the appropriate response.

13 Changes to This Policy

YUCANSOFT may update this Vulnerability Disclosure Policy from time to time. The current version will be published on this page. Researchers should review the current policy before conducting security testing.

14 Contact

YUCANSOFT Technologies & Consulting Ltd

Security Team

Email: security@yucansoft.co.uk

Please use a clear subject such as:

Security Vulnerability Report – [brief description]

For urgent security matters, please include URGENT SECURITY ISSUE in the subject line.

Report a vulnerability →