AI assistant connectors let Mio search and read your own accounts — Google Drive, Gmail, GitHub, Slack and nine others — strictly when you ask a question that needs them. All 12 are read-only by default, and understanding exactly what “read-only” means, and what it protects you from, is the difference between connecting an account with confidence and being nervous about what an AI assistant can touch.
What “Read-Only” Actually Means Here
A connector gives Mio permission to search and read content inside an account you’ve linked — it does not give Mio permission to send, delete, edit or move anything in that account unless a separate write-action capability is explicitly turned on. The features page is specific about this per connector: Gmail is described as “search your Gmail and read message text (read-only),” Microsoft 365 as “OneDrive files, Outlook mail and calendar (read-only).” The rest — Google Drive, Google Calendar, GitHub, Dropbox, Notion, Slack, Trello, Todoist, PostRSS and Talkmio — are described the same way: search and read, not write.
This matters practically. If you connect Gmail and ask “find the invoice from our supplier last month,” Mio can search your mailbox and quote the relevant message back to you. It cannot, through that connector alone, send a reply, delete the email, or move it to another folder. If you connect GitHub and ask “summarize open issues tagged ‘bug’,” Mio can read the issue list and repository contents. It cannot merge a pull request or push a commit through the connector alone. Paid plans can additionally enable write actions for connectors as a separate, explicit capability, per the pricing page — but the base connection stays read-only unless that’s turned on.
All 12 Connectors
| Connector | What Mio can read |
|---|---|
| Google Drive | Search and read your Drive files and Google Docs. |
| Gmail | Search your Gmail and read message text (read-only). |
| Google Calendar | See your upcoming events and free slots. |
| Microsoft 365 | OneDrive files, Outlook mail and calendar (read-only). |
| GitHub | Your repositories, issues, pull requests and file contents. |
| Dropbox | Search and read files in your Dropbox. |
| Notion | Search your Notion pages and databases. |
| Slack | Read channels and search messages in your Slack workspace. |
| Trello | Your Trello boards, lists and cards. |
| Todoist | Your Todoist tasks and projects. |
| PostRSS | Your PostRSS feeds, targets and posting statistics. |
| Talkmio | Your Talkmio live-chat conversations and visitors. |
Two of the twelve are worth flagging as products from the same company: PostRSS and Talkmio are both built by Internet Solutions, UAB, the team behind Ask Mio, which is why they connect natively rather than through a generic integration layer.
What Read-Only Protects You From
The risk people usually imagine with connecting an AI assistant to email or a file drive is an accident: the assistant misreads an instruction and sends something it shouldn’t, deletes a file it misidentified, or overwrites a document. A read-only connector removes that entire category of risk by design — there is no write path for those accidents to travel through. Mio can misread a document and summarize it wrong, which is a real and separate risk worth checking for, but it cannot act on that misreading by changing anything in the source account, because the connector was never given permission to write in the first place.
This is a meaningfully different security posture from an integration that can act on your behalf. An assistant that can both read and send email needs you to trust its judgment about when to act; a read-only connector only needs you to trust its judgment about what to say back to you, which you can verify before doing anything with it yourself. For most day-to-day questions — “what’s on my calendar,” “find that Notion page about the Q3 roadmap,” “summarize this GitHub issue thread” — read access is also simply all that’s needed.
When You’d Want Write Actions Instead
Read-only is the sensible default, but some workflows genuinely need more — drafting and sending a reply directly from a connected inbox, updating a Trello card’s status, or committing a code fix to a repository without copy-pasting it manually. That’s what the paid-plan write-action capability is for. It’s an explicit, separate switch from the base connector, which means connecting an account for reading does not quietly grant more access later without you choosing it — the two are different permissions, not different tiers of the same one.
Connector vs Tool vs Upload: Three Ways Mio Sees Your Data
| Method | Scope | Persistence |
|---|---|---|
| Connector | Your own linked account (Drive, Gmail, GitHub, etc.) | Lasts until you disconnect it; re-queried each time |
| File upload | One file you attach to a chat | Searchable in later chats if Document memory is on |
| Tool (e.g. web search) | The public internet, not your accounts | Per-answer only, not stored |
These three are easy to conflate but solve different problems. A connector is for “look inside something I already use.” A file upload is for “look inside this one thing I’m handing you right now.” A tool like web search or Wikipedia is for public information that isn’t yours at all. Document memory, one of the nine account-level modules, is what keeps an uploaded file searchable in later chats without re-attaching it — a related but distinct capability from a connector.
How AI Assistant Connectors Compare to Full Account Access
Some AI products integrate with your accounts by requesting broad OAuth scopes that technically allow reading, writing and deleting, then relying on the assistant’s own judgment never to misuse the write access it was granted. Ask Mio’s AI assistant connectors take a narrower approach: the scope itself is limited to search and read for all 12 connectors by default, so there is no write capability sitting unused in the background waiting for a bad instruction to trigger it. The difference shows up most clearly in a worst case — if a prompt is ambiguous, malformed, or (in a shared or team account) crafted by someone else to trick the assistant into an unwanted action, a read-only connector has no destructive action available to take, regardless of how the request was phrased. That’s a structural protection, not a promise about behavior.
The trade-off, again, is convenience: you cannot ask Mio to “archive all newsletters older than a year” through a read-only Gmail connector and have it actually happen, because archiving is a write action. You’d read the list Mio finds and archive them yourself, or wait for write-action capability if your plan includes it. For most people, most of the time, that’s a fair exchange — the accounts connected to an AI assistant tend to be the ones with the most sensitive content (a work inbox, a company Drive, a private repo), which is exactly where a narrower default is worth the extra manual step.
Setting Up a Connector
Connecting one of the 12 follows the same basic pattern regardless of which account: you authorize Ask Mio through that service’s own sign-in flow (Google’s, Microsoft’s, GitHub’s, Slack’s, and so on), which is the same kind of permission screen you’d see connecting any third-party app — it lists exactly what’s being granted, which for these connectors is search and read. Once connected, the account stays linked until you remove it from your Ask Mio settings, and each new chat can reference it without you reconnecting. There’s no ongoing background sync running in the meantime; Mio queries the connected account only when a question in front of it actually calls for that source.
A Worked Example
Say you want a weekly status update pulled together from three sources: open pull requests in a GitHub repo, unresolved messages in a Slack channel, and tasks due this week in Todoist. With those three connectors linked, one prompt — “summarize this week’s engineering status from GitHub, Slack and Todoist” — can pull from all three read-only sources and return a single summary, without you manually checking three separate apps first. Nothing in any of the three accounts gets changed in the process; the connectors only ever read.
A second example on the personal side: before a trip, connecting Google Calendar and Gmail together lets a single question — “what have I already booked for the Lisbon trip” — pull flight confirmations from your inbox and cross-check them against calendar entries, catching a double-booked afternoon or a hotel confirmation that never made it onto the calendar. Again, both connectors only read; if you want the missing event added, that’s either something you do yourself from Mio’s answer or a job for write-action capability if your plan includes it.
Connectors and Where the Data Actually Sits
A separate but related question is where the content a connector reads ends up once Mio has processed it. Ask Mio stores data on servers in the EU (Germany), and chats and files are not used to train models — a policy that applies to whatever a connector pulls in as much as to a file you upload directly. If GDPR compliance is part of why you’re evaluating AI assistant connectors for a company account in the first place, the fuller picture — including what counts as a data processor relationship and what EU hosting does and doesn’t guarantee — is covered in EU-Hosted AI and GDPR: What It Means for Your Chats.
Frequently Asked Questions
Can Ask Mio send an email through the Gmail connector?
Not through the base connector — Gmail is explicitly read-only: search and read message text. Sending mail is handled separately by the E-mail tool, which always waits for your confirmation before sending to anyone but yourself, or by write-action capability on paid plans if enabled.
Does connecting Google Drive give Mio access to every file I own?
A connector lets Mio search and read your Drive when you ask a question that needs it; it does not proactively scan your entire account without a reason. The scope is “search and read on request,” not a background sync of everything you store.
Is my data from a connector used to train the model?
No. Ask Mio’s data is stored in the EU and your chats and files are not used to train models, per the pricing page FAQ. That applies to information pulled through a connector the same as anything else in your account.
What happens if I disconnect a connector?
Mio loses the ability to search and read that account going forward. Disconnecting is the way to fully revoke access — a read-only connector still requires your explicit link to function at all.
Can I use a connector without a paid plan?
Connector access and write-action capability vary by plan tier — check the current pricing page for exactly which plans include which connectors and whether write actions are available on your tier.
Why are PostRSS and Talkmio connectors when they’re not as well-known as Gmail or GitHub?
PostRSS and Talkmio are built by the same company as Ask Mio, Internet Solutions, UAB, so they’re natively supported rather than added as a generic third-party integration. If you already use either product, the connector lets Mio read your feeds or live-chat conversations the same read-only way it reads Gmail or GitHub.
The Bottom Line
AI assistant connectors solve a real problem — not having to re-explain or re-upload information that already lives somewhere you use daily — without the risk of an assistant acting on your accounts by accident, because all 12 are read-only unless you explicitly turn on more. Start with the one account you re-paste into chats most often, connect it, and see how much re-typing it saves. The pricing page has the current breakdown of which plans include which connectors.