Boardwell privacy policy
Last updated 17 November 2026
Boardwell is a set of Trello Power-Ups made by Codefoundry Software LLC. This page explains what data Boardwell reads from Trello, and from a Google or Notion account if you connect one, what it uses that data for, where it goes, how long it is kept, and how to remove it. Most board data goes from Trello to your browser and nowhere else. The exceptions, where Boardwell's server handles your data, are listed below. Google account data has its own section, Google user data.
What Boardwell reads
When you authorize Boardwell, Trello asks you to let it read your boards, your member profile and your workspaces. Boardwell uses that access to load the boards you open: lists, cards, labels, members, checklists, custom fields and card history. If you choose Workspace, it loads the open boards in that workspace that you can see.
Where your data goes
- Your browser only. Board data is fetched straight from Trello's API into the browser tab you are using, and queries, charts and files are made there. The other items in this list are the only times Boardwell's server receives board data.
- Checking your plan. To show whether a workspace has a paid plan, your browser sends your Trello sign-in token and the board's id to Boardwell's server. The server uses the token once, to ask Trello which workspace the board is in and that you can see it, and does not keep it.
- Share links (Share Links by Boardwell). When you make a share link, Boardwell's server keeps your Trello read-only token for Share Links by Boardwell, encrypted, so it can read the board when someone opens the link. Each time a link is opened, the server reads the board from Trello with that token and sends the viewer only the cards and fields you picked for the link. The board's content is held in the server's memory for at most two minutes, so a page opened again soon after doesn't ask Trello again, and is never written to disk. The token is never sent to anyone who opens a link.
- Google Sheets (Cards Exporter and Cards Importer). If you connect a Google account, Boardwell asks Google for your email address, so it can show which account is connected, and for access to only the spreadsheets Boardwell makes or you pick in Google's file picker (Google's
drive.filepermission). Boardwell can't see any other file in your Drive. When you send cards, your browser writes them to the spreadsheet with a Google access token that lasts about an hour, and the board data doesn't pass through Boardwell's server. When you import, your browser reads the rows of the spreadsheet you picked the same way. Google user data below has the details. - Notion (Cards Exporter and Cards Importer). If you connect Notion, Notion asks you which pages Boardwell may use, and Boardwell can read, add and update content only in those pages. It can't read your Notion member list or anyone's email address. Notion doesn't accept requests from browsers, so sends and imports go through Boardwell's server. The cards you send, or the rows you import, pass through it between Trello and Notion and are held in memory only while that happens.
- No analytics or advertising. Boardwell sets no cookies and loads no trackers, analytics or ads.
- Hosting. Boardwell's pages and scripts are static files served by Cloudflare. Like any website, Cloudflare may keep standard request logs, such as IP addresses and page addresses. Those logs never contain board data.
What is stored, and where
- Your Trello sign-in token is kept by Trello in the Power-Up's private data for your account. Only you can read it. Removing Boardwell's access in Trello revokes it.
- Forms (Intake Forms by Boardwell). When you save a form, Boardwell's server keeps your Trello read and write token for Intake Forms by Boardwell, encrypted, so it can add a card when someone sends the form. It uses that token only to add the card to the list you picked and fill in that card's custom fields. What a person types into a form goes straight onto the new card in Trello; Boardwell's server doesn't keep it. To limit abuse, the server counts responses per form and per sender for one hour, with the sender's internet address kept only as a one-way code that changes every hour; these counts are deleted after a day. Files sent with a form are passed straight on to Trello as attachments of the new card and are not kept by Boardwell; Trello checks attachments for malware. If the form's team has switched on Cloudflare Turnstile, the form page loads Cloudflare's check, which looks at signals from the visitor's browser to tell people from automated scripts, and Boardwell's server asks Cloudflare whether the check passed before adding the card (see Cloudflare's Turnstile privacy addendum).
- What you save for everyone on a board in Board Insights by Boardwell (saved tiles, reports, team queries, and the order and choice of tiles on Insights) is kept on Boardwell's server, under the board's Trello id. This is what you typed or picked: names, queries and Trello ids such as lists, labels and people a tile filters by. No card text is stored, and who saved each item isn't recorded. Anyone who can see the board can read it, and members who can edit the board can change it. Delete an item where you saved it. Card badge settings and the workflow lists are stored by Trello in the Power-Up's shared data for that board.
- What you save just for yourself (your own tiles and reports in Board Insights, and your saved views and chosen boards in Table View) is stored by Trello in the Power-Up's private data for your account on that board.
- A cache of recent views is kept in your browser's local storage on your device, so they open instantly. It holds your last ten views, each either one board or one workspace. A workspace view includes every board loaded with it, up to 50. Use Clear saved boards in Board settings › Your data to remove it, or clear this site's data in your browser.
- The spreadsheet each board was last sent to (its id, name and address) is kept in your browser's local storage on your device, so the next send updates the same spreadsheet. Clear this site's data in your browser to remove it.
- A copy of Trello's history (Audit Log by Boardwell) is kept in your browser's IndexedDB storage on your device, for up to 200 boards you have opened in the log, so the next open only asks Trello for what's new. It holds what Trello's history already contains: who changed what, when, and the old and new text. Nothing from it is sent to Boardwell's server. Clear this site's data in your browser to remove it.
- Linked templates (Master Templates by Boardwell) are stored by Trello in the Power-Up's shared data on the template board: the ids and names of the template and the boards made from it, and for the last ten syncs when they ran, who ran them (their Trello name), how many boards changed and a short note of what was added. Undo for the last sync is kept in your browser's IndexedDB storage on your device: the ids of the lists, cards and checklist items it added. Nothing from either is sent to Boardwell's server.
- Share links are kept on Boardwell's server as Trello ids and the link's settings only (which lists, labels, people, card and fields it shows, its expiry and a hashed password), with the Trello member id of whoever made it. No board, card or people names and no card text are stored. Your Share Links by Boardwell token is stored encrypted, and is deleted when Trello stops accepting it.
- Forms are kept on Boardwell's server as the wording their makers wrote (title, introduction, questions, choices, thank-you message), Trello ids (the list, labels, people and custom fields they fill), whether they're paused, their closing date, and how many cards they have added. Your Intake Forms by Boardwell token is stored encrypted, and is deleted when you delete your last form or Trello stops accepting it.
- Google and Notion connections are kept on Boardwell's server under your Trello member id, so the Exporter and the Importer share them. For Google that is the refresh token, encrypted, and the account's email address. For Notion it is the access token, encrypted, and the workspace's name. No card text is kept with them. Choose Disconnect in the Exporter or Importer to delete a connection at once; Boardwell also asks Google or Notion to revoke the token.
- Usage counts. To see how teams find and start the paid plan, Boardwell's server counts a few steps per Trello workspace: adding a Power-Up, starting the trial, seeing the trial-ended screen, opening Billing, starting checkout and the first payment. Each count keeps only the workspace's id, which Power-Up it was, when it first and last happened and how many times. No names, member ids, board or card data. The server also sends each step, the first time a workspace reaches it, to PostHog (in the United States), which charts them for us: only the workspace's id, which Power-Up it was and when. Nothing is sent from your browser, and no internet address goes with it.
- Paid plans. When someone starts a plan, Boardwell's server keeps the Trello workspace's id, the Trello member id of the person who started it, and the plan's Stripe ids and status. Payment is handled by Stripe: card details and billing contact go to Stripe, never to Boardwell. Boardwell sends Stripe only those Trello ids, no names, email addresses or board data.
Google user data
This section covers the data Boardwell receives when you connect a Google account to Cards Exporter by Boardwell, to send a board to Google Sheets, or to Cards Importer by Boardwell, to make cards from a spreadsheet. Connecting is optional, and nothing here applies until you do.
What Boardwell accesses
Boardwell asks Google for these permissions, and no others:
- Your email address (
openidandhttps://www.googleapis.com/auth/userinfo.email), to show which Google account is connected. - Only the Google Drive files you use with Boardwell (
https://www.googleapis.com/auth/drive.file): the spreadsheets Boardwell creates for you, and the ones you pick in Google's file picker. Boardwell can't see, list or open any other file in your Drive.
Boardwell doesn't ask for your name, contacts, calendar, Gmail or any other Google data.
How Boardwell uses it
- Your email address is shown in the Exporter so you know which account your cards go to.
- When you pick a spreadsheet in Google's file picker, Boardwell gets access to that one file. The Exporter writes to it, or the Importer reads its rows so you can turn them into cards.
- The Drive permission is used to create a spreadsheet when you first send a board, and to write the board's cards, checklist items and lists into that spreadsheet each time you send it again. Boardwell writes only to its own tabs (Cards, Checklist items and Lists) and leaves your other tabs alone.
- Boardwell uses Google data for nothing else.
Where it goes and how it is stored
- When you send cards, your browser writes them to the spreadsheet directly, using a Google access token that expires after about an hour. The cards don't pass through Boardwell's server.
- Boardwell's server keeps two things for each connected account, under your Trello member id: Google's refresh token, encrypted with AES-256-GCM, and the account's email address. The server uses the refresh token only to give your browser a new short-lived access token when you send cards.
- Your browser keeps the id, name and address of the spreadsheet each board was last sent to, in local storage on your device, so the next send updates the same spreadsheet.
- Boardwell keeps no copy of what is in your spreadsheets.
- Data travels over HTTPS, and the server and database are hosted by Cloudflare.
Sharing
Boardwell doesn't sell, rent or share Google user data with anyone. It doesn't use Google data for advertising, and it doesn't use it to develop, improve or train AI or machine learning models. It transfers Google data to no one else, except where needed to provide the feature you asked for, to comply with the law, or as part of a merger or sale of the business, in which case the buyer must follow this policy. No person at Boardwell reads your Google data unless you ask for help with it, or it's needed for security or to comply with the law.
Keeping and deleting it
Boardwell keeps the refresh token and email address until you disconnect. Choose Disconnect in Cards Exporter to delete them from Boardwell's server at once; Boardwell also asks Google to revoke the token. Removing Boardwell from the third-party connections in your Google account revokes its access too, and Boardwell deletes the stored token the next time it finds the token no longer works. To have everything deleted, write to support@boardwellfortrello.com. Spreadsheets Boardwell created stay in your Drive, and you can delete them like any other file.
Limited Use
Boardwell's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Removing your data
Disable the Power-Up on a board to stop Boardwell from loading it. Revoke Boardwell's access from your Atlassian account settings to delete the sign-in token. Clear the cache as described above. Revoke a share link from the Share window to delete it at once; anyone opening it after that sees that it doesn't work. Revoking Share Links by Boardwell's access in your Trello account settings stops every link you made. Delete a form from the Forms window to stop it at once; the cards it added stay on the board. Disconnect Google or Notion in the Exporter or Importer to delete that connection and stop its schedules. You can also remove Boardwell from your Google account or from the connections in your Notion settings. Apart from plan records and usage counts, what a board saves for everyone in Insights, share link settings, forms, the Share and Forms tokens, and Google and Notion connections, Boardwell holds no copy of your data. A workspace's plan record stays after the plan ends, so the free trial is offered only once.
Children
Boardwell is a business tool and is not directed at children.
Changes
If this policy changes, we will update this page and the date at the top.
Contact
Questions about privacy: support@boardwellfortrello.com.