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 Developer Console Architecture
1.0 PURPOSE & GOOGLE PLAY DECLARATION FRAMEWORK
This document provides a highly structured, precise map of the data collection, data sharing, and security configurations implemented within the Encity mobile application. It is constructed to match the strict declarative options required within the Google Play Console Data Safety Form.
In alignment with Google’s Developer Program Policies, Minovox Ed Tech Pvt. Ltd. certifies that the technical disclosures listed below accurately reflect the current production architecture of the Encity Android application.
2.0 SUMMARY OF GOOGLE PLAY DECLARATION ATTRIBUTES
- Data Encryption in Transit: YES. All user data collected by the application is securely transmitted from the client mobile device to our API endpoints using industry-standard Transport Layer Security (HTTPS/TLS 1.3) encryption protocol.
- Data Deletion Mechanism Provided: YES. The application provides an explicit, frictionless in-app account deletion pathway under Profile Settings, allowing users to request the permanent erasure of their personal information.
- Data Sharing: YES. Data sharing occurs exclusively to facilitate hyper-local service operations (e.g., sharing a customer’s address with an assigned service provider) and to process payments through secure gateways. We do not sell data to third-party ad brokers.
3.0 DATA TYPES EXTRACTED, PURPOSES, AND SHARING BEHAVIOR
The table below outlines the exact classifications you must check when finalizing the Data Safety questionnaire in the Google Play Console:
| Google Play Data Category | Specific Data Field | Data Collection Status | Data Sharing Status | Explicit Purpose for Processing |
| Location | Precise Location (ACCESS_FINE_LOCATION) | Collected (Foreground & Background if enabled) | Shared (Passed to designated local providers) | App functionality, hyper-local search discovery, distance mapping, and routing. |
| Location | Approximate Location (ACCESS_COARSE_LOCATION) | Collected | Shared | Regional service mapping and localized discovery filter optimizations. |
| Personal Info | Name | Collected | Shared | Account management, profile creation, and peer-to-peer identification. |
| Personal Info | Email Address | Collected | Not Shared | Account authentication, security alerts, and system support communications. |
| Personal Info | User IDs (Account Token) | Collected | Not Shared | App functionality and unique database synchronization. |
| Personal Info | Phone Number | Collected | Shared (With booking counterparties) | OTP authentication, verification, and facilitating direct contact between users and providers. |
| Personal Info | Physical Address | Collected | Shared (With booking counterparties) | Delivering on-site services (e.g., plumbing, electrical) to the user’s home or office. |
| Financial Info | User Payment Info / Purchase History | Collected (Processed via SDK) | Shared (With PCI-DSS gateway) | Processing payments, managing subscription renewals, and tracking transaction history. |
| Photos & Videos | Photos / Media Files | Collected (User-initiated uploads) | Shared (Visible on public listings) | Constructing profile avatars, uploading portfolios, and attaching images to local reviews. |
| App Info & Performance | Crash Logs | Collected (Via Firebase SDK) | Shared (With analytics vendor) | App diagnostics, performance optimization, and identifying system software bugs. |
| Device or Other IDs | Android ID / Advertising ID (GAID) | Collected | Shared (For diagnostics/security) | Fraud prevention, device authentication, and system security monitoring. |
4.0 CORE DECLARATION FIELDS FOR CONSOLE INPUT
4.1 Data Collection Declaration
“Our application explicitly collects specified personal data, device identifiers, and geolocation variables. All collected items are directly tied to the primary execution of our hyper-local marketplace service, user registration, and secure platform operations.”
4.2 Data Sharing Declaration
“Encity only shares user data with third parties to facilitate core transactional operations. Specifically, name, contact number, and service address are shared with the service provider assigned to an user’s request. Financial transaction variables are securely handled by PCI-DSS compliant processors (Razorpay/Stripe). We do not share data with third-party tracking networks for independent monetization or data broker operations.”
4.3 Security Practices Declaration
“All data transmitted out of the Encity mobile ecosystem is wrapped in an encrypted transport layer (TLS/HTTPS). We provide an accessible data deletion mechanism both in-app and via our web portal, ensuring users can permanently purge their personal data footprints within 30 days of request submission.”