Below you'll find our answers to the following questionnaire curated by Google for SDK providers.
Fullstory for Mobile Apps
|
Fullstory’s groundbreaking platform helps you deliver stand-out mobile experiences while respecting end-user privacy.
|
Data type SDK accesses and collects
|
For each data type listed:
- Describe required (or automatic) data access versus optional access. “Optional” includes the ability for a user to opt into or opt out of data collection.
- IP address
- Device type
- App name
- App version
- Fullstory for Mobile Apps SDK version
- Device model
- Device manufacturer
- Platform
- OS version
- Display type
- Screen size
- User taps and gestures
Customers may choose to provide consent dialogs allowing end-users to opt-out of Fullstory. Additionally, Fullstory for Mobile Apps does not screenshot or video record any user activity.
- Does SDK transmit this data off the device ?
- Yes, on average, one minute of session replay is ~20kB of information with caching. Please see this article for more detail on Fullstory for Mobile Apps performance.
- Describe purposes of collection and subsequent sharing and use.
- Fullstory collects Usage Data and Diagnostics. For further information on our privacy policy, please see this article.
- Does SDK transfer data to other third parties, including other apps on the user’s device? Describe the purposes for this sharing.
|
App level notes [complete section for any data collected or shared]
|
- Does your SDK encrypt data in transit?
- Yes, Fullstory for Mobile Apps uses Transport Layer Security Protocol
- Can the app developer and/or users request to delete user data collected?
|