Docs / Reference / Widget Data and GDPR

Widget Data and GDPR

When you embed FeedBlox on a customer website, that customer is the controller for visitor submissions. FeedBlox acts as the processor and only handles that data to provide the service.

What We Capture

Sentiment or numeric rating, optional comment, optional visitor email when enabled, and optional extra field answer you configure
Page URL at submit time, user-agent string, and submitter IP address (for abuse prevention)
Viewport size on each element-trail event
Structural element trail (hashed fingerprints of recent clicks; no DOM text or button labels)
Bounded client debug: recent console lines, failed fetch and XHR, uncaught JS errors, optional metadata from FeedBlox.setMetadata
Screenshots or recordings only when the visitor explicitly captures them (Pro and Max)

A FeedBlox report showing what was captured: the comment, page URL, browser user agent, and client debug — What a captured report looks like in the dashboard. Sample data.

What We Do Not Capture

Tracking cookies or cross-site identifiers on visitors
Full-page session replay or keystroke logging outside the widget panel
Request or response bodies for network calls
Query strings on captured network URLs (stripped before storage)

Your Duties as a Site Owner

Tell visitors what you collect and why.
Have a lawful basis for processing visitor feedback and debug data.
Use FeedBlox.setMetadata only for fields you are allowed to share.
Avoid logging passwords or tokens to the browser console on pages where the widget runs.