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.
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, swipe, pan), their network requests (request header and body, response header and body), system events (app status changes), view controller changes (the user navigating your app), push notifications that arrive, custom logs and application console logs. Shake SDK automatically deletes as much PII as possible on the mobile device itself. It also gives you additional methods to manage, delete and obfuscate any potential PII on the mobile device itself before anything is sent to Shake servers. | |
| Advertising data | Not collected. | |
| Other usage data | Not collected. | |
| Crash data | Shake's Crash reporting module. You can disable it. | |
| Performance data | Shake's Black box can show you the last 60 seconds of device memory usage, your app memory usage, network connectivity changes, device orientation and the CPU levels. You can also disable it. | |
| Other diagnostic data | Collected. | |
| Screenshot | A screenshot of the user's screen at the moment Shake is invoked. You can avoid capturing PII on the screenshot by marking sensitive views as private. In the case of manual invocation, your users can additionally blur or delete the screenshot before submitting the ticket. | |
| Screen recording | Automatically-captured video of what the user did in your app during the last 15 seconds prior to submitting a ticket. It's disabled by default. If you enable it, your users will be asked to allow screen recording first and will have the ability to delete it before submitting the ticket too. Shake doesn't record other apps' content — just yours. Use this optional feature only during internal testing. | |
| 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. If you decide you don't want to collect this data, you can hide this field. | |
| 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 | Whether or not the user had to somehow unlock the device to use it, with Touch ID for example. | |
| 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 | You can send yourself a value of any variable from your app. Use this feature safely and respectfully. | |
| Custom files | You can prepare and send to yourself any file that you want from your app. Use this feature safely and respectfully. |
Additional notes
You may receive PII if you don't use Shake carefully so please:
- Double-check additional files and data you attach to tickets.
- Openly disclose collected data with the regulating authority, such as the app store.
- Protect sensitive data to avoid capturing and sending PII to Shake servers.