ManageXR only collects data necessary to provide our device management services to your organization. There are 2 primary types of data that we collect:
Data about your devices: this technical data and usage data is used to help you manage and track your devices on our platform.
Data that you store on our services: this data includes things like apps and files that you want to distribute to your devices via our platform.
Additionally, we collect a small amount of personally identifying information (emails, names, etc.) so that an admin on an organization can log in and remotely manage the devices on our platform. We'll also use these emails and names to send out service notifications and announcements (which users can opt out of).
ManageXR never collects personal data about your end-users or customers (i.e. the people using an organization's VR headsets).
To learn more about our data collection policies, check our Data Processing Addendum.
ManageXR Data Map
The table below describes exactly what data ManageXR collects, when we collect it, why we collect it, how we store it, and when it is disposed of.
Source How is the data collected? | Data What data is collected? | Reason Why do we collect this data? | Handling How is this data stored? Who can access it? | Disposal When is the data disposed of? |
Demo Sign Up (Website contact form) | - Name - Organization Name - Organization Details (# devices, type of device used) | This is how we take new business inquiries and start conversations to sign up new users. | This data is stored in GSuite and HubSpot, and is encrypted in transit and at rest. Data is accessible by our Sales / Marketing team. |
Upon Request |
User Sign up |
- Name - Organization Name |
This data is used to initialize a new organization and admin account on our platform. | Data is stored in our database: Google Firestore. Data is encrypted in transit and at rest. Data is accessible by the owning organization and the ManageXR Technical Support / Sales / Marketing Teams. |
30 days after account deletion or request. |
User Creation |
- Name - Other non-PII |
This data is used to initialize a new ManageXR user account. These users may also sign up for email announcements/ notifications about our services. | Data is stored in our database: Google Firestore. Data is encrypted in transit and at rest. Data is accessible by the owning organization and the ManageXR Technical Support / Sales / Marketing Teams. |
30 days after account deletion or request. |
Device Registration/ Sync | Device data, including: - Serial Number - MAC address -Manufacturer - Model - IP Location - Current WiFi Network Name - Current Foreground App - Available Storage - Current RAM Usage - Battery Level - All installed apps and versions - OS version - Firmware version |
This data is used to help an organization track their device and display the current device state in the ManageXR web console.
|
Data is stored in our databases: Google Firestore and Cloud SQL.
|
30 days after account deletion or request. |
Device Usage Analytics |
- Current app identifier - Duration app was used - Device serial number |
This data is used to help an organization track their device usage. | Data is stored in Google Analytics and Google BigQuery. Data is encrypted in transit and at rest. Data is accessible by the owning organization and the ManageXR Technical Support Team. |
30 days after account deletion or request. |
App Upload |
- Application APK and OBB files
App details: - name - package name - description - version - categories - and other non-PII |
This data is used to distribute and install apps on an organization's devices. | Data is stored in Google Firestore and a Google Storage Bucket. Data is encrypted in transit and at rest. Data is accessible by the owning organization. The ManageXR Technical Support Team may access this data if requested by end user to assist in a support request. |
30 days after account deletion or request. |
File Upload
|
- File
File Details: - name - description - file type | This data is used to distribute files to an organization's devices. These files range from app icon images, branding images, and any generic file an organization would like to distribute to their devices (videos, assets, configuration files, etc). | Data is stored in Google Firestore and a Google Storage Bucket Data is encrypted in transit and at rest. Data is accessible by the owning organization. ManageXR Technical Support Team may access this data if requested by the end user to assist in a support request. |
30 days after account deletion or request. |
Device Error Handling |
- Device serial number - Device error details - Other non-PII |
This data is used to help the ManageXR team track app crashes and errors. | Data is collected and stored using Firebase Crashlytics. Data is encrypted in transit and at rest. Data is accessible by the ManageXR Tech Team. |
After 90 days. |
Website Error Handling |
- User email - IP address - Web app error details - Other non-PII |
This data is used to help the ManageXR team track app crashes and errors. | Data is collected and stored using Sentry. Data is encrypted in transit and at rest. Data is accessible by the ManageXR Tech Team. |
After 90 days. |
Device Setup Tool Error Handling |
- User identifier - IP address - Device Setup Tool error details - Other non-PII |
This data is used to help the ManageXR team track app crashes and errors. | Data is collected and stored using Sentry. Data is encrypted in transit and at rest. Data is accessible by the ManageXR Tech Team. |
After 90 days. |
Mighty Launcher Error Handling |
- User identifier - Mighty Launcher error details - Other non-PII |
This data is used to help the ManageXR team track app crashes and errors. | Data is collected and stored using Sentry. Data is encrypted in transit and at rest. Data is accessible by the ManageXR Tech Team. |
After 90 days. |
Need more help?
Talk to a member of our team using the chat bubble (in the bottom right of your screen), or reach out to support@managexr.com