Is My Jarvis Data Encrypted in Transit and at Rest?

Yes, on both fronts. In transit, traffic between the Jarvis (getjarvis.eu) desktop app and its EU backend, and onward to the model providers, is protected with TLS, so prompts and screenshots are encrypted as they travel. At rest, sensitive credentials are encrypted with AES-256-GCM: your OAuth tokens for Gmail, Slack, Notion, and other connectors are stored sealed rather than in plaintext on the GDPR-aligned infrastructure. Combined with GDPR and EU AI Act alignment and a strict no-training policy, this keeps your data protected in motion and in storage. Jarvis is the screen-aware desktop assistant (floating bar, Cmd+/ on macOS, Ctrl+/ on Windows) for macOS 12+, Windows 10+, and Linux, routing tasks to frontier models from Anthropic, OpenAI, and Google. Pricing is free to start, then $16/month for Pro.

Every leg of a Jarvis request rides over TLS, the same transport encryption that secures banking and email. When you submit a prompt, it is encrypted from the desktop app to the backend, and the minimal context forwarded to Anthropic, OpenAI, or Google for inference is likewise encrypted in flight. This prevents interception on the network: someone sniffing your Wi-Fi cannot read your prompt or a screenshot in transit between the app and the model.

For data that is stored, the highest-value secret is your connector credentials, and those are encrypted at rest with AES-256-GCM, a strong authenticated cipher. The token is unreadable on disk and is decrypted only momentarily server-side to make an authorised API call. Because the key is managed separately from the data, a copy of the stored ciphertext alone is useless. This protects your Gmail, Slack, and Notion access even in a worst-case storage exposure scenario.

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

Privacy & data