Security and your data
How your data is kept safe
The short version: your cards stay in Trello, payments stay with Stripe, and our server holds almost nothing. This page says exactly what, so you can check it instead of taking our word for it.
Where your data goes
Spreadsheet Importer, Card Approvals and Bulk Edit Sheet run in your own browser, inside Trello, and talk to Trello directly. Our server is not in the middle of that conversation. Request Forms is the exception, because a public form has to add cards when you are not there; what that means is set out below.
| Power-Up | Where the work happens | What reaches our server |
|---|---|---|
| Spreadsheet Importer | Your spreadsheet is read inside your browser and cards go between your browser and Trello. | Only if you choose Paste text: that text is sent to our server and on to Anthropic to be split into cards. It is not stored. |
| Card Approvals | The approval record is kept on the card, in Trello. | A short statement of who approved what passes through our signing service to be countersigned. It is not stored or logged. |
| Bulk Edit Sheet | Cards are read and changed between your browser and Trello. Unapplied edits are kept in your own browser. | Nothing. |
| Request Forms | A form has to work while nobody is at Trello, so this one does run on our server: it receives each response and adds the card. | The form you built, the permission you gave it (encrypted), and each response on its way to Trello. Responses are not stored. |
For every Power-Up our server also learns one thing: whether your Trello workspace has a subscription. It knows the workspace by its Trello id, not by name.
What our server stores
- Subscriptions: the Trello workspace id and Stripe's own reference numbers. No names, no email addresses, no card details.
- A monthly count of how many times a workspace has used Paste text, to apply its allowance.
- Error lines: if something fails on our side, one line with a reference code, the address of the page that failed and the kind of error, kept for a few days. It holds nothing from your cards or files.
- Request Forms only: the forms you build, the Trello member id of whoever connected the board with their permission (encrypted), a monthly count of responses, and for one day a scrambled marker per response that stops duplicates. The responses themselves are not stored.
That is the whole list. There is no database of your boards or of your form responses.
How Request Forms holds its permission
- Trello hands the permission to our server once, when you choose Connect. It is never kept in a browser and never sent back out.
- It is encrypted with AES-256 before it is stored, and tied to the one board and member it was given for, so a stored copy is useless anywhere else.
- A form can only add cards to its own board. Every list, label, member and custom field a form names is checked against that board on our server.
- Disconnect withdraws the permission at Trello itself. If you revoke it in Trello's settings or delete your Trello account, Trello tells us and our copy is deleted.
- Public forms are served from a separate address, forms.stumason.dev, by a separate program that holds no payment or signing keys.
- Answers are added to cards as plain text, so a stranger cannot plant links, pictures or mentions in your board.
The permission Trello asks you for
The importer and the sheet need to read and change cards, so Trello asks you to allow that. Trello only offers this permission for all the boards you can edit; the Power-Up works on the board you opened it from and nowhere else. The permission is kept in your own browser, expires after 30 days, and you can withdraw it at any moment in Trello under Settings, then Applications. Card Approvals asks for no permission at all. Request Forms is different and is covered below.
Nothing changes without you seeing it first
An import or a sheet of edits is shown to you change by change, with the old value beside the new one, before anything is written. Afterwards the whole set can be undone with one button, and cards that were added are archived, not deleted.
Approvals that cannot be forged
Every approval request and decision is signed. Trello vouches for who made it, our service countersigns it, and the signature is checked in your browser every time the card is shown. An approval that has been altered, or copied onto another card, shows as not verified.
Payments
Stripe takes the payment on its own pages. Your card number never reaches our server and we cannot see it. A workspace admin can change the card or cancel from inside the Power-Up, and cancelling takes effect at the end of the month already paid for.
The site itself
- Everything is served over HTTPS only, from Cloudflare's network.
- The pages carry a strict content security policy, so they can only load code from this site and from Trello.
- The security headers score A+ on the independent scanner at securityheaders.com. Follow the link to run the scan yourself.
- No cookies, no analytics and no advertising scripts. Even the fonts are served from this site, so visiting it tells no third party.
Checked before listing
Trello checks every Power-Up before it can appear in the Trello directory, including its security headers and its privacy policy. Spreadsheet Importer has been through that check and is listed in the directory. Card Approvals, Bulk Edit Sheet and Request Forms are going through it now. A listing is not an endorsement: these Power-Ups are independent of Atlassian.
If something goes wrong
Every screen has a "Get support details" box. It produces a short report with your browser, the board's id and the last error, and nothing from your cards, for you to send if you choose to. Emails to support@stumason.dev are read by the developer who built these Power-Ups.
Reporting a security problem
If you think you have found a weakness, please write to support@stumason.dev with "Security" in the subject. You will get a reply from a person, and credit if you would like it.
Who is behind this
These Power-Ups are made and supported by Stu Mason, an independent software developer in the United Kingdom. They are not made or endorsed by Atlassian. The full legal detail is in the privacy policy and the terms.