How It Works Features Blog FAQ Download

Security and privacy

Arguium sees meetings, screens and conversations. That only works if the handling of that data is something you can actually inspect and control.

Bring your own key

Supply your own Gemini or OpenAI API key and requests go directly from your machine to your provider account, not through Arguium infrastructure. Keys are encrypted at rest on your device.

Local models

You can point Arguium at a local Ollama model for chat. Arguium doesn’t support screenshots with Ollama, and voice transcription stays on the device only with Apple Speech (a Mac with Apple silicon and macOS 26).

Local encrypted sessions

Conversation history is stored on your machine and encrypted at rest. Sessions are cleared on logout.

Hardened runtime

The desktop app runs with Node integration disabled, context isolation enabled and the renderer sandboxed — the standard hardening baseline for Electron applications. API keys, prompts, screenshots and personal data are never written to application logs.

Phone Mirror is end-to-end encrypted

Phone Mirror shows Arguium’s transcript and answers on your phone; it is not screen mirroring, and nothing of your computer’s screen is sent to the phone. What it sends is encrypted on your computer with AES-256-GCM and decrypted on the phone. The key exists only inside the QR code — in the part of the link after #, which browsers never send to a server — so Arguium’s relay forwards ciphertext it cannot read and stores only hashes. The QR is single-use and expires in 2 minutes, and a new pairing is view-only until you click Allow control on the computer. One honest limit: there is no forward secrecy. The key in the QR is the pairing’s key for its whole life (up to 30 days if you choose Remember this phone), so treat the QR like a password. This covers the phone link: to produce answers, Arguium still sends your transcript and screenshots to the AI provider you use, as it always has.

Download Arguium free

Frequently Asked Questions

Yes, with your own API key: requests go straight to your provider (voice transcription needs your own OpenAI key, or Apple Speech on a Mac).

Session history is stored locally and encrypted on your device.

Keys you supply are encrypted at rest on your machine and are never written to logs.