Privacy notice
A plain-language summary of how Web Preview handles data. This is a pre-launch overview, not legal advice.
What the widget collects on customer sites
When a reviewer leaves feedback, the widget records the comment itself, the element it was pinned to (tag, CSS classes, and a stable selector), a screenshot of the page area around the pin, the page URL and title, viewport size, and browser and operating-system details. Console or network errors may be attached when they exist, to help with debugging.
Site visitors do not need an account and are not tracked across pages. If visitor chat is enabled, conversations are stored only when the visitor chooses to send a message.
Screenshots and redaction
Screenshots are taken at the browser, before upload. Input fields commonly holding sensitive data — passwords, card numbers, and form fields marked with privacy attributes — are masked in the image and excluded from the data payload.
Project owners can add their own privacy selectors, so any element they mark (for example a logged-in user's profile panel) is excluded from screenshots and diagnostics on every capture.
Consent controls
The feedback button itself only collects data when someone deliberately uses it. Features that collect more, such as screen recordings, are opt-in per project and will require a visible indicator while active. Customers remain responsible for the notices their own privacy law requires on their sites.
Data retention and your rights
Feedback history is kept per plan limits and delete interactions are soft deletions, so accidental threads can be recovered within the retention window. Accounts can request full export or permanent deletion of their data. Request handling workflows are being finalised before launch and will be documented here in full.