Privacy Overview

Sprig's entire application was built with Privacy as a top priority - including Replays.

By default, all secure form contents (including password fields) are not recorded or stored.

Additionally, users are able to hide specific mobile classes as they wish. Configure privacy settings at Settings > Replays > User privacy. Additionally, an Admin can turn off replays for the whole workspace, or by Product at Settings > Replay > Configure.

Mobile Replay Privacy

While a replay clip may look and feel like a screen recording, Sprig's Replay clips are not actual “screen” recordings but instead a visual presentation of the application UI as the user sees it. The Sprig SDK takes screenshots of the device screen and then reconstructs those into a video clip that can be played back.

This approach allows us to selectively capture data and UI elements, such as user interactions and form contents, while redacting other data, such as images and password fields.

By default, all secure form contents (including password fields) and on-screen keyboard interactions are not recorded or stored. Additionally, users are able to hide specific mobile classes as they wish. Configure privacy settings at Settings > Replays > User privacy. Additionally, an Admin can turn off replays for the whole workspace, or by Product at Settings > Replay > Configure.

Interactions

In addition to visual user behavior, Sprig Replays also captures user interactions, such as taps, swipes, and other gestures, providing a comprehensive view of the user experience. Interaction data, like touch coordinates and event timings, are recorded to understand user behavior.

Compliance

In adherence to guidelines set by the California Consumer Privacy Act (CCPA), Replays does not capture nor require capturing permissions from end-users. The CCPA mandates that businesses must disclose their practices related to both the collection and sale of consumers' personal information in their privacy policies. While businesses are required to give consumers the option to opt-out of having their personal information sold to third parties, the law does not oblige them to provide a similar opt-out for just the collection of personal information.

View more information on Sprig's Privacy Policy: here

We welcome feedback on our privacy practices. Please contact us at [email protected] if you have any questions or concerns.

Performance

Sprig Replays have been designed to use as little resources as possible. We break down performance into 4 categories: CPU, Memory, and Network.

CPU

We use a background thread job wherever possible to limit the CPU usage. The screen recording should have very little impact on your app's CPU consumption.

Max Memory

Session Replay data has near zero impact on memory usage for modern web applications. Sprig immediately moves any data to IndexedDB to keep memory usage low and to persist replay across page loads.

Network

Sprig uploads Replay data in one request as opposed to other solutions that upload small pieces frequently. This approach improves compression efficiency, reduces network overhead and reduces energy consumption for mobile devices. Sprig can upload Replay clips over WiFi or Cellular.