Google Play Policy Puresect Security (Android) Effective: October 22, 2026

Security App Privacy Policy

This Privacy Policy explains how ZLTS LLP collects, manages, and safeguards data processed by the PureSect Security gate terminal Android application used by security personnel.

Scope of this Policy

This document covers only the guard-app (gate terminal). It does not cover the personal staff-app used by housekeeping, maintenance, and other staff, or the committee-app used by society administrators, which have their own respective policies. The guard-app does not collect, handle, or display any salary, wage, or payroll information for security personnel or anyone else.

1. Introduction & Scope

PureSect, a subsidiary of ZLTS LLP ("PureSect", "we", "us", "our"), provides the guard-app to Housing Societies, Commercial Complexes, and Organizations ("Society") so that authorized security personnel can manage entry, exit, visitor authentication, vehicle access, automated IoT/biometric device synchronizations, and emergency response at the Society's gates.

The application infrastructure and databases are hosted on Utho Platforms Private Limited ("Utho Cloud"), providing sovereign Indian cloud infrastructure, high availability, and compliance with national data localization mandates.

The guard-app operates in kiosk mode on tablets or rugged mobile devices mounted at society gates, interfacing both directly with guards on duty and through IoT integrations with external hardware (e.g., biometric fingerprint readers, facial recognition terminals, RFID boom barriers, and hardware QR/barcode scanners).

Because it processes information about several categories of data subjects, this Policy addresses each group separately:

  1. Security Guards / Personnel who log in and operate the app or check in via IoT biometric readers.

  2. Visitors and Delivery Personnel checked in at the gate or through self-service IoT scanning kiosks.

  3. Society Staff & Service Personnel whose QR badges, RFID cards, or biometric templates are scanned for gate attendance and in/out logging.

  4. Residents contacted for visitor pre-approvals, delivery confirmations, or IoT gate pass validations.

  5. Vehicles entering or exiting the premises via ANPR, RFID, or barrier sensor triggers.

By operating the guard-app, or by entering a Society that utilizes the PureSect platform and its connected IoT infrastructure, the relevant person (or the Society acting on their behalf as the Data Fiduciary) acknowledges the privacy practices described herein.

2. Definitions

Term Meaning
Society / Organization The residential complex, housing cooperative, apartment owners' association, or commercial property operating PureSect, identified in the system by a contextId and contextType.
Society Management Committee The elected or appointed governing body responsible for society administration and security oversight (Data Fiduciary under the DPDP Act, 2023).
Security Agency The licensed private security agency (under the Private Security Agencies (Regulation) Act, 2005 / PSARA 2025) that employs and deploys security guards to the Society.
Security Guard / Personnel A guard deployed by the Security Agency who operates the guard-app gate terminal on duty.
Visitor Any guest, delivery executive, service provider, or cab driver requesting entry to the Society.
IoT / Hardware Integrations External connected devices including standalone USB/Bluetooth/IP QR scanners, biometric fingerprint/facial recognition terminals, smart turnstiles, and automated boom barriers connected to the guard-app via IoT gateways or local APIs.
Gate Log The digital ledger of entry and exit events at a gate, including visitor, vehicle, staff attendance, IoT biometric verification logs, and SOS alerts.
ANPR / RFID Automatic Number Plate Recognition and Radio-Frequency Identification used for automated vehicle entry and boom barrier operations.
Cloud Infrastructure Provider Utho Platforms Pvt. Ltd. ("Utho Cloud"), providing enterprise sovereign cloud hosting within Tier III/IV data centers in India.

3. Information We Collect

3.1 Security Guards / Personnel (App Operators)

  • Name, mobile number, and photo registered on the guard's official QR identity badge or biometric profile.
  • Employing Security Agency details, assigned gate ID, and shift schedules.
  • Login credentials, JWT authentication tokens, role configurations, and permission metadata.
  • Gate duty attendance: Duty check-in/check-out timestamps recorded via QR badge scan, app login, or connected IoT biometric hardware terminals.
  • Immutable audit trail: Log of administrative actions performed within the app (e.g., which guard approved or denied an entry, overridden an IoT gate trigger, or raised an SOS alert).

