Report an Issue

1. What You Can Report

We welcome reports on any of the following. All reports — regardless of topic — can be sent to report@kancoding.com.

• Diversity, equity & inclusion (DEI) — concerns about discrimination, bias, unequal treatment, or exclusionary behaviour involving our team, hiring practices, or services.
• Social impact concerns — observations about how our work, partnerships, or conduct may negatively affect individuals, communities, or society at large.
• Environmental issues — concerns about unsustainable practices, greenwashing claims, or decisions that conflict with our stated environmental commitments.
• Security vulnerabilities — bugs, exploits, or weaknesses in our website or services.
• Privacy concerns — suspected data leaks, unauthorised access, or mishandling of personal information.
• Content issues — inaccurate, misleading, or inappropriate content on our platform.
• Technical bugs — broken functionality, errors, or unexpected behaviour that affects users.
• Policy violations — conduct by a Kancoding team member that may breach our workplace or ethical standards.
• Abuse or fraud — any suspected misuse of Kancoding's services or brand.
• Any other concern — if something does not fit the above but feels important to raise, we still want to hear from you.

2. How to Submit a Report

Send your report by email to report@kancoding.com. There is no online form — email ensures a direct, traceable channel between you and our team.

If your report involves a security vulnerability, please use a descriptive subject line such as "Security Report: [brief description]". For general issues use "Issue Report: [brief description]".

3. What to Include

To help us investigate efficiently, include as much of the following as possible:

• A clear description of the issue and where it occurs (page URL, feature, etc.).
• Steps to reproduce the problem (for technical or security issues).
• Screenshots, screen recordings, or logs if available.
• The date and time you first noticed the issue.
• Your contact email in case we need to follow up.

You may submit anonymously — simply leave out your contact details. Anonymous reports are still reviewed, though we may not be able to update you on the outcome.

4. Our Response Process

5. Responsible Disclosure

If you have discovered a security vulnerability, we ask that you follow responsible disclosure practices:

• Report the issue to us privately before making it public.
• Give us reasonable time to investigate and patch the issue before disclosing it publicly.
• Do not exploit the vulnerability to access, modify, or delete data beyond what is necessary to demonstrate the issue.
• Do not perform actions that could harm our users or disrupt our services.

We appreciate researchers who follow responsible disclosure and will acknowledge their contribution where appropriate.

6. Pledge an Issue

You can also use this channel to pledge a concern — meaning you want to formally record a worry or observation about our practices, services, or team conduct, even if it has not yet caused direct harm.

Pledges are treated with the same seriousness as direct reports. They are logged, reviewed, and factored into our continuous improvement process.