Chrome extension that files annotated bug reports into Plane.so.
Last updated: 2026-05-19
Plane Bug Reporter (“the extension”) is a Chrome extension that lets a user capture an annotated screenshot of a web page and file a bug report into a Plane.so project of their choice. This page describes exactly what data the extension touches, where it goes, and what the developer can and cannot see.
The extension is maintained by Mapas Concepts B.V. (“we”, “us”). Contact: dev@maira.cloud.
We are the publisher of the extension. We are not the controller of the data that the extension transmits — that is the user’s own Plane.so workspace operator, which the user configures in the extension’s options page.
The extension processes the following data only on the user’s device and only at the moment the user clicks “Capture & annotate” or “Send to Plane”:
| Data | Source | Where it goes |
|---|---|---|
| Screenshot of the visible browser tab | chrome.tabs.captureVisibleTab |
Uploaded as an attachment to the issue the user creates in their own Plane.so workspace. |
| Page URL, page title, viewport size, user agent, timestamp | The active tab | Included in the issue description body the user submits to Plane.so. |
| Console log entries and uncaught errors (last 200, from the active tab only) | console.* and window.onerror hooks injected into the active tab |
Included in the issue description body the user submits to Plane.so. |
| Annotations the user draws on the screenshot | The user | Burned into the screenshot before upload. |
| Title, description, priority the user types into the form | The user | Sent to Plane.so as part of the issue. |
| Plane.so authentication credentials (OAuth tokens or API key) | The user pastes them once, or completes OAuth | Stored in chrome.storage.local on the user’s own device. Never transmitted anywhere except to the Plane.so API endpoints the user configured. |
The extension does not collect or transmit any of the above to any server
operated by Mapas Concepts. All requests go directly from the user’s browser to
the Plane.so endpoint that the user configured in the extension’s options
page (Plane Cloud api.plane.so by default; otherwise a self-hosted Plane
URL of the user’s choice).
Nothing. The extension makes no analytics, telemetry, or error-reporting calls back to Mapas Concepts. We do not operate any server the extension talks to. We cannot see which pages you capture, who you send issues to, or what your tokens are.
Anything you submit to Plane.so is governed by Plane.so’s own privacy policy and by the policies of the workspace operator who controls your Plane.so workspace. Read Plane’s policy: https://plane.so/legal/privacy.
The Chrome Web Store listing surfaces these permissions; here is the justification for each:
activeTab, tabs — read the current tab’s URL/title and capture its
visible pixels when the user clicks the action button.scripting — inject the console / error capture script into the
current tab on demand.storage — persist the user’s Plane.so settings and tokens in
chrome.storage.local on their own device.identity — open the Plane.so OAuth consent window via
chrome.identity.launchWebAuthFlow. Required only if the user picks the
OAuth auth mode.<all_urls> host permission — necessary because the user may file a
bug report from any web page. The extension only reads / captures the tab
the user is on when they explicitly click “Capture & annotate”. It does
not scan or track browsing in the background.https://api.plane.so/*, https://app.plane.so/* — destination of
the API calls the extension makes on behalf of the user.The extension is a developer tool. It is not directed at users under 16 and should not be installed by them.
If we change this policy, the new version will be posted at this URL with an updated “Last updated” date. Substantive changes will also be noted in the project CHANGELOG of the extension repository.
Questions about this policy or about data handling: dev@maira.cloud.