1. How to report
Email admin@blinx.lk with the subject "Security report". Please include:
- the affected address (URL) or system;
- the type of issue and its likely impact;
- clear steps to reproduce it, with a proof of concept if you have one; and
- how we can contact you.
Please do not report issues through public channels, social media or our public contact forms.
2. Scope
In scope: blinx.lk and its subdomains, including the client portal and the public forms.
Out of scope:
- denial-of-service or load testing, and spam;
- social engineering, phishing or physical attacks on our staff or offices;
- systems run by third parties (for example Google, Meta, Cloudflare or Supabase), which have their own programmes;
- automated scanner output without a demonstrated, exploitable impact; and
- missing best-practice headers or settings that have no practical security impact.
3. Rules for testing
- Only test accounts and data that belong to you. Stop as soon as you reach anyone else's data, and do not keep, share or change it.
- Do not degrade the service, delete data or use the issue beyond what is needed to show it.
- Give us reasonable time to fix the issue before you tell anyone else (we ask for up to 90 days).
- Follow the law.
4. What we promise
- We acknowledge your report within 3 working days and keep you updated.
- We will not take legal action against you for research that follows this policy in good faith.
- With your permission, we will thank you publicly once the issue is fixed.
5. How we protect the site
Highlights of our security practice: HTTPS everywhere; least-privilege database access rules; multi-factor authentication, passkeys and audit logs for staff; bot protection and rate limits on public forms; private, signed-link storage for sensitive files; and regular security reviews of our code and dependencies. See our Privacy Policy for how we handle personal data.
