Security and vulnerability reporting
Effective date: November 2026. Nepgram is a young company, and we know software has flaws. If you find a security problem on nepgram.com, in our apps or in our API, please tell us. We read every report, fix what is real, and thank the people who help us.
How to report
- Email security@nepgram.com. You can write in English or Nepali.
- Tell us what you found and where (the page, app screen or API call), the steps that show it again, what someone could do with it, and the account or booking reference you tested with.
- Do not send passwords, card numbers or other people's personal details. Tell us what kind of information was exposed, not the information itself.
- A problem with your own booking or payment is faster through support.
No paid bug bounty program
Nepgram does not run a paid bug bounty program, and we do not pay per report. We are a small team, and we would rather say this before you spend your time than after.
What we do offer:
- Our thanks, and a clear answer about what happened with your report.
- Public credit once the fix is live, if you want it.
- For a report that prevented real harm, we may choose to send a token of thanks. That is our decision alone, it is sized to a small company, and it is not a published rate or a promise for future reports.
Rules for testing
- Use only your own account and your own bookings.
- Do not view, change, download or delete another person's information. If you reach it by accident, stop there and tell us.
- No denial of service: nothing that slows or interrupts Nepgram for other people, such as request floods or load tests.
- No social engineering, phishing or pressure on our staff, our partners or travelers.
- No automated scanning of the live site or API. Scanners set off our abuse protection, and the address they come from is blocked.
- Stop as soon as you have confirmed the flaw, and report it. Do not go further to see how far it reaches.
- A booking, ticket, refund or Nepgram Points obtained through a flaw is cancelled. It is not a reward, and using it is outside this policy.
- Test Nepgram only. Do not test our partners' own systems, or the banks and payment providers we connect to.
What is out of scope
We do not act on these without proof of a real effect:
- Missing security headers or cookie flags.
- SPF, DKIM or DMARC observations.
- Self-XSS, where the person affected has to paste the code themselves.
- Clickjacking on a page with no sensitive action.
- Rate-limit observations with no demonstrated effect.
- Software version banners.
- Scanner output with no proof of effect.
What to expect from us
- We acknowledge your report within 3 business days.
- We tell you whether we could reproduce it, and when it is fixed.
- We ask you to keep the details private until the fix is live. If you want to write about it afterward, we agree on a publication date with you.
Good faith
If you follow this policy and act in good faith, we will not take legal action against you for your research. This covers Nepgram's own systems only: we cannot give the same assurance on behalf of our partners or payment providers.