Does Productboard require consent?

Conditionally. A cookie that prevents duplicate submissions may qualify as functionally necessary. However, cookies that build persistent user profiles across sessions and metadata collected about page context go beyond strict necessity and require consent under the ePrivacy Directive.

What data does Productboard's feedback widget collect?

Productboard captures user-submitted text, category selections, priority indicators, and file attachments, transmitting these to Productboard's servers. Scripts also collect page URL, user agent, and screen dimensions as contextual metadata to help product teams identify where feedback originates.

How does ConsentStack handle Productboard?

ConsentStack classifies Productboard as functional and applies conditional gating based on the implementation. Where the widget only handles explicit form submissions with session-only cookies, ConsentStack can allow it without consent. Persistent identification cookies trigger gating until consent is granted.

What tracker domains does Productboard use?

ConsentStack has catalogued tracker domains for Productboard including productboard.com. These are the network destinations Productboard's scripts contact, which a consent platform blocks until a visitor agrees.

Productboard - Feedback Widget Privacy Controls

Back to Vendor Library

Overview

Productboard provides product management teams with tools for collecting, organizing, and prioritizing customer feedback and feature requests. When embedded on websites or within application portals, Productboard's scripts power feedback widgets that allow end users to submit ideas, vote on features, and communicate product needs directly to the development team. These widgets serve as a bridge between customer-facing surfaces and the internal product roadmapping workflow.

The scripts are tightly scoped to the feedback collection use case and do not perform broad behavioral tracking or advertising functions. However, they do involve data transmission to Productboard's servers and may use cookies to manage the submission experience, which has privacy implications that website operators should evaluate.

What This Script Does

Productboard's client-side scripts enable feedback collection functionality on your website or application:

Feedback widget rendering: Scripts load an interactive widget — typically a slide-out panel or modal — where visitors or logged-in users can submit feature requests, bug reports, or general product feedback.
Form data collection: The widget captures user-submitted text, category selections, priority indicators, and any attached files, transmitting this data to Productboard's servers for processing.
Submitter identification: Cookies may be set to associate submissions with a user identity, prevent duplicate submissions from the same session, and maintain form state if a user navigates away and returns.
Portal integration: For public-facing feature voting portals, scripts manage the display of existing feature requests, vote counts, and status updates, fetching this data from Productboard's API.
Contextual data capture: Scripts may collect metadata about the page context (URL, user agent, screen dimensions) to help product teams understand where feedback originates.

The data collected is primarily user-initiated (explicit form submissions) rather than passively observed behavioral data, which distinguishes Productboard from analytics-oriented tools.

Consent & Compliance

Productboard's scripts primarily facilitate an explicit user action — submitting feedback — rather than passively tracking behavior. Under GDPR, the lawful basis for processing this data may be legitimate interest (providing a requested feedback mechanism) or consent, depending on the scope of data collected and how it is used within Productboard's platform.

If the widget sets cookies to identify users or persist session state, these cookies fall under the ePrivacy Directive's consent requirements unless they are strictly necessary for the feedback service. A cookie that prevents duplicate submissions could be argued as functionally necessary, while one that builds a persistent user profile across sessions would require consent.

Website operators should review what data Productboard collects beyond the explicit form submission and ensure their privacy policy discloses the third-party data processing relationship.

Should You Block This Without Consent?

Productboard's scripts provide functional value by enabling user-initiated feedback submission. The primary data flow is explicit (form submissions) rather than passive tracking. However, the cookies set for user identification and the metadata collection may extend beyond what is strictly necessary. Blocking the widget without consent is a cautious approach, but many implementations can be justified under legitimate interest given the user-initiated nature of the interaction.

Conditional.

Is Productboard GDPR compliant?

Productboard typically loads functional trackers, which are not strictly necessary for your site to work. Under the GDPR and the ePrivacy Directive, non-essential cookies and trackers must stay blocked until a visitor gives clear opt-in consent. So Productboard can be fully GDPR compliant, but only if your site holds its scripts until consent is granted and lets visitors decline just as easily. Compliance depends on how your site loads Productboard, not on Productboard itself.

Visit website