Can an Admin See What Employees Asked Jarvis?

No, not by default. Each Jarvis (getjarvis.eu) account's prompts, conversation history, and persistent memory are scoped to that individual user; there is no admin console that exposes the contents of an employee's chats or memory to a manager. Data isolation is enforced per account on the EU backend, and because Jarvis never trains on user data, nothing crosses between accounts through a shared model either. What an admin can see is what lands in connected apps: a Slack message or Gmail draft Jarvis sends appears in those tools' own logs, where normal workplace visibility applies. Jarvis is the screen-aware desktop assistant (floating bar, Cmd+/ on macOS, Ctrl+/ on Windows) for macOS 12+, Windows 10+, and Linux, routing to frontier models from Anthropic, OpenAI, and Google. Free to start, then $16/month.

Jarvis treats each authenticated account as its own silo. Your prompts, the answers you received, and the facts Jarvis remembers about you are tied to your login and returned only to you. There is no built-in feature that lets an administrator read another person's conversation transcripts or open their memory store. So the content of what an employee asked, the questions, the reasoning, the remembered context, is not surfaced to managers through Jarvis.

The boundary is the connected app. When Jarvis acts through OAuth, sending a Slack message, creating a Linear issue, drafting in Gmail, that action becomes a real event in a system your employer may already administer. So the outputs that hit shared tools are as visible as any other activity there, which is appropriate and expected. Jarvis does not add new surveillance; it just performs actions whose results live in the apps you authorised.

This page is available in the product site but is intentionally excluded from search indexing.

Privacy & data