Privacy Policy

Feedback is a browser extension for leaving visual notes on webpages. A reviewer connects the extension to a specific Feedback project using a reviewer code. When the reviewer activates the toolbar on a page, the extension creates or opens a feedback session for that page. It does not monitor or transmit page activity while the toolbar is inactive.

In this policy, “workspace” means the Feedback project to which the reviewer code connects, and “workspace owner” means the person or organization that operates that project and decides how submitted feedback is used.

The extension handles the following information:

• Connection information: the reviewer code, server address, project identifier, and project name needed to connect the extension to the selected workspace.
• Page information: the full URL of a page on which you activate Feedback, including any query string or fragment contained in that URL.
• Content you submit: the note you write and, when applicable, text you intentionally have selected on the page.
• Annotation context: information needed to locate and describe the selected element, such as its label, CSS selector and classes, element path, nearby visible text, accessibility attributes, computed styles, page coordinates and size. On development websites, this can also include detected React component or source-file information.
• Basic operational records: timestamps, feedback status, session and annotation identifiers, and the project identity associated with a submission.

The extension does not collect your general browsing history. It does not collect webpage data until you activate the annotation toolbar, and it does not collect cookies, form passwords, financial information, health information, advertising identifiers, or screenshots.

We use the information above only to:

• authenticate the reviewer code and connect to the intended project;
• display the annotation toolbar on the page you choose;
• attach your feedback to the correct page and element;
• send, display, organize, update, and delete feedback in the workspace;
• allow authorized project members and configured tools to act on it; and
• maintain the security and reliability of the service.

We do not use extension data for advertising, credit decisions, or profiling, and we do not sell or rent it.

Submitted feedback is sent to the Feedback server identified by the extension’s configuration. It may be available to:

• the owner and authorized members of the workspace connected by your reviewer code;
• infrastructure providers that host the Feedback application and its database, acting on behalf of the service operator;
• agents, MCP clients, or webhook destinations deliberately configured by the workspace owner to process project feedback; and
• authorities or other parties when required by law, necessary to protect rights and safety, or involved in a business transfer subject to this policy.

The workspace owner controls its members and integrations. Ask the person who supplied your reviewer code if you need the exact list of providers or integrations used by that workspace.

• The reviewer code and project connection remain in Chrome’s local extension storage until you disconnect, clear the extension’s data, or uninstall it.
• A local browser copy of annotations and toolbar preferences may be stored for continuity. Locally cached annotations are filtered to the most recent seven days by the extension toolbar.
• Feedback sent to the server remains in the connected workspace until it is deleted by an authorized user or according to the workspace operator’s retention practices. Disconnecting the extension does not delete feedback already submitted to the server.

You can limit or remove extension data by:

• not activating Feedback on pages that contain sensitive information;
• removing sensitive values from a URL before activating the toolbar;
• avoiding selecting or including sensitive page text in a note;
• deleting individual annotations through Feedback where available;
• disconnecting the project in the extension; or
• uninstalling the extension or clearing its stored data in Chrome.

To request access to, correction of, or deletion of server-stored feedback, contact the owner of the workspace connected by your reviewer code. The workspace owner is responsible for responding to requests concerning its project data.

Reviewer codes are treated as credentials and should not be shared outside the intended project. Production connections should use HTTPS. We use reasonable technical and organizational measures designed to protect stored and transmitted data, but no system can guarantee absolute security.

We may update this policy when the extension’s features, data practices, or legal requirements change. The effective date at the top of this page will be updated when changes are published. Material changes will be communicated through an appropriate in-product or listing notice when required.

For questions about this policy or the extension operator’s privacy practices, use the publisher support contact shown on the extension’s Chrome Web Store listing. For a request about feedback stored in a particular workspace, contact that workspace’s owner.