Privacy
The feedback widget follows the same privacy approach as the tracker: no cookies for identification, minimal data, and explicit screenshot consent.
What is stored
Section titled “What is stored”| Data | When | Purpose |
|---|---|---|
| Rating, optional comment | Every submission | Review feedback |
Only if the visitor enters it or via usertrax.identify() | Follow-up / matching | |
| Page URL, title, referrer | Automatically | Submission context |
| Viewport, user agent, locale | Automatically | Device and language |
| Buffered JS errors | When present | Reproduce bugs |
| Optional screenshot (PNG) | Only after the visitor explicitly shares | Visual page context |
| IP address | Server-side | Abuse prevention (same as tracker) |
session_id | When a tracker session exists | Journey and channel context |
What is not stored
Section titled “What is not stored”- No tracking cookies and no local storage for identification by the widget itself
- No screenshot without user action — the browser shows the Screen Capture API share dialog
- No automatic recording of keystrokes, form fields, or passwords
Screenshot consent
Section titled “Screenshot consent”Screenshots use the browser Screen Capture API. The visitor must click Add a screenshot and share their tab. Cancelling the dialog submits feedback without an image.
Avoid showing sensitive data in the viewport on pages where the widget is embedded — a screenshot could capture it.
Cookie banners
Section titled “Cookie banners”For the cookieless feedback widget alone you typically do not need a cookie banner. It sets no cookies. Still review your full stack (analytics, ads, other scripts) and your counsel’s requirements.