Privacy and Data Collection

What FrictaSolv Collects

• ✓Page path, timestamp, browser, operating system, and anonymous session ID
• ✓Counts of rage clicks, dead clicks, failed requests, JavaScript errors, slow loads, and navigation loops
• ✓Failed request method, URL path, and status code
• ✓Console error messages truncated for dashboard diagnosis
• ✓Optional screenshots when the configured frustration threshold is reached

Customer Controls

• ✓Screenshot capture can be disabled by setting the auto-snapshot threshold to 0
• ✓Ignore rules can silence noisy endpoints or expected errors
• ✓Retention can be configured from the organization settings
• ✓The SDK can be removed anytime by deleting the tag from GTM, theme code, or the site template

Sensitive Data

Do not intentionally send passwords, payment card numbers, authentication tokens, or private customer content to FrictaSolv. Teams should use ignore rules and screenshot controls for pages that may contain sensitive information.

Data Retention

Frustration events are retained for a bounded window set by your plan (free tier: 7 days; paid plans longer, configurable in organization settings). Opt-in screenshots are stored in Cloudflare R2 and purged on a separate, shorter schedule tied to your plan's replay retention (as short as 1 day). Once a screenshot passes that window it is permanently deleted from R2 while the underlying event and its aggregates are kept.

Sub-processors

We act as a processor for the data you send us and engage a small set of sub-processors to run the service. See the current list and our change-notification policy on the sub-processors page.

Your data rights (access & erasure)

For any site using FrictaSolv, the site operator is the controller of the data and you should send access or deletion requests to them. As their processor, we provide an org-scoped API so operators can export or permanently erase a visitor's data (including screenshots) on request. Erasure is a hard delete across our systems, not anonymization.