Security
How your data is protected, and where to report a weakness.
Updated November 20, 2026. A change to these pages is announced here first.
Report a Problem
Email security@neova.app with what you found and how to reproduce it. We reply within 3 business days.
Please
- Give us reasonable time to fix it before you make it public.
- Do not access, change or delete other people's data, and do not disrupt the service.
- Test only against your own account and your own crawls.
What We Promise
If you follow these rules in good faith, we will not take legal action against you, and we will credit you once the fix is out, if you want.
How Neova Protects Your Data
- On your computer, crawls stay on your computer; tokens and keys live in the system's own password store.
- Neova Online runs on a server in Nuremberg, Germany, reached only over HTTPS. Passwords are kept as scrypt hashes; device keys and API keys as SHA-256 fingerprints; each account's crawls in its own folder.
- Share links, Neova Go and the Companion are locked on your computer with AES-256-GCM before upload. The key stays in the part of the link after the #, which browsers never send to a server.
- The engine inside the app ships as native code. The only credential of Neova's inside it is the Google sign-in client for desktop apps, which Google treats as public; your own tokens and keys are never in the app.
Machine-readable: app.neova.app/.well-known/security.txt
Our team speaks English and French. Please write to us in one of those; an AI translator is fine.