3.2 Visitors and Delivery Personnel

  • Name and mobile number.
  • Purpose of visit, host resident name, and flat/unit number.
  • One-Time Password (OTP) verification status or pre-approval QR code validations processed via app camera or external hardware QR scanners.
  • Timestamp of entry and exit, gate identifier, and delivery service provider name (e.g., e-commerce, food delivery platforms).
  • Visitor photograph captured via gate camera terminal or integrated self-service visitor kiosk (where enabled by Society policy).

3.3 Vehicles

  • Vehicle registration number (entered manually or captured via ANPR camera).
  • Number plate captured images processed by ANPR modules (where installed).
  • RFID tag identifiers associated with registered resident or staff vehicles for automated IoT boom barrier access.
  • Vehicle entry/exit timestamps and gate location.

3.4 Society Staff Attendance & In/Out Scans (Hardware & IoT Biometrics)

When a domestic worker or staff member checks in or out at the gate:

  • Scanner / QR Entry: Scanned via device camera or connected external USB/Bluetooth/IP hardware QR scanner, logging staff ID, timestamp, and gate ID.
  • IoT & Biometric Hardware Integration: Where the Society installs external biometric terminals (e.g., fingerprint scanners, facial recognition devices, smart turnstiles), attendance and in/out events are transmitted via local local-area-network (LAN) or cloud IoT APIs to the guard-app.
  • Biometric Data Handling: Biometric hardware devices generate mathematical encrypted vector hashes (templates) locally on the device hardware or dedicated edge controller. PureSect servers do not store raw, reconstructable biological fingerprint images or facial photographs for biometric matching. Only the resulting verified User ID, verification status (Success/Failure), timestamp, and gate location are logged into the central PureSect database.

3.5 Emergency (SOS) Alerts

When a guard triggers an Emergency SOS alert manually or an IoT sensor trigger (e.g., panic button, barrier breach sensor) is activated, the app records the alert event, timestamp, gate location, and initiating account/sensor ID. The alert is immediately broadcasted to configured committee members, residents, and security supervisors.

3.6 Device & Technical Data

  • Gate terminal hardware ID, model, Android OS version, app version, and connected IoT peripheral IDs (e.g., paired Bluetooth scanners, IP biometric reader MAC addresses).
  • Network diagnostic telemetry, API performance logs, and Firebase Cloud Messaging (FCM) tokens.

3.7 Information We Do Not Collect

The guard-app does not collect or process:

  • Salary, compensation, or payroll records for security guards or society staff.
  • Precise GPS background location tracking of guards.
  • Raw biological biometric templates (e.g., full unencrypted fingerprint bitmaps or high-res facial biometric point grids—these remain on edge hardware controllers).
  • Payment card, credit card, or banking credentials.

4. How We Use Information

PureSect processes gate data strictly for legitimate operational and security management purposes:

  1. Access Control & Property Security: Verifying, logging, and managing visitor, vendor, and vehicle movement to safeguard premises via app controls and connected IoT hardware.
  2. Automated Attendance & Entry/Exit Logging: Synchronizing staff, vendor, and guard attendance via external hardware scanners, QR readers, and integrated biometric terminals.
  3. Resident Notifications: Sending real-time push notifications and IVR/app alerts to residents for visitor verification, delivery approvals, and automated gate entries.
  4. Automated Barrier Operations: Validating pre-approved visitor QR passes, RFID tags, and verified biometric inputs to trigger automated boom barriers, turnstiles, and smart gates.
  5. Staff Duty & Shift Verification: Recording gate duty hours for security guards and attendance logs for housekeeping/domestic staff across all entry channels.
  6. Emergency Response: Generating immediate broadcast alerts during gate incidents, SOS emergencies, or perimeter security breaches.
  7. Incident Audit & Investigation: Maintaining tamper-proof audit trails and Gate Logs for society safety reviews or official police inquiries.
  8. Infrastructure & App Stability: Ensuring application uptime, API connection reliability, and network diagnostic monitoring on Utho Cloud servers.

