Privacy

Mello for Trello, the Chrome extension. Last changed 27 October 2026.

Short version: Mello shows you your own Trello cards in your own browser. It has no servers of its own, no accounts, no analytics and no tracking. It doesn't sell, share or send your data to anyone.

What it reads

Mello reads your Trello boards, lists, cards, comments, checklists, labels, members and attachments: the same things you see on trello.com. It does that by asking trello.com, from your browser, with the Trello sign-in you already have in Chrome. It never sees or stores your Trello password, and it doesn't use an API key or token.

What you change in Mello (a due date, a comment, a card moved to another list) is sent to trello.com, the same as if you had made the change there.

On trello.com's own pages, Mello may show a small "Open Mello" pill in the corner. Of the page it reads only the address, so that Mello opens on the same board or card, and it sends nothing anywhere; it only opens Mello, or hides itself for a week when you close it.

Mello also notices a tab that is a page of a Mello server you are signed in to, so it can offer to connect it. It tells by the tab's address and the icon the page names, which Chrome shows it for every tab; it reads nothing on the page itself. When a tab opens a Mello server's Connect Mello for Chrome page (the server's pill links there), Mello closes that tab and asks in its own whether to connect the server.

If you connect a Jira Cloud site (an address ending in atlassian.net), Mello reads the issues its query finds there: their summaries, statuses, assignees, reporters, labels, due dates, priorities and types. When you open one, it reads the rest: its description, comments, other fields, sub-tasks and linked issues, and the list of its attachments, with small pictures of the ones that are images. A file is fetched only when you open it, and stays in that page: Mello keeps no copy. It asks the site from your browser, with the Jira sign-in you already have in Chrome. It never sees your Atlassian password and doesn't use an API token. When you change an issue in Mello (move it, edit a field, comment on it, or add one), Mello sends that change to the site, the same way and nowhere else.

On a Jira site's own pages, Mello may show a pill offering to add that site. Of the page it reads only the address, to know it is Jira and which site; it sends nothing anywhere until you click Add, and ✕ stops it asking about that site for a month.

What it keeps, and where

Everything Mello keeps stays in Chrome on your computer, in the extension's own storage:

• your settings: theme, columns, which boards and lists you hide, and so on
• the order you rank cards in
• a copy of the cards it last loaded, so it opens quickly
• smaller copies of pictures from your cards, so they load quickly the second time

None of this leaves your computer. Removing the extension deletes all of it. ⚙ Settings → Your setup → Export saves your settings to a file only when you ask it to.

Who it talks to

• trello.com, to read and change your boards, as above.
• Nobody else, unless you add a server of your own under ⚙ Settings → Servers. Then Mello also talks to that server, at the address you typed, with the sign-in you gave it. A server you add is run by you or by whoever you got the address from, and its own privacy terms apply to what it keeps.
• A Mello server open in one of your tabs, when that page says you are signed in there. Mello asks it once what it is (its name and version, which it tells anyone) and sends nothing about you. If you then click Connect, Chrome asks you to allow that address, and Mello asks the server for a sign-in of its own for this browser, using the sign-in you already have there.
• A Jira Cloud site you connect, to read the issues its query finds and to send the changes you make to them, as above. Nothing from Jira is sent to any other address: not to trello.com and not to a Mello server.

Mello contains no analytics, advertising, crash reporting or tracking code, and loads no code from anywhere: everything it runs ships inside the extension.

Permissions

• Storage and unlimited storage: to keep the settings, ranking and copies described above on your computer. Unlimited, because a few hundred cards with pictures can pass Chrome's default limit.
• Access to trello.com: to read and change your boards, and to show the "Open Mello" pill on Trello's pages.
• Access to atlassian.net sites: to read and change the issues of a Jira site you connect, and to show the pill that offers a Jira site on its own pages. Mello reads a site only after you connect it.
• Tabs and scripting: Trello only accepts requests made from a trello.com page, so Mello sends its requests from a trello.com tab, opening one in the background if none is open. The same permission lets Mello's button bring its own tab back instead of opening a second one, and shows it which tab is a Mello server's page, as above.
• Other sites, only if you ask: when you add a server of your own, Chrome asks you to allow that one address. Mello asks for nothing else.

Children

Mello isn't aimed at children and doesn't knowingly handle children's data.

Changes

If this policy changes, the new version will be at this address, with the date at the top changed. A change that lets Mello send your data anywhere new would come with a new version of the extension that tells you so first.

Contact

Questions about this policy: use the contact email on Mello's Chrome Web Store page.

Mello is an independent project. It isn't made by, endorsed by or affiliated with Trello or Atlassian. Trello and Jira are trademarks of Atlassian.