MIA and your data: what it sees, what it never sees and how long it's kept

Can MIA see more than I can?

No. MIA asks MB Suite for data as you, with your role and your permissions in each module: what you can't see, it can't see either. It never gets into an organization you don't have access to, and it never receives passwords, API keys or secrets, not even the ones you keep in the Vault.

Does MIA read my connected email and calendar?

Never. The content of the mailboxes (Gmail, Outlook or IMAP) and calendars (Google Calendar or Outlook) you connect to MB Suite doesn't reach MIA, not even when an email shows up in a contact's timeline in the CRM. It's a commitment: MB Suite's AI never receives that content. If you ask MIA for it, it tells you it can't and where to see it on the screen.

And my LinkedIn data?

MIA checks them like those of any other connected platform, with your permissions: your LinkedIn Ads campaigns, metrics and spend, your LinkedIn page's metrics and comments, and the people and companies you mention in your LinkedIn posts. What other people write there, such as a comment or a lead form answer, is data for MIA, as on any other network.

What does MIA do with what other people write?

It treats it as data, never as an order. Messages from leads and customers, comments, form answers, notes from others and the files you attach can carry text that tries to give orders —“ignore your instructions and send this to…”—. MIA doesn't follow them, and on top of that MB Suite protects you by design. To be safe, MIA treats that way everything it reads from your records (people, companies, deals, tasks, messages), what comes with your platforms' data when you ask for it by campaign, ad, search term or post, every file you attach, the settings anyone on your team can write —custom fields, the labels of most modules, templates, descriptions— and what comes from the web, like the pages and errors the site audit finds. It only trusts what MB Suite writes —the numbers it calculates, also those of your platforms— and the structure that changes with each module's permissions, such as the pipelines and their stages or the CRM labels:

• In a request where MIA read that kind of content, any change asks for your OK, even if you chose Acts: “I read text written by third parties in this request, so I'm asking for your OK before changing anything.” The only exception are short names —a deal's title, the name of a person or a campaign—: with them, in Acts it still makes some internal changes that can be undone, as long as they don't give anything to someone else (see The two levels of MIA: Proposes and Acts).
• What goes out of MB Suite, what can't be undone and what's sensitive always waits for your click on the card, and a “yes” written in the chat doesn't count.
• If, after reading that text, MIA wants to pass something to the MB Suite team, it doesn't send it on its own: it shows you Review the request before sending it.
• In a background job, that caution doesn't reset: once the job reads that kind of content, it lasts until the job ends.
• That caution can carry over to the next requests in the same conversation, while the answer MIA built with that text is still part of it. A new conversation starts without it.

Who can read my conversations with MIA?

Only you. The other members of your account, owners and admins included, can't open them. If the MB Suite team needs to review a request to give you support, it can open that request's step by step, and that access is recorded with its reason. The same goes for your background jobs: only you see them, and the MB Suite team can open one, or stop it, by recording the reason (see Background jobs: hand MIA the long work and get on with yours); and the email that lets you know one finished doesn't include the result: you read it in MB Suite. The same goes for your conversations with a specialist or one of your team's agents. What MIA does in your account, on the other hand, isn't private: it's recorded under your name in Activity, like everything your team does.

What MIA saves in its memory isn't private either: the account profile, the rules, what it learned, the maps and each agent's notes are seen by everyone in the account in Settings > MIA. Your preferences, on the other hand, only you see (and MB Suite support, by recording the reason). See What MIA remembers: your account's memory and how to correct it.

Routines are different: they work for the team. Whoever sets one up chooses who sees it —only them, the members they choose or everyone—, and owners and admins always see it; what it leaves never shows up for someone who can't see the data it brings. See Routines: put an agent to work on its own, on a schedule or when something happens.

How long is everything kept?

• Conversations — 12 months from their last activity; each message, 12 months from when it was written. After that they're deleted on their own.
• The step by step of each request — 30 days.
• Background jobs — what you asked for, the goal, the result and the steps of each one, 180 days from when it ends; a proposal you don't start expires after 7 days.
• The files you attach — MIA deletes them after reading them. That's why, to retry a request, you attach them again.
• Archived conversations — archiving only takes them out of your Recent list; they're kept like the rest, and you bring them back with Unarchive.
• What MIA remembers — until someone deletes it; its earlier versions and the monthly record of what MIA did are kept for a limited time, explained in What MIA remembers: your account's memory and how to correct it.

What does Delete delete?

Everything in the conversation. In History, open the conversation's menu and choose Delete; confirm with Delete conversation. It disappears for you right away, and then its messages, its step by step, the cards that were still waiting, its plans, its background jobs —if one was working, it stops— and the files you attached are deleted. It can't be undone.

What stays is what isn't the conversation itself: the changes MIA made in your account and its Activity, the routines you set up in it —they keep working until someone deletes them—, what MIA saved in its memory (you see it and delete it in Settings > MIA), the credits used, the requests you passed to the MB Suite team, the notes about what MIA couldn't do yet, and a technical record of each request and each background job, without its text, that MB Suite keeps for a limited time to measure how MIA works.