Sun – Fri: 10:00 AM – 5:00 PM

Last reviewed: 20 November 2026

IP Sewa holds client filings, identity documents and payment records, so we take security reports seriously. If you believe you have found a vulnerability, we want to hear about it. This page explains how to report it, what you may test, and how we respond. It is published by Lawyers Nepal Platform Pvt. Ltd., which operates IP Sewa.

How to report

Email info@ipsewa.com with the subject “Security report”. Please include the affected URL or feature, clear steps to reproduce the issue, what an attacker could achieve, and any proof-of-concept output. Send findings privately — never in a public comment, review or social media post.

We aim to acknowledge a report within a few working days, keep you informed while we investigate, and tell you when it is fixed.

In scope

  • ipsewa.com — the public site, trademark search and the free tools.
  • The client portal (/portal) — using only an account you register yourself.

Out of scope

  • The admin panel login: no password guessing, credential stuffing or brute force.
  • Real payments and payment gateways (Fonepay, Khalti, card checkout). Do not make, alter or replay a payment.
  • Other people's accounts or data. If you reach any, stop at once and report it — do not view further, keep, download or change it.
  • Denial of service, load or volume testing, and high-rate automated scanning.
  • Social engineering, phishing, or any attempt on our staff, clients or offices.
  • Third-party services we use (Cloudflare, Google, email and payment providers) and our other websites.
  • Reports without a demonstrated security impact, such as missing security headers, email SPF/DMARC settings, clickjacking on pages with no sensitive action, software version banners, or automated scanner output that has not been verified.

Rules for good-faith research

  • Test only within the scope above, and at a gentle rate that does not affect other users.
  • Use only your own test account and data.
  • Do not use a finding to go further than needed to show it exists.
  • Give us reasonable time to fix the issue — up to 90 days — before any public disclosure, and agree the disclosure with us.

Safe harbour

We will not take legal action against research that follows this policy in good faith, and we will not ask a law-enforcement agency to act against it. If you are unsure whether something is in scope, ask us first at the address above.

Rewards

We do not run a fixed-price bug bounty. For the first report of a valid, previously unknown and in-scope vulnerability that we can reproduce, we offer a reward decided after triage according to its severity and impact — higher-impact findings receive higher rewards. With your permission we are also glad to credit you publicly. Reports outside this policy, duplicates and issues already known to us are not rewarded.

security.txt

Our machine-readable contact file is published at /.well-known/security.txt.