Security & Responsible Disclosure
We take the security of our products and our customers' data seriously. If you believe you have found a vulnerability in fanpino.com or any Fanpino product, we want to hear from you.
How to report
- Email [email protected] with the subject line starting with "Security:".
- Include the affected URL or product, steps to reproduce, and the impact you observed.
- Give us a reasonable amount of time to fix the issue before disclosing it publicly.
Please don't
- Access, change, or delete data that doesn't belong to you.
- Run denial-of-service, spam, or social engineering attacks against us or our customers.
- Use automated scanners that generate heavy traffic.
How we protect your data
- Every release is checked against all 10 categories of the OWASP Top 10.
- All traffic is HTTPS-only, with HSTS set for 1 year (31,536,000 seconds).
- Passwords are stored only as bcrypt hashes, and login sessions expire after 24 hours.
- Uploads are capped at 50 MB, and 7 browser-executable file types (HTML, SVG, JS and others) are refused.
What we promise
- We will reply to every good-faith report and keep you updated until it is resolved.
- We will not take legal action against research done in good faith under this policy.
- We will credit you publicly on this page, with your permission.
We don't run a paid bug bounty program. We do recognise every valid report here and are happy to provide a written letter of appreciation.
Hall of Fame
Thank you to these researchers for responsibly reporting issues that made our products safer.
- Piyush Nana Lavange2026-11
Account enumeration through the registration endpoint (accepted as low risk)
- Avadhut Kulkarni2026-11
Customer accounts could be used without confirming the email address
- Khushal Bhoyar2026-11
HTML markup accepted in the contact form name field
- T.Jaswanth2026-11
HTML injection through the name field into registration welcome emails
- Ankit Admane2026-11
Weak password policy at customer registration, password change and reset
- Dhruv2026-09
Stored XSS through PDF attachments uploaded to customer support tickets
Last updated: