App Data Usage
Data Usage Overview
Overview of data obtained via the toolstation mobile app and usage in relation to app store guidelines and privacy requirements. The app store requires that information about the app’s privacy practices, including the practices of third-party partners whose code is integrated into the app is provide on app store submissions and updates.
Toolstation App Data Types /Usage:
The following can be used to complete questions required for app store submission
| Data Types | Usage | App / SDK |
|---|---|---|
| Contact Info | App Functionality, Product Personalisation | App/API |
| Usage Data | Analytics, App Functionality, Product Personalisation | App/API, Third-Party: Firebase Crashlytics, Third-Party: Datadog |
| Diagnostics | Analytics, App Functionality | Third-Party: Firebase Crashlytics, Third-Party: Datadog |
| Identifiers | Analytics, App Functionality, Product Personalisation | App/API, Third-Party: Firebase Crashlytics, Third-Party: Datadog |
| Purchases | App Functionality, Product Personalisation | App/API |
- Note: Currently, the toolstation app is not required to request permission from users for tracking as the app does collect data that identifies users or a users device collected on apps, websites and other locations owned by third parties for the purposes of:
- targeted advertising or advertising measurement
- the information collected is shared with data broker
App Store Outlined Data Types and Usage Categories
Reference: https://developer.apple.com/app-store/app-privacy-details/
Types of data: Refer to the list of data types below and compare them to the data collection practices in your app.
| Contact Info | Description |
|---|---|
| Name | Such as first or last name |
| Email Address | Including but not limited to a hashed email address |
| Phone Number | Including but not limited to a hashed phone number |
| Physical Address | Such as home address, physical address, or mailing address |
| Other User Contact Info | Any other information that can be used to contact the user outside the app |
| Health & Fitness | |
| Health | Health and medical data, including but not limited to data from the Clinical Health Records API, HealthKit API, ovementDisorderAPIs, or health-related human subject research or any other user provided health or medical data |
| Fitness | Fitness and exercise data, including but not limited to the Motion and Fitness API |
| Financial Info | |
| Payment Info | Such as form of payment, payment card number, or bank account number. If your app uses a payment service, the payment information is entered outside your app, and you as the developer never have access to the payment information, it is not collected and does not need to be disclosed. |
| Credit Info | Such as credit score |
| Other Financial Info | Such as salary, income, assets, debts, or any other financial information |
| Location | |
| Precise Location | Information that describes the location of a user or device with the same or greater resolution as a latitude and longitude with three or more decimal places |
| Coarse Location | Information that describes the location of a user or device with lower resolution than a latitude and longitude with three or more decimal places, such as Approximate Location Services |
| Sensitive Info | |
| Sensitive Info | Such as racial or ethnic data, sexual orientation, pregnancy or childbirth information, disability, religious or philosophical beliefs, trade union membership, political opinion, genetic information, or biometric data |
| User Content | |
| Emails or Text Messages | Including subject line, sender, recipients, and contents of the email or message |
| Photos or Videos | The user’s photos or videos |
| Audio Data | The user’s voice or sound recordings |
| Gameplay Content | Such as saved games, multiplayer matching or gameplay logic, or user-generated content in-game |
| Customer Support | Data generated by the user during a customer support request |
| Other User Content | Any other user-generated content |
| Browsing History | |
| Browsing History | Information about content the user has viewed that is not part of the app, such as websites |
| Search History | |
| Search History | Information about searches performed in the app |
| Identifiers | |
| User ID | Such as screen name, handle, account ID, assigned user ID, customer number, or other user- or account-level ID that can be used to identify a particular user or account |
| Device ID | Such as the device’s advertising identifier, or other device-level ID |
| Purchases | |
| Purchase History | An account’s or individual’s purchases or purchase tendencies |
| Usage Data | |
| Product Interaction | Such as app launches, taps, clicks, scrolling information, music listening data, video views, saved place in a game, video, or song, or other information about how the user interacts with the app |
| Advertising Data | Such as information about the advertisements the user has seen |
| Other Usage Data | Any other data about user activity in the app |
| Diagnostics | |
| Crash Data | Such as crash logs |
| Performance Data | Such as launch time, hang rate, or energy use |
| Other Diagnostic Data | Any other data collected for the purposes of measuring technical diagnostics related to the app |
| Other Data | |
| Other Data Types | Any other data types not mentioned |
Data use
It would help if you had a clear understanding of how each data type is used by you and your third-party partners.
For example, collecting an email address and using it to authenticate the user and personalize the user’s experience within your app would include App Functionality and Product Personalization.
Purpose
| Term | Defination |
|---|---|
| Third-Party Advertising | Such as displaying third-party ads in your app, or sharing data with entities who display third-party ads |
| Developer’s Advertising or Marketing | Such as displaying first-party ads in your app, sending marketing communications directly to your users, or sharing data with entities who will display your ads |
| Analytics | Using data to evaluate user behavior, including to understand the effectiveness of existing product features, plan new features, or measure audience size or characteristics |
| Product Personalization | Customizing what the user sees, such as a list of recommended products, posts, or suggestions |
| App Functionality | Such as to authenticate the user, enable features, prevent fraud, implement security measures, ensure server up-time, minimize app crashes, improve scalability and performance, or perform customer support |
| Other Purposes | Any other purposes not listed |