Support

Talk to a human — usually within one business day.

How to reach us

• General support. Email support@mio.xyz for help installing Mio, connecting integrations, billing questions, bug reports, or anything else. We aim to respond within one business day (Monday–Friday, Paris time).
• Security disclosures. If you’ve found a vulnerability or suspect a security incident, email security@mio.xyz directly. We acknowledge security reports within one business day. Please do not publicly disclose issues before we’ve had a chance to investigate.
• App dashboard. Manage connected integrations, review what Mio can see, and delete your workspace data at app.mio.xyz.
• Privacy and legal. See our Privacy Policy and Terms of Service.

Common topics

1. Installing Mio in your Slack workspace

A Slack workspace admin installs Mio by visiting app.mio.xyz and clicking Add to Slack. Slack will prompt for the permissions Mio needs to operate; review and approve them. Mio is added to your workspace and the admin who installed it becomes the initial workspace owner inside Mio.

Stuck on the install? Email support@mio.xyz with the workspace URL and a description of what you’re seeing, and we’ll help.

2. Inviting Mio to channels and DMs

• Channels. Type /invite @Mio in any channel you want Mio to participate in. Mio only reads messages and files in channels it’s been explicitly invited to.
• Direct messages. Open a DM with the Mio app from the Slack sidebar and start typing. DMs with the Mio app are visible only to you and Mio — other workspace members can’t read them.
• Threads. Mention @Mio in a thread to bring it in for a specific question without adding it to the channel as a whole.

3. Connecting integrations

Optional integrations — Notion, Linear, HubSpot, Google Workspace (Gmail, Drive, Calendar), Calendly, Asana, GitHub, PostHog, Sentry, and Supabase — only run if you explicitly connect them. Each integration is connected per-user from app.mio.xyz and uses standard OAuth.

If a connection fails or appears stuck, disconnect and reconnect from the dashboard. If that doesn’t resolve it, email support@mio.xyz with the integration name and the approximate time you tried.

4. Managing what Mio can read

• Slack scope. Mio can only see messages and shared files in channels where it’s been invited, and in DMs with the Mio app itself. To remove Mio from a channel, use Slack’s Kick from channel menu.
• Integration scope. Each integration controls what Mio can access on its own side. Disconnect any integration from the Mio dashboard to revoke access.
• Workspace controls. Workspace owners can audit connected integrations and active members from the Mio dashboard.

5. Billing and account changes

View invoices, update payment details, and change plans from the Billing section of app.mio.xyz. For invoice questions, refunds, plan changes, or tax/VAT documentation, email support@mio.xyz.

6. Uninstalling Mio and deleting your data

Removing Mio from Slack and deleting your stored data are two separate steps. Do both if you want Mio fully out:

• Step 1 — Revoke Slack access. In Slack, go to Settings & administration → Manage apps, search for Mio, and click Remove app. This revokes Mio’s Slack tokens immediately. Uninstalling on its own does not delete the data we already hold — you also need Step 2.
• Step 2 — Delete workspace data. In the Mio dashboard at app.mio.xyz, a workspace owner can trigger a Delete workspace data action. This removes all messages, files, embeddings, and integration credentials we hold for the workspace from our production database and object storage immediately. Encrypted backups may retain data for up to 14 days, after which they are automatically purged.

If you don’t see a delete option, or if you want us to confirm deletion in writing, email security@mio.xyz from the address of the admin who installed Mio and we’ll handle it.

7. Reporting a bug

Send a note to support@mio.xyz with:

• Your workspace URL.
• Approximate time the issue occurred (with timezone).
• What you expected to happen and what actually happened.
• Screenshots or screen recordings if you have them.

The more detail, the faster we can reproduce. We’ll acknowledge within one business day and follow up when there’s a fix or a workaround.

8. Requesting a feature

We read every request. Email support@mio.xyz with the problem you’re trying to solve — not just the solution — and we’ll let you know if it’s already on the roadmap, if we’d like to interview you about it, or if it’s out of scope.

9. Security and responsible disclosure

Report security issues to security@mio.xyz. Useful details to include:

• A clear description of the issue and its impact.
• Steps to reproduce, including any affected URLs, accounts, or workspaces.
• Your assessment of severity and any suggested remediation.

We commit to acknowledging reports within one business day, keeping you updated on remediation, and crediting reporters who’d like to be named. Please give us a reasonable window to investigate and patch before public disclosure.

10. Status and incidents

We do not yet operate a public status page. For ongoing incidents or degraded service, email support@mio.xyz and we’ll share the current status and ETA. Workspace admins are notified by email when incidents affect their data.

11. Contact

General support: support@mio.xyz
Security disclosures: security@mio.xyz

Tools for Sovereignty Inc.
Delaware, USA