EVE BOT is software you run, not a service you sign up for. This page describes what a deployment of it handles, so that whoever operates one can be clear with the people who use it. The project's maintainers do not receive any data from anyone's deployment: there is no telemetry, no analytics, and no phone-home in the code.
A deployment stores what its team does: the conversations with HQ and each Bot, the jobs and their results, files a Bot saves, the activity feed, and memory, which is what the operator and the Bots chose to remember about how work should be done. On Vercel this lives in the operator's own Blob store; standalone, it lives on disk on the operator's machine. It stays there until the operator deletes it.
Bots work inside web applications through a real browser on the team's computer, and read what appears on screen, including email and documents, in order to do the job they were given. That content is sent to the model provider the operator configured, such as Vercel AI Gateway or a local endpoint, under that provider's terms. Sign-ins to those applications are made by a person in the live browser; the software never asks for a password in chat, and the browser's saved sign-ins are part of the operator's backups.
Access to a deployment's console is protected by a token the operator sets, or by the operator's own Vercel login. Anyone with that token can read everything the deployment stores. Operators should treat it as a password and rotate it if it leaks.
Questions about a specific deployment go to its operator. Questions about the software go to https://github.com/Shaivpidadi/eve-bot/issues.