NOVA by Bridgeye
Security

Found a security problem? Tell us.

How to report a vulnerability in NOVA, what we promise in return, and how to test without harming anyone.

Last updated 20 November 2026 · Effective 20 November 2026

In short

  • Email ciso@bridgeye.com with what you found and how to reproduce it.
  • We reply within 3 working days and keep you updated until it is fixed.
  • If you follow this policy, we will not take legal action against you for your research.
  • Please give us 90 days to fix it before you publish anything.

1.How to report

Email ciso@bridgeye.com. Please include:

  • What the problem is and which product or address it affects (NOVA, NOVA Web, NOVA CLI, the NOVA API, NOVA MCP, or this website).
  • Steps to reproduce it, and any proof-of-concept code or screenshots.
  • What an attacker could do with it, as far as you know.
  • How you would like to be credited, if at all.

Report in English. One report per problem helps us fix each one faster. If you think the problem is being exploited right now, say so in the subject line.

2.What we promise

  • To confirm we received your report within 3 working days.
  • To tell you within 10 working days whether we can reproduce it and how serious we think it is.
  • To keep you informed while we fix it, and to tell you when it is fixed.
  • To credit you publicly when it is fixed, if you want us to.

We do not run a paid bug bounty at the moment. We may choose to thank reporters of serious problems, but we do not promise a reward.

3.Safe harbour

If you act in good faith and follow this policy, we will consider your research authorised, we will not take legal action against you or report you to the authorities for it, and if someone else does, we will make it known that you acted within this policy.

This does not cover actions that break the law in ways this policy cannot authorise, and it cannot bind anyone other than Bridgeye Private Limited, such as our hosting or AI providers.

4.Testing rules

Please:

  • Test only with accounts and projects that you own, or that you have the owner's permission to use.
  • Stop as soon as you reach anyone else's data. Do not view, copy, change or delete more than you need to show the problem, and tell us what you accessed.
  • Do not run denial-of-service tests, flood our servers, or send spam.
  • Do not use social engineering, phishing or physical attacks against our staff, offices or customers.
  • Do not try to escape a build sandbox beyond showing that it is possible, and do not use it to reach other customers.
  • Keep the problem confidential until we have fixed it, or until 90 days have passed since your report, whichever is sooner. If we need longer, we will explain why and agree a date with you.

5.What is in scope

In scopeOut of scope
runnova.ai and its NOVA, NOVA Web, NOVA API and NOVA MCP services; the NOVA CLI; build sandboxes and the publishing systemSites and apps our customers build and publish (report those to the site's owner, or to us as abuse); third-party services we use, such as Google, GitHub or Razorpay
Ways to reach another customer's data, take over an account, run code outside a sandbox, or bypass payment or plan limitsMissing security headers or cookie flags with no demonstrated impact, self-XSS, clickjacking on pages with no sensitive actions, results of automated scanners without a working example

6.More

How we protect your data is described in our Privacy Policy. Using NOVA is subject to our Terms of Service. This policy is also listed in our security.txt file at runnova.ai/.well-known/security.txt.