Privacy Policy for Trello Agent Context

Last updated: March 24, 2026

Summary: Trello Agent Context does not send your Trello data, captured traffic, or exports to servers operated by the extension authors. Processing happens in your browser. Optional features may store settings on your device or repeat network requests you explicitly choose, as described below.

1. What this extension is

Trello Agent Context is a Chromium extension that adds a Chrome DevTools panel. When DevTools is open on a tab, the extension observes that tab’s network activity (via DevTools APIs), keeps responses whose URLs match an allowlist of Trello-related hosts, parses them locally, and helps you view and copy structured card information as Markdown or JSON. It is intended for people who already use Trello in the browser with their normal login.

2. Data the extension authors do not collect

The publishers of this extension do not operate a backend for this tool and do not receive:

Your Trello card content, board data, or exports
Analytics, crash reports, or usage telemetry from the extension
Your passwords or session tokens sent to us

There is no account sign-up for the extension and no remote “phone home” for captured data.

3. What happens on your device

Network capture: Matching request and response data are processed in memory inside the DevTools panel while you use it. Retention limits you configure in the panel apply to that local capture (older entries may be discarded).
Settings: Preferences such as theme, retention limits, and related options are stored locally in your browser (for example via IndexedDB and local storage APIs exposed to extension pages).
Clipboard: When you use copy or export actions, the browser places content on your clipboard or in a download flow you control. That is standard browser behavior and is not sent to the extension authors.

4. Optional request replay

If you use a feature that re-runs a captured HTTP request, the extension’s background context may issue a fetch to the Trello URL you selected (only trello.com and *.trello.com, including api.trello.com). That uses your browser’s normal rules for that origin (such as cookies where the browser allows). Those requests are between your browser and Trello, not to servers run by the extension authors.

5. Permissions (as declared in the extension manifest)

DevTools page: Registers the “Trello Agent Context” panel next to other DevTools tools.
Host permissions (trello.com and *.trello.com): Declared so the background script can perform the optional replay fetch only to those Trello origins, matching the same hosts the extension uses for capture. The extension does not use this to upload captured data to the authors.
Background service worker: Handles extension messaging needed for optional replay and standard extension lifecycle events.

6. Third-party services you already use

When you load Trello in a tab, Trello and Atlassian (and their infrastructure) handle authentication and API responses under their own terms and privacy policies. This extension only reads responses the page flow already triggered, and does not replace or bypass Trello’s own controls.

7. Children’s privacy

The extension is not directed at children. It does not knowingly collect personal information for the authors. Parents and organizations remain responsible for how minors use Trello and the browser.

8. Changes

This policy may be updated when behavior or permissions change. The “Last updated” date at the top will be revised accordingly.

9. Contact

Questions about this policy or the extension: use the repository or support channel distributed with the extension, or email denniskinuthiawaweru@gmail.com.