Frequently asked questions

Mio is a Slack-native AI coworker. You @mio in any channel and it answers questions about your company, prepares meetings, ships weekly briefs, and acts across 3,000+ integrations including Notion, Linear, Google Workspace, GitHub, and HubSpot.

Mio is grounded in your company's actual data: your messages, docs, tickets, and calendar. General chatbots answer from public information; Mio answers from your team's context, and takes actions on your behalf across your connected tools.

Mio only reads messages and shared files in channels you invite it to, and in DMs with the Mio app itself. Optional integrations like Google Workspace, Notion, Linear, HubSpot, and GitHub only run if you connect them. Mio never trains AI models on your data.

Mio is GDPR compliant and runs on Google Cloud Platform in Europe, with encryption at rest and in transit. Integration credentials are encrypted.

About 30 seconds. A Slack workspace admin clicks Add to Slack at app.mio.xyz, approves the standard Slack permissions, and Mio is live in your workspace. Inviting Mio to channels and connecting integrations takes another minute.

Mio is free to start. We’re currently in early access, onboarding a team a day. When it’s your turn, you’ll get an email.

Mio connects to 3,000+ tools through managed OAuth, including Slack, Notion, Linear, GitHub, Google Workspace (Gmail, Drive, Calendar, Docs, Sheets), HubSpot, Asana, Calendly, PostHog, Sentry, and Supabase. Each integration is connected per-user with one click — there are no API keys to paste.

Ask Mio in Slack and it answers questions about your company, prepares meeting briefs, drafts weekly and investor updates, summarizes project status, triages your Slack, and can even read an error and open a pull request. It acts on demand or on a schedule you set.

Mio is Slack-native — you use it by mentioning @mio in any channel or DM. It reaches into your other connected tools to gather context and take actions, but Slack is where you talk to it. There is no separate app or dashboard to check day to day, aside from app.mio.xyz for installation and managing integrations.

No. Mio drafts and proposes, and you stay the editor on every draft and the approver on every action. Sensitive actions wait for an explicit yes before anything goes out.

Mio works for teams of any size, from early-stage startups to scaled companies. It is most valuable once enough of your work lives across multiple connected tools and Slack channels, since that context is what it synthesizes. Solo founders and full leadership teams both use it.

Mio understands and responds in many languages — ask it in your language and it answers in kind. This site is available in English, Spanish, Japanese, Korean, Indonesian, and Thai.

If you connect Google Calendar, Mio finds the meeting and reads the attendees from the invite. You can also name the person or company directly in your message and Mio will search across your connected tools for context.

On demand for now — you ask Mio in Slack and it replies with the brief. Automatic pre-meeting briefing is on the roadmap. Email support@mio.xyz to register interest.

Yes. For internal meetings, Mio draws on the attendees’ Slack history, shared docs, and project status instead of CRM data. Ask “@Mio prep for my weekly with the engineering team” and it will pull recent channel activity, open issues, and pending decisions.

Typically 10–30 seconds. Mio streams the reply in Slack as it builds it, so you start reading immediately.

Scheduled recaps are on the roadmap. For now you trigger them on demand with one message in Slack. Email support@mio.xyz to be notified when scheduled recaps ship.

Yes. Ask Mio to recap multiple channels at once: “@Mio draft a company weekly covering #engineering, #sales, and #ops.” Mio reads all three channels and merges the output into a single structured update.

No. Mio only reads messages in channels it has been explicitly invited to. To include a channel in recaps, type /invite @Mio in that channel first.

Tell Mio in natural language. “@Mio draft the weekly for #engineering, focus on what shipped and skip anything still in planning.” Mio follows your instructions and adjusts the output accordingly.

Scheduled briefs are on the roadmap. For now, you trigger the brief with one message in Slack when you start your day. Email support@mio.xyz to be notified when scheduled delivery ships.

Yes. Ask Mio in a shared channel and the brief posts there for everyone to read. Useful for leadership teams that want a shared morning context before a daily standup or async check-in.

By default, Mio looks at activity since your last session — typically the previous working day. You can also specify “@Mio brief me on the last 48 hours” if you’re returning from a weekend or time off.

Yes. Tell Mio in natural language what to focus on. “@Mio give me my morning brief focused on sales and any engineering incidents.” Mio adjusts the scope of the brief based on your instructions.

No. Mio handles information retrieval and synthesis — answering questions, drafting recaps, preparing briefs. A Chief of Staff handles judgment, relationships, and execution. The two work well together: Mio does the data work so your CoS can focus on the higher-order tasks.

Yes. Mio works with whatever you connect. It’s most useful when it can read across your full stack, but it adds value from day one with just Slack and one or two integrations. Connect more tools as your team grows.

Mio is GDPR compliant and runs on Google Cloud Platform in Europe, with encryption at rest and in transit. It only reads data you explicitly grant it access to, and never trains AI models on your data. See our Privacy Policy for full details.

Visit app.mio.xyz, click Add to Slack, approve the standard Slack permissions, and Mio is live. Invite it to a channel with /invite @Mio and ask your first question. The whole setup takes under 5 minutes.

Yes. Mio is installed at the workspace level, so all members of the workspace can use it. Each person connects their own tool integrations individually. A Chief of Staff can ask questions on behalf of the exec team, or invite Mio to shared channels so everyone can query it directly.

Only if you invite it. Mio only reads messages in channels where it has been explicitly added with /invite @Mio. You control exactly which channels it can see, including sensitive exec and board channels.

Yes. Ask Mio to pull the relevant data from your connected tools and draft a structured outline. It works best as a starting point — you review, refine the narrative, and add the judgment Mio can’t provide. It saves the hours of data collection, not the final editorial pass.

Install Mio from app.mio.xyz, invite it to your exec and leadership channels, and connect the key integrations (Google Workspace, your CRM, your project tool). That setup takes under 10 minutes. Email support@mio.xyz if you want help configuring it for your team’s specific workflow.

Mio hosts customer data on Google Cloud in Paris, France (region europe-west9), encrypted in transit and at rest. Workflow orchestration runs in Frankfurt (region europe-west3).

No. Mio never uses customer data to train AI models. Your messages, files, and integration data are used only to answer your team’s questions and take the actions you request.

Yes. Mio is GDPR compliant and hosts EU customer data in the EU. A Data Processing Agreement, SOC 2 report, and security questionnaire are available on request — write to security@mio.xyz.

Mio’s core sub-processors include Google Cloud (hosting), Anthropic (Claude LLM inference), OpenAI (text embeddings), Slack, Langfuse (observability), Tavily (web search), Temporal Cloud (orchestration), and Pipedream (integration connectors). A complete, current list is available on request. Optional integrations you connect are data sources you authorize, not Mio sub-processors.

A workspace owner can delete all workspace data from app.mio.xyz at any time, and Mio deletes customer data within 30 days of account termination. Encrypted backups are purged on a rolling basis after that.

Email security@mio.xyz. We acknowledge reports within 48 hours and won’t take legal action against good-faith research conducted under standard responsible-disclosure practice.