Login
Sign up

Last Updated: June 16, 2026

Effective Date: June 16, 2026

Operating Entity: Minovox Ed Tech Pvt. Ltd. (operating as “Encity”)

Platform Scope: Encity Mobile Application (Google Play Store Ecosystem)

1.0 TRANSPARENCY & GOOGLE PLAY COMPLIANCE

To deliver an optimal, fully functional, and secure hyper-local marketplace experience, the Encity mobile application requires access to specific hardware and software permissions on your Android device.

In strict compliance with the Google Play Store Developer Programme Policies on Permissions and Malicious Behavior, Minovox Ed Tech Pvt. Ltd. maintains a policy of absolute transparency. This disclosure document outlines exactly what device permissions we request, when they are triggered, and why they are necessary.

We do not engage in silent, unauthorized data mining, nor do we access device capabilities that are irrelevant to our hyper-local search directory and service booking functionalities.

2.0 DETAILED HARDWARE & SOFTWARE PERMISSIONS INDEX

2.1 Precise Location Permissions (ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION)

  • Operational Context: Foreground & Contextual Location Access.
  • Why It Is Required: Encity is a location-centric discovery platform. This permission allows the app to detect your precise physical coordinates to instantly map out and display independent Service Providers (such as plumbers, electricians, or consultants) closest to your real-time position.
  • User Autonomy: You can opt to grant access “Only while using the app” or input a physical location manually. For Service Providers who opt in, approximate or precise location data may be used to calculate route distances for dispatched customer service calls.

2.2 Storage and Media Access (READ_EXTERNAL_STORAGE / READ_MEDIA_IMAGES)

  • Operational Context: Photo and File Selection.
  • Why It Is Required: This permission allows users to browse their device gallery to select and upload media files to the Platform.
  • Core Use Cases:
    • End-Users: Uploading a profile picture or attaching photo evidence of a home repair problem to a service booking or public review.
    • Service Providers: Uploading business logos, professional trade certificates, and images of past projects to build their digital storefront portfolio.

2.3 Camera Access (CAMERA)

  • Operational Context: Direct Image Capture.
  • Why It Is Required: This allows the Encity app to launch your device’s native camera application.
  • Core Use Cases: Capturing a live photo of a faulty appliance to clarify an in-app service request, or photographing mandatory government identity cards during the Service Provider onboarding and verification process.

2.4 Push Notifications (POST_NOTIFICATIONS)

  • Operational Context: System & Transaction Alerts.
  • Why It Is Required: Required on modern Android operating systems to push real-time updates directly to your device status bar.
  • Core Use Cases: Sending immediate alerts regarding your booking confirmation, real-time arrival updates from an assigned technician, customer inquiry alerts for providers, and critical security validation codes.

3.0 MANAGEMENT AND REVOCATION OF PERMISSIONS

You retain complete, autonomous control over your device data at all times. You can modify, restrict, or entirely revoke any of the permissions granted to the Encity application by navigating through your Android operating system settings:

  1. Open your device Settings.
  2. Tap on Apps or Application Manager.
  3. Locate and select Encity.
  4. Tap on Permissions.
  5. Select the specific permission you wish to amend (e.g., Location or Camera) and toggle it to Don’t Allow or Ask Every Time.

Operational Note: If you choose to revoke certain core permissions, such as location services, the Encity application will remain accessible, but its ability to automatically display proximate service options or map distances will be restricted, requiring manual address entry.

4.0 SECURITY & THIRD-PARTY PERMISSION RESTRICTIONS

Data compiled through these device permissions is encrypted in transit using Secure Socket Layer (SSL/TLS 1.3) protocols and is safely stored within firewalled cloud architectures. Encity does not sell, trade, or share device data harvested via these permissions with third-party advertising brokers. Access is restricted strictly to facilitating marketplace functions, processing payments, and generating platform performance metrics.