Google Play Compliance
Transparent disclosure of application purpose, permissions, and data usage for Google Play review.
Purpose of the Application
iShield Protector is an enterprise Android Device Management (MDM) platform agent. It enables businesses to securely manage, monitor, and control organization-owned or financed Android devices at scale.
Typical deployment scenarios include:
- EMI and loan financing companies managing financed Android devices provided to borrowers
- Enterprises managing employee-issued devices under a corporate device policy
- Kiosk operators locking devices to specific purpose-built applications
- Distributors managing device fleets across customer portfolios
- Educational institutions managing student tablets
- Healthcare organizations securing clinical Android devices
Required Permissions — Justification
Device Administrator & Device Owner APIs
Justification: iShield Protector is an enterprise Mobile Device Management (MDM) agent. Device Administrator and Device Owner privileges are required to enforce corporate device policies, manage app installations, apply lock task mode, and execute remote management commands. These APIs are the foundation of Android Enterprise management.
Actual Usage: Used exclusively for authorized enterprise device management operations as directed by the organization that enrolled the device.
Notifications & Foreground Services
Justification: A persistent foreground service notification is required to maintain the MDM agent active while the device is in use. This is a mandatory Android requirement for long-running background processes. The notification informs the device user that MDM management is active.
Actual Usage: Used to maintain the management agent active and to deliver device commands received from the management server.
Location Access
Justification: Location data is collected only when explicitly enabled by the organization managing the device. This is used for asset tracking of organization-owned devices and is disclosed to device users through the organization's acceptable use policy.
Actual Usage: Used only when location tracking is explicitly enabled by the managing organization. Not collected by default.
Storage Access
Justification: Storage access is required to support app sideloading operations performed by the managing organization, log file generation for diagnostic purposes, and policy configuration caching.
Actual Usage: Used for MDM agent operational data only. No personal files are accessed.
Network & Connectivity
Justification: Network access is required to communicate with the iShield Protector management server to receive commands, report device health, and maintain the MQTT heartbeat connection.
Actual Usage: Used exclusively for MDM server communication. All traffic is encrypted in transit.
Data Usage
Data Collected
Device identifiers (IMEI, serial, model)
Device health telemetry (battery, storage, connectivity)
Security and compliance events
Command execution logs
Location data (only when explicitly enabled)
Data NOT Collected
Personal messages or call logs
Photos or media files
Passwords or credentials
Browsing history
Personal contacts
Privacy Commitments
Enterprise Context Only
All device data belongs to and is accessible only by the managing organization. iShield Protector does not sell or share device data with third parties for advertising or analytics.
Encrypted in Transit
All communication between the MDM agent and the iShield Protector management server is encrypted using TLS 1.2+.
Device User Transparency
The persistent foreground notification informs device users that their device is under enterprise management at all times.
Data Retention
Device telemetry data is retained according to the organization's configured retention policy. Data is deleted upon device unenrollment or account termination.