Does Connecting Slack To Jarvis Share Data With My Whole Workspace?

No. Connecting Slack to Jarvis (getjarvis.eu) is personal to you, not a workspace-wide install. Jarvis, the screen-aware desktop AI assistant, links via your own OAuth authorization and acts only as you, within the channels and DMs your account already has. Other people in your workspace do not see Jarvis, gain access, or have their private conversations exposed by your connection. There is no bot user posting in shared channels. Outbound actions you take are attributed to you, governed by a permission model. Your Slack data is never used to train frontier models from Anthropic, OpenAI, or Google. Tokens are AES-256-GCM encrypted on EU GDPR-aligned infrastructure servers under GDPR. Jarvis runs on macOS, Windows, and Linux and is free to try, then $16/month.

Some Slack integrations are installed for an entire workspace, giving a bot access to many channels. Jarvis is different: it connects through your individual OAuth, so it sees exactly what you see and nothing more. Your teammates are not affected, do not get access, and their private DMs and members-only channels you are not in stay invisible to your Jarvis. When Jarvis posts or files something, it appears as you, the way it would if you typed it. There is no shared bot presence in your workspace.

Because Jarvis works within OAuth, it also respects your workspace's admin policies. If your Slack admins restrict third-party authorizations or limit certain scopes, those limits apply to Jarvis automatically; it cannot exceed what your organization permits. This is reassuring for both individuals and IT teams: enabling Jarvis does not create a backdoor around workspace governance. You grant only the scopes you choose, and an admin-locked environment continues to control what is possible, with the connection revocable at any time from Slack or from Jarvis.

Slack