Security & Privacy

Docs › Support › Security & Privacy

Security & Privacy

How NOVA protects your code, your secrets and your control over your computer.

You approve the risky things

Deleting files, installing software, committing, pushing, deploying and opening secret files always ask, in every mode. See Permissions.

Secrets are masked

NOVA masks recognised passwords, keys, tokens and cookies in the sessions, logs and handoff notes it saves. Masking is a safety net, so don't paste secrets into your requests.

Your sign-in is stored securely

NOVA stores your sign-in in your operating system's secure credential store where one is available. On Windows, if it can't store your sign-in securely, it saves nothing and tells you.

What stays on your computer

  • your sessions, memory and settings
  • the project map
  • data files you analyse
  • handoff notes

Other people's code

A project you clone can't run commands through NOVA until you trust it. Skills you install from Git show their source and a checksum first.

Keep NOVA in one folder

\makeroot

NOVA won't create or edit files outside the current folder until you run \exitroot.

Join our Discord

Chat with our engineers and become part of the active NOVA developer community.

Join Discord

Need help?

Open an issue on GitHub or email support@bridgeye.com.

Get help
Bridgeye • Autonomous Software Engineering.