Zero Marketing Usage: Gate data and IoT log streams are never monetized, sold, leased, or utilized for targeted advertising.

6. Society Management Committee Rights & Fiduciary Duty

The Society Management Committee acts as the Data Fiduciary under the DPDP Act 2023 for all Gate Logs, IoT attendance entries, and operational visitor data generated at its premises. PureSect (a subsidiary of ZLTS LLP) acts as the Data Processor.

  • The Management Committee maintains administrative rights to view, audit, and download Gate Logs and attendance summaries for official society security purposes.
  • The Committee determines whether optional features—such as integrated IoT biometric readers, visitor photo capture, or ANPR cameras—are activated for their Society.
  • The Committee does not have access to guard salary or wage information, which is administered independently by the Security Agency outside PureSect.
  • Committee members are legally bound to prevent unauthorized sharing, commercial exploitation, or public disclosure of visitor, staff, and resident log details.

7. How We Share Information

Data processed by the guard-app and its connected peripherals is shared strictly on a need-to-know basis:

  • With Host Residents: Visitor name, photograph (if captured), vehicle number, and entry purpose are shared with the visited resident for authorization.
  • With Society Management: Gate Logs, staff attendance records (QR and biometric scan timestamps), and incident audit trails are accessible to authorized society office-bearers.
  • With Security Agencies: Duty check-in/check-out timestamps and gate assignment logs (including biometric guard check-ins) are accessible to the employing Security Agency for shift and workforce verification.
  • With Cloud Infrastructure Partner (Utho Platforms Pvt. Ltd.): Encrypted data storage and network traffic are hosted on Utho Cloud data centers in India.
  • With Parent Entity (ZLTS LLP): Internal data flow between PureSect systems and parent entity infrastructure for system maintenance, platform stability, and core operations.
  • Statutory & Law Enforcement Bodies: Disclosed to police or legal authorities when required by a valid legal order, court summons, or official security investigation.

8. Multi-Society Guard Operations

When a security guard works across multiple society locations managed by the same Security Agency:

  • Data is strictly compartmentalized by contextId.
  • Operational logs and biometric attendance entries from Society A are isolated and completely inaccessible to users or administrators of Society B.

9. Android Device Permissions & Rationale

The guard-app requests specific runtime permissions necessary to execute gate terminal operations and interface with connected hardware:

Permission Name Operational Purpose
android.permission.CAMERA Scanning QR badges for staff attendance, reading visitor OTP passes, and capturing visitor photos or vehicle license plates.
android.permission.BLUETOOTH / BLUETOOTH_CONNECT / BLUETOOTH_SCAN Pairing with external hardware barcode/QR scanners, handheld thermal printers, or local Bluetooth IoT gate controllers.
android.permission.ACCESS_FINE_LOCATION Required by Android OS for discovering nearby Bluetooth/IoT hardware devices connected to the gate terminal.
android.permission.POST_NOTIFICATIONS Receiving alerts for pre-approved guests, resident approvals, IoT hardware disconnect notices, and emergency SOS signals.
android.permission.INTERNET & ACCESS_NETWORK_STATE Maintaining secure communication with PureSect backend servers on Utho Cloud and local-network IP biometric terminals.
android.permission.CALL_PHONE / ACTION_DIAL Placing direct audio calls to host residents for gate entry confirmation when enabled.
android.permission.RECEIVE_BOOT_COMPLETED / FOREGROUND_SERVICE Ensuring the gate terminal automatically launches and operates continuously in dedicated Kiosk mode while maintaining background IoT device polling services.

