Privacy Policy
Last updated: November 16, 2026
At Arguium, we take your privacy seriously. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our desktop application.
1. Information We Collect
Account Information
When you create an account, we collect:
- Email address (via Google OAuth)
- Display name
- Profile picture (if provided by Google)
Usage Data
We record how you use Arguium, linked to your account, to run and improve the service:
- For some requests: when it happened, the model, its size in tokens, its cost and how long it took
- How many requests you make each day
- Your credit use
- Which features you use (chat, voice, screenshots and insights) and roughly how long you use them
- When you sign in and when you were last active, and your app version
This does not include the content of your messages, recordings or screenshots.
Technical Data
Our servers receive your IP address with each request, and the approximate location it implies. We use them to connect you and to limit abuse. They appear in server logs, which we keep for 7 days, and our abuse limits hold your IP address briefly, for a few hours at most. Older request records can also hold it until they are deleted (see Data Retention).
Data You Provide
When using Arguium, you may provide:
- Text messages sent to AI providers
- Screenshots for analysis
- Voice recordings for transcription
- Content from services you connect in Settings → MCP Servers (Notion, Linear, Atlassian for Jira and Confluence, ClickUp, Attio, Sentry and Google Calendar): when an answer needs it, Arguium reads the pages, issues, documents, tasks, customer records, error reports and calendar events your account there can open, to write that answer (see Connected Services and Google Calendar below)
- Feedback you send from the app, and messages you send to contact@arguium.com
Our Website
arguium.com uses Cloudflare Web Analytics to count visits. It uses no cookies or local storage and does not fingerprint visitors. It records the page visited, the referring site, the browser, operating system and device type, the country and page-load timings, and it does not log query strings.
2. How We Use Your Information
We use the information we collect to:
- Provide and maintain the Arguium service
- Process your AI requests through our proxy service
- Track usage for billing and quota enforcement
- Improve and optimize our application
- Understand how Arguium is used: how many people use it, which features they use, for how long, whether they run out of credits and whether they come back
- Communicate with you about service updates
- Reply by email to feedback you send from the app (at your account's email address) and to messages you send us
- Email you about your account or subscription, when we need to
Understanding Usage
We use usage data on the basis of our legitimate interest in running, securing and improving Arguium. You can object at any time by contacting us. We review account and usage records and server logs with the help of an AI assistant (Claude, by Anthropic), which summarises them for us. These can include your name and email address.
Support Messages
We read your feedback and support messages with the help of an AI assistant (Claude, by Anthropic), which summarises them and drafts replies. A person reads and approves every reply before it is sent.
3. Data Storage and Security
Local Storage
Your conversation history and screenshots are stored locally on your device using OS-level encryption. We do not have access to this locally stored data.
Cloud Storage
The following data is stored in our secure cloud infrastructure:
- Account information
- Usage statistics and credit balances
- Subscription status
AI Provider Data
When you use our service with app-provided API keys, your prompts and content are sent through our proxy to AI providers (Google Gemini, OpenAI). When you use your own API keys (BYOK mode), data goes directly to your chosen provider.
Connected Services (MCP Servers)
You can connect Notion, Linear, Atlassian (Jira and Confluence), ClickUp, Attio or Sentry in Settings → MCP Servers so answers can use your docs, tickets, tasks, customer records and error reports. Arguium only reads from these services: it never creates, changes or deletes anything there. Google Calendar, which can also create an event when you confirm it, has its own section below.
- Your sign-in: connecting opens the service's own sign-in page in your browser. The sign-in it issues is stored on your device, encrypted by your operating system, for the Arguium account you are signed in to. It is never sent to Arguium's servers.
- Lookups: when a typed chat answer needs it, or when you ask for an answer to a voice line (Look up, the Answer This shortcut, Tap to answer, or Answer now on Phone Mirror), Arguium sends a search from your device to that service and reads what it returns. The AI writes the search: for a voice line, from that line and the lines before it, which may be what another person said. With a local Ollama model, a voice line’s search is that line’s own words. With "Look up my workspaces when I ask" on (the default), a line your microphone hears that names or asks about a connected service can also start a lookup. Your microphone can pick up other people through your speakers, so use headphones on calls, or turn that setting off in Settings → MCP Servers.
- What is read goes to your AI provider: to write the answer, what Arguium reads is sent to the AI provider you use, like the rest of your question: through our proxy when you use Arguium credits, or directly to the provider when you use your own API key; with a local Ollama model, to that model.
- With Web search on: with Gemini or OpenAI, one Chat answer can read a connected service and search the web. The AI then writes its web searches knowing what it read, so words from your pages, issues or records can be in a search Google or OpenAI runs for your answer: on your own account with your own Gemini or OpenAI API key, or on Arguium’s account on Arguium’s credits. Turn off Web search in Settings → Personalization to keep them apart.
- Other people’s details and technical data: a customer database such as Attio holds details about other people (names, email addresses, companies, notes about them), and Sentry’s error reports hold technical data, such as stack traces, that can contain passwords or keys. When an answer reads them, they go to your AI provider like anything else Arguium reads. A connected service may process a search with its own AI features, under its own terms. Attio’s note search finds notes by meaning, with AI that Attio runs. Sentry can pass the words of an issue search to its own AI, so in that search Arguium keeps only filters, such as “is:unresolved”, and removes other words; text inside a filter, such as message:“…”, is sent as written.
- Saved answers: an answer saved in your session history can contain information quoted or summarized from a connected service, with the titles of the pages and issues it read, and the Memory index on your device indexes that saved text. Disconnecting a service does not remove them. If you use Phone Mirror, the phone shows which services and pages an answer read.
- Disconnecting: Disconnect deletes the sign-in from your device and asks the service to revoke it, where the service supports that. ClickUp doesn’t: to disconnect it fully, also remove “ClickUp MCP Service” in ClickUp → Settings → ClickUp API, which also disconnects other apps that use it. Signing out of Arguium, or switching to another Arguium account, does the same for every connected service.
- Logs: the app's logs on your device record which service and lookup were used, how long it took and whether it worked, never what was searched for or read.
Google Calendar
You can connect Google Calendar in Settings → MCP Servers, so answers can say what is on your calendar and, when you confirm it, add an event to it.
- What Arguium asks Google for: to see and create events on your calendars (
calendar.events), to see the list of your calendars (calendar.calendarlist.readonly), to see when you are free or busy (calendar.freebusy), and an identifier for your Google account (openid), which keeps each Google account’s connection apart. - Your sign-in: connecting opens Google’s own sign-in page in your browser. The sign-in Google issues is stored on your device, encrypted by your operating system, for the Arguium account you are signed in to. It is never sent to Arguium’s servers. Arguium talks to Google Calendar directly from your device.
- What it reads: when a typed chat answer or a voice line you ask about needs it, or when a line your microphone hears names or asks about your calendar (as described above for connected services, including “Look up my workspaces when I ask”), Arguium asks Google for the events in the time window the answer needs, with any search words the AI chose. Of each event, the answer gets its title, time, time zone, location, organizer, guests’ email addresses and replies, whether it repeats, whether it is tentative or cancelled, Google’s identifiers for it and its calendar, and the start of its description, with the links and formatting Arguium recognizes taken out. It can also get your calendars’ names, time zones and your access to them, and when you are busy. Google’s video-call fields and attachments are left out; a description or location that mentions a call, such as a meeting ID or dial-in number, keeps its words, without links. An invitation from someone else lands on your calendar, so what it reads can include other people’s details and text they wrote.
- Where it goes: what Arguium reads from your calendar is sent to your AI provider to write the answer, like anything else a lookup reads: through our proxy when you use Arguium credits, or directly to the provider when you use your own API key; with a local Ollama model, to that model. Our proxy does not log it. It keeps a copy of each AI response, which can quote your calendar or hold a proposed event, for up to 24 hours, only so a retried request gets the same reply. Like other lookups, what it reads stays in the conversation, so later answers in that chat or voice session, other connected services’ lookups and, with Web search on, web searches can use it (the AI may put words from your events into those searches), and Phone Mirror shows the answer and which services it read (see the points above on Web search and Saved answers: answers saved in your session history and Memory can contain your events, and disconnecting does not remove them).
- Creating events: Arguium never creates, changes or deletes an event on its own. When you ask it to add an event, in Chat or with the Answer This shortcut or Tap to answer on your computer, it shows a card with the event’s title and time, and its calendar, guests, repeats, location and description, shown in full or one click away (Show). Nothing is created until you click Create on that card, and you can edit or cancel it first. Arguium asks Google to email guests only if you turn on “Email guests” on the card. Creating events works with Arguium’s credits on the models that passed our tests, not with your own API key, your ChatGPT plan or Ollama. Phone Mirror shows that an event is waiting on your computer, but cannot create it. Arguium does not change or delete existing events.
- Records of events it creates: so it doesn’t create an event again on its own when Google’s answer is lost, Arguium keeps a record of each event you confirm (its details and whether Google confirmed it) on your device, encrypted, for the Arguium account you are signed in to. A settled record is removed the next time Arguium records an event, once it is 7 days old. One Google hasn’t confirmed is kept until Arguium can check it with Google or you settle it on the card, and disconnecting keeps it, so it can be checked when you reconnect. Signing out of Arguium, or switching to another Arguium account, deletes the records.
- Disconnecting: Disconnect deletes the sign-in from your device, and signing out of Arguium, or switching to another Arguium account, does the same. Arguium does not revoke its access at Google, because one revocation would also disconnect your other computers. To remove Arguium’s access everywhere, remove Arguium at myaccount.google.com/connections.
- Logs: the app’s logs on your device record which Calendar action was used, how long it took and whether it worked, never your events or what was searched for.
- Google’s Limited Use requirements: Arguium’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Arguium uses your calendar data only to answer you and to create the events you confirm. It does not sell it, use it for advertising, or use it to develop, improve or train AI models. No person at Arguium reads it, unless you ask us to (for example, by sending it in a support message), for security or to investigate abuse, or where the law requires it. It goes only where this section says: to the AI provider that writes your answer and the uses of the conversation described above. With your own API key, your provider handles it under the terms of your account with them, which for some plans (such as Gemini’s free tier) let the provider use it to improve its services.
Custom Servers (Premium)
With Premium, you can also add up to 5 MCP servers of your own in Settings → MCP Servers → Custom servers, by their https:// address. We don’t run or check these servers: whoever runs one receives what Arguium sends it, under their own terms.
- What is sent to a custom server: each time you type a chat message, or ask for an answer to a voice line (Look up, Tap to answer or Answer this), while one of its tools is on, Arguium connects to the server with your sign-in and reads its list of tools, so the server can tell when you ask. A separate AI request that sees only that message or line and the tools you turned on then decides whether to use one of them, and with what words; that request goes to your AI provider like any other. Beyond the connection itself (which names the app as Arguium), the server receives only those words, taken from your message or line: none of your chat history, screenshots, persona or profile, or what other services returned. A browser sign-in also registers Arguium with the server, by name. Arguium connects to a custom server from your device, so the server also sees your IP address.
- Your sign-in: you sign in on the server’s sign-in page in your browser, or paste an access token. Either is stored on your device, encrypted by your operating system, and never sent to Arguium’s servers. A pasted token is sent only to that server’s address; a browser sign-in’s keys go only to that server and the sign-in site it uses, and Arguium asks you first when that site is on another address. Arguium’s own requests to a custom server and its sign-in go only to public internet addresses, never to one on your local network; the sign-in page itself opens in your browser.
- Read-only tools you choose: every tool starts off, and only tools the server marks read-only can be turned on. That mark is the server’s own claim, so add only servers you trust. When a tool changes on the server, Arguium turns it off until you review it.
- What it returns: the server’s results go to your AI provider to write the answer, as described above for connected services, and can end up in a saved answer, which Memory can read later. What a server returns can steer the answer, as a web page can, so read such answers with care. Links in an answer that read a custom server, and in every message after it in that chat or voice session, are shown as plain text, and saved sessions keep that, except a link to one of the web pages that answer searched, listed under it, which stays a link. With Web search on, with OpenAI, the same answer can also search the web; what a custom server returns never goes into a web search.
- Logs: the app’s logs name a custom server only by an anonymous code, never by its name, its tools or what was sent.
- Removing: Remove deletes the server and its sign-in from your device and, for a browser sign-in, asks the server to revoke it, where it supports that. A pasted token stays valid at the server until you revoke it there. Signing out of Arguium, or switching to another Arguium account, removes your custom servers and their sign-ins the same way.
4. Data Sharing
We do not sell your personal information. We may share data with:
- AI Providers: Your prompts and content, including what Arguium reads from a service you connect, are sent to the AI provider you select (Google, OpenAI, or local Ollama)
- Services You Connect: only if you connect Notion, Linear, Atlassian, ClickUp, Attio, Sentry or Google Calendar in Settings → MCP Servers, that service receives the search queries Arguium sends to it to look things up for your answers, and Google Calendar receives the events you confirm; a custom server you add receives what Arguium sends it, and whoever runs it handles that under their own terms (see Custom Servers above)
- Payment Processors: Stripe handles subscription payments securely
- Infrastructure Providers: Cloudflare and Firebase for hosting and authentication; Resend for sending our email replies (it keeps a record of each email for 30 days)
- Support and usage review: Anthropic, whose AI assistant helps us read support messages, feedback, account and usage records and server logs, and draft replies
5. Your Rights and Choices
You have the right to:
- Access your personal data
- Delete your account and associated data
- Object to our use of your usage data, by contacting us
- Use your own API keys to bypass our proxy
- Use a local Ollama model for chat
- Disconnect a connected service, or remove a custom server, at any time in Settings → MCP Servers, and remove Arguium’s access to Google Calendar at myaccount.google.com/connections
- Enable Stealth Mode to hide from screen sharing (on Windows; on macOS, some apps can still capture it)
6. Data Retention
We retain your account data as long as your account is active. Request records and daily usage history are retained for 90 days and server logs for 7 days. Your last sign-in time, app version and current credit and feature counters stay with your account. You may request deletion of your data at any time by contacting us.
7. Children's Privacy
Arguium is not intended for users under 13 years of age. We do not knowingly collect personal information from children.
8. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date.
9. Contact Us
If you have questions about this Privacy Policy, please contact us at: