Trust: how your data is handled
What we encrypt, who can see what, and how to delete everything. Each line matches how the service works today, including the parts that are not as protected as we want yet.
Last updated November 6, 2026
Your logins are sealed to you
Keys to the personal accounts you connect are locked in your private vault. Only your browsers and the AI apps you allowed can open it. A copy of our database plus our server key opens none of them.
Content passes through
Mail, files, calendars and documents go from the service to your AI app during a request and are not stored. Messenger chats are the exception: they are kept encrypted so your AI can search them.
Delete it yourself, at once
Remove one account, disconnect an AI app or delete your whole profile from the dashboard. Nothing waits for us. Encrypted backups roll off within 30 days.
What is encrypted
Everything sensitive is encrypted with AES-256-GCM, each connected account with its own key. What differs is who holds the key that opens that account key.
| Data | How it is protected | Who can open it |
|---|---|---|
| Keys to your personal accounts: OAuth tokens, API keys, app passwords | Sealed to you Encrypted with the account’s own key, and that key is sealed to your private vault. The vault is created on your first sign-in in a browser, with nothing to set up. | Only a request that brings a key to your vault: a browser you approved, an AI app or personal token you allowed, or your recovery key. The server keeps no key that opens it. |
| Keys to team accounts, and to personal accounts connected before your vault existed | Server key Encrypted with the account’s own key, which is wrapped by the server’s master key. Several team members use the same account, so it cannot be sealed to one person yet. | The server, to run a request. Someone holding both the database and the master key could decrypt them. Moving these accounts into vaults is our next step. |
| Messenger chats and sessions: Telegram, Telegram Bot, WhatsApp | Server key Message text, senders, chat names, attachment details, the sending queue and the session are encrypted with the account’s own key under the master key, so the messenger keeps syncing while no browser is open. Chat and message ids are stored only as keyed hashes, and search runs on keyed hashes of words. | The server, to sync, search and send. The same caveat as above applies. |
| Actions waiting for your confirmation | Server key The action and its arguments are encrypted until you answer, and deleted a day after that. | The server, to run the action once you approve it. |
| Your password and every sign-in token | Hash only The password is stored as a scrypt hash. Browser sessions, AI app tokens and personal tokens are stored only as SHA-256 hashes. | Nobody: a hash cannot be turned back into the password or token. |
| Your mail, files, calendars, documents and other service content | Not stored Fetched from the service during a request and handed to the AI app that asked. Only a write action’s result is remembered for a few minutes, so a repeated request does not run it twice. | The AI app that made the request, and the service itself. |
| Your email, name, account names, plan and the activity log | Not encrypted Stored as is and protected by access control. The activity log records which tool ran, when, from which AI app and whether it worked, never the arguments or contents. It is kept 7 days on Free, 90 on Personal and 365 on Pro. | You in the dashboard. The admin panel shows a summary (see below). |
Who can see what
Each party that touches your data, what it gets and what it never gets.
Your AI apps
Sees
- The tools you allow, and the results of the calls it makes, within your rules and access profiles
- The names of the connected accounts it can use
- A request to confirm a risky action, if you chose to confirm in the chat
Never sees
- Your passwords and service keys: they never leave Manyplug
- Accounts outside its access profile
- What your other AI apps asked for
Your team
Sees
- Team accounts, which every member can use
- A personal account you shared with them, at the level you chose
- The member list: names and emails
- Whoever pays for the team: the team’s actions counted in their plan’s usage, not what they were
Never sees
- Your personal accounts that you did not share, including the team’s owner and admins
- Your sign-in, your other AI apps or your own plan’s usage
Manyplug staff (the admin panel)
Sees
- Your email, name, how you sign in and your active sessions
- Your plan, payment status and usage counts
- Which services you connected, their names and whether they work
- Which AI apps are signed in
Never sees
- Service keys or tokens: no admin screen decrypts anything
- The contents of your mail, files or messages
- Call arguments or your AI chats
People who run the servers
Sees
- Manyplug is run by one person today. With both the database and the server’s master key, that person could technically decrypt team accounts, messenger chats and accounts not yet in a vault. We don’t, and we say plainly that it is possible.
Never sees
- Your sealed accounts: opening them would take shipping changed code to the server and waiting for one of your own requests
The services you connect
Sees
- The requests made on your behalf, as if you used the service yourself
- In messengers, your contacts see the messages your AI sends and, once it replies, that the chat was read. Reading alone marks nothing as read.
Never sees
- Which AI app made the request, unless the request itself says so
Providers we rely on
Sees
- Paddle, our reseller and Merchant of Record: your payment details and billing address. We get only the plan, status and subscription id.
- Render (Frankfurt, EU): hosts the servers and the encrypted database
- Our email provider: the address and text of emails we send you
- An error tracker, when enabled: error reports scrubbed of arguments, tokens and contents
Never sees
- Your service keys in readable form
- Card numbers on our side: we never see them
How to delete your data
All of it is self-service and takes effect at once.
Remove one account
In the dashboard open Services, open the account and press Remove. Or ask your AI, for example “remove my old Gmail”: removal from the chat waits for your confirmation. Its keys are erased at once, and for a messenger so are all stored chats, the sending queue and the session. To revoke access on the service’s side too, use its own settings (for Google: myaccount.google.com/permissions).
Disconnect an AI app
Open AI apps, open the app and press Disconnect. Its tokens and its access to your vault are deleted. It can connect again only after you sign in.
Delete your Manyplug profile
Open Settings, find Delete account, type your email and press Delete for good. Every connected account, key, token, chat and the history are deleted right away.
- The activity log already deletes itself: entries older than your plan’s period (7, 90 or 365 days) are removed every day.
- Deleted data can stay in encrypted database backups for up to 30 days, until those backups expire.
- Paddle keeps records of payments as tax law requires, under its own policy.
- Want a copy of your data, or something deleted that you cannot reach? Write to support@manyplug.com. We answer within 30 days.
What we do not claim
So that the rest of this page can be trusted:
- Manyplug is not end-to-end encrypted. To send an email for you, the server has to see that email for the moment it sends it.
- It is not “zero-knowledge” yet: team accounts, messengers and accounts from before your vault use the server key, as described above.
- Code running on the server could capture a key while one of your real requests runs. What protects you here is who can change and deploy that code.
- There is no external audit or certification (such as SOC 2) yet.
- Your AI app’s provider receives the results it asked for and handles them under its own policy.