10. Data Security & Sovereignty

  • Indian Data Localization: All databases, ANPR images, attendance logs, and gate activity archives are hosted exclusively within Indian data centers operated by Utho Platforms Pvt. Ltd.

  • Encryption Standards: Data in transit between gate terminals, connected IoT devices, and cloud servers is protected using HTTPS/TLS 1.3 encryption and secure local API tokens. Storage volumes are encrypted at rest using AES-256 standards.

  • Terminal & IoT Edge Security: The guard-app runs in locked Android Kiosk Mode on gate devices. Communication with connected biometric hardware terminals is restricted to authenticated local networks or encrypted gateway protocols to prevent tampering or spoofing.

11. Data Retention & Erasure Schedule

Data collected via the guard-app and connected IoT devices is retained according to society rules and statutory limits:

Data Type Retention Period
Visitor Logs & Photos 90 to 180 Days (Configured by Society policy; auto-purged thereafter).
ANPR Vehicle Logs & Images 90 Days (unless flagged for security review).
Staff Gate Attendance Logs (QR / IoT / Biometric Timestamps) 3 Years (Per applicable labor and attendance record guidelines).
Guard Duty Logs & Activity Trails 3 Years (For PSARA workforce compliance and shift audits).
Emergency SOS & Incident Logs 7 Years (Or until legal/police investigations are formally closed).
Device Diagnostics & IoT Telemetry 30 Days.

12. Data Principal Rights (DPDP Act 2023)

Visitors, staff members, residents, and security personnel have the right to:

  1. Request confirmation and a summary of personal data held in Gate Logs or IoT attendance ledgers.
  2. Request correction of inaccurate information.
  3. Seek erasure of personal data when operational and legal retention periods expire.
  4. Register a grievance regarding data handling or biometric registration choices.

Data rights requests regarding Gate Logs should be directed to the Society Management Committee (Data Fiduciary) or PureSect's Grievance Officer.

12A. Account & Data Deletion (Google Play Compliance)

Guard accounts are normally provisioned by the employing Security Agency or the Society. You may initiate deletion of your account and associated profile data through the self-service portal below, or ask your Security Agency or Society Administrator to deactivate the account.

Account & Data Deletion

Statutory Notice: Authentication credentials and profile data are deleted when the request is processed. Visitor logs, ANPR records, attendance logs, emergency logs, and other gate records that must be retained for security, labour, or statutory compliance are retained under Section 11 before deletion or anonymisation.

13. Children's Data Protection

The guard-app is operated exclusively by adult security personnel. Minor visitors entering the premises are not registered independently; their entry is indexed under the accompanying adult or host resident. PureSect does not knowingly collect personal data directly from children.

14. Changes to This Privacy Policy

This Policy may be updated periodically to reflect software updates, new IoT/biometric hardware integrations, infrastructure changes, or regulatory modifications. The "Last Updated" date indicates the latest revision.

15. Contact & Grievance Redressal

For questions, grievances, or data protection queries under the DPDP Act 2023, please contact our Grievance Officer:

Field Details
Company Legal Entity PureSect (A Subsidiary of ZLTS LLP)
Customer Care & Grievance Email care.puresect@zlts.org
Cloud Infrastructure Provider Utho Platforms Pvt. Ltd. (Sovereign Indian Cloud)
Registered Business Address FLAT NO L 4 304 BUILD N0 7 DHANYA SATIWALI NAKA, VASAI EAST, Vasai East IE, WALIV, Vasai, Thane- 401208, Maharashtra, India.

For inquiries regarding how a specific Society handles, configures, or audits its Gate Logs or integrated biometric/IoT devices, please contact that Society's Management Committee directly.

16. Governing Law & Jurisdiction

This Policy is governed by the laws of the Republic of India, including the Digital Personal Data Protection Act, 2023, the Information Technology Act, 2000, and PSARA guidelines. Any legal proceedings shall be subject to the exclusive jurisdiction of the competent courts in Thane / Mumbai, Maharashtra, India.