Your AI Assistant Should Not Be Ours

The useful part of an AI assistant was never the model. It is the data the model can reach. That is exactly the part most providers keep for themselves.

Every provider is adding AI. Almost none are adding a choice

Summarise this thread. Draft a reply. Find the invoice from March. The feature is always the headline, and the arrangement underneath it never is. Your provider runs the model. Your provider decides which of your data it reads. Your provider decides how long that lasts and what the terms say next year.

InfoPeak went the other way. We run no AI at all. Instead, the assistant you already use can reach your InfoPeak data directly, with permissions you set and can take back.

What MCP is, in one paragraph

MCP, the Model Context Protocol, is a published standard for letting an AI tool talk to a service. Claude speaks it. ChatGPT speaks it. So does a growing list of developer tools. The idea is the one that already makes IMAP and CalDAV worth having: one open protocol, many clients, nobody locked in. InfoPeak runs an MCP server at mcp.infopeak.io. You point your tool at that address, approve what it may do, and your assistant can search your mail, read a message, check your calendar, look up a contact or open a file.

You choose the tool. We handle the access.

• You choose the tool. Claude, ChatGPT or something else entirely. We do not recommend one over another, and we do not sit in the middle of the conversation.
• You choose the reach. Mail, calendar, contacts and files are separate permissions, and each one is read or write. Nothing arrives bundled.
• You choose when it ends. Every connection is listed under Security in your settings. Withdraw one and it stops working immediately, everywhere.

The permission is real, not a label

A checkbox that only changes a label is theatre. When you decline mail sending, the tool for sending mail does not appear in the list your assistant receives. It is not disabled, not greyed out, not refused after the fact. As far as the assistant is concerned, it was never there.

The access itself is a scoped device code with an expiry, the same mechanism that already decides what a phone or a mail client may reach. It lapses after an hour and renews behind the scenes. Your account password is never handed to the tool at any point.

Why we did not build an assistant of our own

Building one would have required the single thing we have engineered ourselves out of: the ability to read your data. Your mail, files and calendar are locked with a key that only your password opens, which is the whole point of how the platform is built. An InfoPeak assistant would have meant keeping a copy of that key, or asking you to give it up. For a provider built this way, the honest version of an AI feature is to let you bring your own.

What your assistant can reach today

• Mail. Search, read, send, move and mark as read.
• Calendar. Every calendar you have, shared ones included, and create, change or delete.
• Contacts. Search, create, change and delete.
• Drive. Browse folders, read text files, upload, and create or remove folders.

Notes, Docs and Messenger are not reachable yet, and the reason is worth saying plainly: they have no open protocol for the server to speak. We would rather give Notes a real interface of its own than let the AI server reach into the database behind everything else. Images and PDFs can be listed but not read as text.

Where this fits, whoever you are

• On your own. One assistant, one inbox, one calendar. See InfoPeak One.
• In a household. Several people, several assistants, one shared family calendar that each of them can read without anyone handing over a key. See InfoPeak Family.
• At work. Client mail and appointments an assistant can reach, on a platform that answers to European law. See InfoPeak Professional.

Questions people ask

Does InfoPeak train AI on my data?

No. We run no AI, and we cannot read your data in the first place. What your own assistant does with what it reads is governed by the terms of the tool you picked, which is one more reason the choice should be yours.

Which plans include it?

All of them, including Free. IMAP, CalDAV, CardDAV and WebDAV are open on every plan, so anyone who can write code could already build this themselves. Charging for the convenient version would only shut out the people who cannot.

Do I have to hand over my password?

Not to the tool. The approval screen sits on our own domain and asks for it once, because the key that opens your data cannot be produced without it. The tool receives a scoped code, never the password.

Can I connect more than one tool?

Yes. Each one is listed on its own, with its own permissions, and each can be withdrawn without touching the others.

What happens when I withdraw access?

The connection stops working immediately. Withdrawing removes the consent itself and not merely the current code, so the tool cannot quietly renew an hour later.

Where do I set it up?

On the connect page, next to the guides for mail, calendar and Drive. It takes an address, a few checkboxes and about a minute.