Data privacy disclosure
When users send you tickets, Shake "magically" and automatically captures a lot of other data, too. Although it feels like magic, it's not. We want you to fully understand and control it.
You're viewing the Chrome Extension docs. Other platforms → iOS Android React Native Flutter Web
Collected data
Data | Attributes and sensitivity | Description |
---|---|---|
Phone number | Not collected. | |
Name | Not collected. | |
Email address | Not collected. | |
Physical address | Not collected. | |
Other contact information | Not collected. | |
Health or fitness data | Not collected. | |
Payment, credit or other financial info | Not collected. | |
Precise or coarse location | Not collected. | |
Sensitive info | Not collected. | |
User's contacts, emails or text messages | Not collected. | |
Photos, videos or other user's files | Shake does not automatically collect the contents of the user Gallery or similar locations. However, keep in mind that your users can decide to attach any of their files by browsing their device themselves, and those files could contain PII. | |
Audio or gameplay data | Not collected. | |
Customer support or other user content | Not collected. | |
Browsing, purchase or search history | Not collected. | |
Device ID | Bundle identifier, DeviceID, platform and operating system. Not used for advertising. | |
Product interaction | Shake's Activity history shows a timeline of all user actions (every tap), their network requests (request header and body, response header and body), system events (app status changes), screen changes (the user navigating your app), custom logs and application console logs. Shake SDK automatically deletes as much PII as possible on the device itself. Activity histroy can be disabled in Chrome extension settings. | |
Advertising data | Not collected. | |
Other usage data | Not collected. | |
Crash data | Not collected. | |
Performance data | Not collected. | |
Other diagnostic data | Not collected. | |
Screenshot | A screenshot of the user's screen at the moment Shake is invoked. User can additionally blur or delete the screenshot before submitting the ticket. | |
Screen recording | User can attach screen recording if he wants, it's not attached automatically. | |
Permissions | A list of permissions the user has granted to your app. | |
User email | The user that's submitting a ticket enters this data themselves. | |
Time | A timestamp of the moment Shake was invoked. | |
OS | The operating system version of the user’s device. | |
Device | The user device model, Samsung Galaxy S8 for example. | |
App version | The build version of your app, 1.5.42 for example. | |
Network | The network connection type (WiFi, cellular or offline) and name. | |
Current view | The app screen on which Shake was invoked. | |
Timezone | The system settings timezone. | |
City and country | The city from which the ticket was sent. As with any network header on the Internet — that's how the Internet works — Shake SDK's header also contains the sender's IP address. Shake servers read only the request's city (nothing more geographically precise than that), saves that city name and never saves the IP address. Even though some don't consider the IP address PII, we choose to err on the side of caution and want to ensure everyone’s complete safety and security by not saving it. | |
Locale | The system settings locale, en-US for example. | |
Battery status | The battery percentage and whether the device was being charged at that moment. | |
Your app memory usage | How much memory your app was using. | |
Used storage | How much storage is still available on the user's device. | |
Authentication to unlock device | Not collected. | |
Resolution | The screen width ✕ height in pixels. | |
Orientation | The device orientation at the moment when the feedback was submitted, landscape for example. | |
Density | The screen pixel density, XHDPI for example. | |
Shake SDK | The version of Shake SDK that was used to submit the ticket. | |
Metadata | Not collected. | |
Custom files | Not collected. |