Arguium sees meetings, screens and conversations. That only works if the handling of that data is something you can actually inspect and control.
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.
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).
Conversation history is stored on your machine and encrypted at rest. Sessions are cleared on logout.
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 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.
In Settings → MCP Servers you can connect Notion, Linear, Atlassian (Jira and Confluence), ClickUp, Attio, Sentry or Google Calendar so answers can use your docs, tickets, tasks, customer records, error reports and calendar. Arguium only reads, with one exception: in Google Calendar it can add an event, only after you select Create. The tools it may call are a fixed list built into the app, checked again on every call. Your sign-in stays on your computer, encrypted by the operating system, for the Arguium account you are signed in to, and is never sent to Arguium’s servers. To answer, the search goes from your computer to the service, and what Arguium reads goes to your AI provider with the rest of your question (through Arguium’s proxy when you use credits). Saved answers can keep what they quoted or summarized from it, in your local history. Disconnecting, or signing out of Arguium, deletes the sign-in from your computer and asks the service to revoke it, where it supports that (for Google Calendar, remove Arguium in your Google Account → Security → Third-party apps & services to end its access on every computer). With Premium you can also add your own MCP servers, which we don’t run or check: only tools the server marks read-only can be turned on (the server’s own claim), and, beyond a request for its tool list each time you ask, each one receives only what Arguium takes from the message or voice line you asked about, never your chat history or screenshots. Details in the Privacy Policy.
Notion, Linear, Atlassian, Jira, Confluence, ClickUp, Attio, Sentry and Google Calendar are trademarks of their owners. Arguium is not affiliated with them.
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.