We welcome good-faith security reports that help protect our users. This page explains what is in scope, how to report, what to expect from us, and the rules for testing. We do not operate a bug bounty, and we do not pay for unsolicited reports.
Last updated: 26 August 2025
Public websites and web applications owned and operated by ClickAlgo Limited.
Only targets that can be accessed without using credentials that belong to someone else and without causing disruption.
Third-party services include hosting providers, payment processors, email services, analytics, and content delivery networks.
Denial-of-service attacks, high-volume automated scanning, resource exhaustion, or any action that degrades service availability.
Reports without a working proof of concept, or those consisting only of automated scanner output.
Best-practice findings without clear exploitability, such as missing security headers on non-sensitive pages, version banners, or clickjacking, where no sensitive action occurs.
Username or email enumeration, lack of rate limiting or account lockouts, and recommendations related to CAPTCHA implementation.
Cosmetic HTML or CSS injection in non-sensitive areas (including emails) without a demonstrable exploit chain.
Social engineering, phishing, physical security testing, or non-technical fraud.
Respect privacy. Do not access, modify, or copy data that does not belong to you.
Do not disrupt services or degrade performance.
Act in good faith and within the boundaries of this policy.
Send an email to security@clickalgo.com with:
A clear description of the issue.
The exact affected URL or system.
Step-by-step instructions to reproduce the vulnerability.
A minimal proof of concept that demonstrates the impact.
We will acknowledge valid reports sent to security@clickalgo.com.
Out-of-scope reports and generic scanner results will not receive a reply.
We do not pay for reports or run a bug bounty.