Legal Document · Internal Use Only

Privacy Policy

Employee Management Application — How we collect, process, store, and protect your personal information within our organization.

Version2.0
Last UpdatedMarch 2026
Applies ToAll Authorized Employees
Contactprasanna@citadelnetinc.com

This Privacy Policy ("Policy") governs how Citadel Net Inc. ("Company," "we," "us," or "our") collects, processes, stores, shares, and protects the personal information of authorized employees ("you," "user," or "employee") who access and use the internal Employee Management Application ("Application" or "App"). By accessing or using the Application, you acknowledge that you have read and understood this Policy. This document is intended to be transparent, comprehensive, and compliant with applicable data protection laws.

This Application is a closed, enterprise-only system. There is no public access, no self-registration, and no use of data for commercial purposes such as advertising. All data collection is strictly limited to what is necessary for the legitimate management of workforce operations.


01

Scope and Applicability

1.1 Who This Policy Covers

This Policy applies to all individuals who are granted access to the Application, including:

1.2 What This Policy Covers

This Policy governs the collection and processing of personal data by the Application across all supported platforms, including Android and iOS mobile applications, and any associated web interfaces or administrative dashboards. It covers data collected automatically (such as attendance records and device logs) as well as data submitted voluntarily by users (such as messages and uploaded images).

1.3 What This Policy Does Not Cover

This Policy does not cover:

No Public Access: This Application is strictly for internal organizational use. There is no public sign-up, trial access, or guest login. All accounts are created solely by authorized HR or Admin personnel.

02

Information We Collect

We collect only the minimum information necessary to operate the Application and manage workforce functions. Below is a detailed breakdown of each category of data collected, the specific fields involved, and the reasons for collection.

2.1 Account & Employment Information

When an HR or Admin officer creates an employee account, the following data is entered into the system:

2.2 Attendance Information

Attendance tracking is a core function of this Application. The following data is collected to record, validate, and audit attendance:

2.3 Messaging & Internal Communication Data

The Application includes internal messaging and module-based communication features. The following data may be collected:

2.4 Device & Technical Information

To ensure Application stability and compatibility, the following technical information is collected:

What We Do Not Collect: We do not collect contact lists, SMS history, browsing history, call logs, microphone audio, or any data unrelated to the Application's core workforce management functions. We do not use your data for advertising, profiling, or resale.

03

Location Data Usage

Location data is one of the more sensitive categories of personal data we collect. This section provides a complete and transparent explanation of how, when, and why location access is used.

3.1 Types of Location Access Requested

3.2 When Location Is Accessed

Location data is accessed only during the following defined scenarios:

Location is not accessed continuously, is not tracked in real time throughout the workday, and is not accessed outside the above-defined attendance windows.

3.3 Geofencing Explained

Geofencing is a virtual geographic boundary defined around a designated office or site location. When an attendance event is triggered, the Application compares the employee's current GPS coordinates to the defined geofence boundary:

3.4 Background Location Justification

Background location access is required because automated attendance attempts are designed to occur even when the Application is running in the background or has not been manually opened by the employee. Without background location access, the automatic attendance feature cannot function — requiring employees to manually open the Application at precise times to mark attendance, which is operationally impractical.

This permission is used narrowly and only during the scheduled windows described in Section 3.2. It is not used for live tracking, surveillance, or any purpose beyond automated attendance validation.

3.5 No Live Tracking or Movement Monitoring

We explicitly confirm: No live tracking is performed. The Application does not monitor or record the employee's movements throughout the day. Location is captured as a point-in-time reading during attendance events only, not as a continuous stream.

3.6 Storage of Location Data

ScenarioData StoredRetention
Employee within geofenceAttendance status only; coordinates not retainedIndefinite (attendance record)
Employee outside geofenceGPS coordinates, timestamp, validation status2 years
Failed attendance attemptTimestamp, error status, optional coordinates2 years
04

Biometric Authentication

The Application supports biometric authentication as a convenient and secure method for employees to log in. This section explains exactly how biometric data is handled.

4.1 Supported Biometric Methods

4.2 How Biometric Data Is Handled

The Application uses the device-native biometric authentication APIs provided by iOS (Face ID / Touch ID via LocalAuthentication framework) and Android (BiometricPrompt API). These APIs work entirely within the operating system's secure enclave:

Your biometric data never leaves your device. Our servers have no capability to store, access, or process fingerprint or facial recognition data. Authentication happens entirely between you and your device's operating system.

4.3 Enabling and Disabling Biometric Login

Biometric authentication is optional. Employees can choose to enable or disable this feature within the Application's settings at any time. Disabling biometric login does not affect access to the Application — employees can continue to log in using their email and password credentials.

05

Camera Usage

5.1 When Camera Access Is Used

Camera access is requested exclusively for the following purposes:

5.2 What Camera Is NOT Used For

The camera is not used for attendance verification, facial recognition, or any form of biometric identification. There is no "selfie check-in" or photo-based attendance feature.

5.3 Storage of Images

5.4 Image Upload Consent

By uploading an image through the Application, the employee acknowledges that the image will be stored and may be viewed by authorized personnel in connection with the relevant work activity. Employees should not upload images containing sensitive personal information unrelated to their work duties.

06

Background Services & System Permissions

The Application requests certain device permissions to function correctly. Each permission is described below along with a clear justification for its necessity.

PermissionPurposeRequired?
Foreground Service Runs a persistent process during attendance validation windows to ensure reliable geofencing and check-in processing even if the device's OS attempts to suspend background tasks Required
Post Notifications Sends attendance reminders, module updates, and internal message alerts to the employee's device Required
Vibration Provides haptic feedback for incoming notifications and alerts, complementing visual and audio indicators Optional
Internet Access Required for all communication between the Application and backend servers, including login, attendance syncing, messaging, and data retrieval Required
Network State Access Allows the Application to check network connectivity before attempting data sync, preventing failed requests and unnecessary battery usage Required
Ignore Battery Optimizations Prevents the Android OS from suspending geofencing and attendance services during battery-saving modes, which would prevent automatic attendance marking from functioning reliably Required
Wake Lock Temporarily prevents the device CPU from sleeping during critical operations such as processing a scheduled notification or completing an attendance sync request; released immediately after the task completes Required
Camera Used to capture images for upload within messaging and module documentation features (see Section 5) On Use
Fine Location Provides high-accuracy GPS coordinates for geofence validation during attendance events (see Section 3) Required
Background Location Enables automatic attendance attempts during scheduled windows when the App is not in the foreground (see Section 3) Required

No permissions are requested beyond those listed above. The Application does not request access to contacts, microphone, call logs, calendar, storage outside of image uploads, or any other system resource not directly related to its workforce management functions.

07

How We Use Your Data

All data collected through the Application is used exclusively for the following organizational purposes:

7.1 Workforce Management

7.2 Operational Coordination

7.3 Security and Compliance

7.4 System Reliability and Improvement

We do not use your personal data for: advertising or marketing to third parties, selling or renting data to external organizations, building behavioral profiles for commercial use, or any purpose unrelated to legitimate workforce management.

08

Data Sharing & Disclosure

We do not sell, rent, or trade employee personal data. Sharing is limited to the following circumstances:

8.1 Within the Organization

8.2 Authorized Service Providers

We engage third-party service providers who process data on our behalf under strict contractual obligations. These providers include:

8.3 Legal and Regulatory Disclosure

We may disclose personal data if required to do so by applicable law, court order, regulatory requirement, or to protect the Company's legal rights. In such cases, we will disclose only the minimum information necessary to satisfy the legal obligation.

8.4 Business Transfers

In the event of a merger, acquisition, or transfer of Company assets, employee data may be transferred to the successor entity, subject to equivalent or stronger privacy protections as outlined in this Policy.

09

Data Retention Policy

We retain personal data only for as long as is necessary for the purposes described in this Policy, or as required by law. The following retention schedules apply:

Data CategoryRetention PeriodReason
Attendance Records Indefinitely, unless Company policy is revised Payroll compliance, labor law obligations, and historical workforce management
Messages & Uploaded Images 7 years Operational and legal record-keeping requirements
Location Data (outside geofence) 2 years Audit trail for attendance disputes and compliance verification
Device & System Logs Based on operational necessity (typically 90–180 days) Technical troubleshooting and security monitoring
Account Information Duration of employment + offboarding period Active workforce management; archived per HR policy after separation
Session Tokens Duration of active session; expire upon logout or inactivity Secure authentication; not retained after expiry

When retention periods expire, data is securely deleted or anonymized in a manner that prevents reconstruction of personal information. Deletion schedules are reviewed periodically and may be adjusted to reflect changes in applicable law or Company policy.

10

Account Deletion & Employee Offboarding

When an employee separates from the Company — whether through resignation, termination, retirement, or contract completion — the following process is followed:

10.1 Account Deactivation

10.2 Data Transfer and Reassignment

10.3 Retention of Historical Records

Following offboarding, historical records — including attendance logs, messages, and activity data — are retained in accordance with the Data Retention Policy in Section 9. This data may be required for payroll reconciliation, legal proceedings, compliance audits, or statutory labor record-keeping obligations.

10.4 Data Deletion Requests

Employees who wish to request deletion of their personal data upon separation may contact HR or the Application Administrator. Deletion requests will be honored to the extent permissible under applicable law; certain records may be required to be retained regardless of deletion request (e.g., attendance records required by labor law).

11

Data Storage & Security

We take the security of employee personal data seriously. Our infrastructure and practices are designed to protect data against unauthorized access, alteration, disclosure, or destruction.

11.1 Infrastructure

Our backend infrastructure is hosted on Amazon Web Services (AWS), one of the world's leading cloud platforms with extensive security certifications. Services used include:

11.2 Data Transmission Security

11.3 Access Controls

11.4 Server-Level Security

11.5 Backup and Recovery

No system is entirely immune to security risks. While we implement industry-standard safeguards, employees are also responsible for protecting their login credentials, not sharing account access, and logging out of the Application when using shared devices.

12

Third-Party Services

The Application integrates with a limited number of third-party services necessary for its operation. These integrations are listed below along with a description of how each service interacts with employee data.

ServicePurposeData Shared
Firebase Cloud Messaging (FCM) Delivers push notifications (attendance reminders, message alerts, module updates) to Android and iOS devices Device push token only; no personal data or message content
Expo Notification Services Cross-platform notification delivery layer used with Expo-based builds Device push token only
Google Maps (future integration) Will be used to render geofence zones on the administrative setup interface for office location configuration Anonymized map data and coordinates; no employee personal data
Amazon Web Services (AWS) Cloud infrastructure hosting for compute, database, and file storage All application data as described in Section 2; governed by AWS Data Processing Agreements

No analytics SDKs, behavioral tracking tools, or advertising networks are integrated into this Application. We do not use any service whose business model depends on monetizing user data.

13

Employee Rights

Employees have specific rights with respect to their personal data processed by the Application. The availability and scope of these rights may vary based on applicable law and your jurisdiction.

13.1 Right to Access

You have the right to request a summary of the personal data we hold about you, including your attendance history, account information, and any stored location data. Requests can be directed to HR or the Application Administrator.

13.2 Right to Correction

If you believe your data is inaccurate or incomplete (e.g., an attendance record is incorrectly marked), you may request a correction. HR will review and update records as appropriate after verification.

13.3 Right to Deletion

You may request deletion of your personal data. We will honor deletion requests to the extent permitted by law. Certain data — such as attendance records required for payroll or statutory compliance — may be exempt from deletion under applicable labor law.

13.4 Right to Object

You may object to certain types of data processing if you believe we are processing your data in a manner inconsistent with this Policy or your legal rights. Please raise any objections in writing to HR or the Application Administrator.

13.5 Right to Data Portability (where applicable)

Under GDPR and certain other data protection frameworks, you may have the right to receive a copy of your personal data in a structured, machine-readable format. Contact the Application Administrator to make such a request.

13.6 How to Exercise Your Rights

To exercise any of the rights described above, please contact:

We will acknowledge your request within 5 business days and aim to fulfill it within 30 days. Complex requests or large volumes may take up to 60 days, in which case we will notify you of the expected timeline.

14

Legal Basis for Processing

All personal data processing activities carried out through the Application are grounded in one or more of the following legal bases:

14.1 Contractual Necessity

Processing of attendance data, account information, and employee records is necessary for the performance of the employment contract between the Company and the employee. Attendance tracking, role assignment, and communication tools are integral to the employment relationship.

14.2 Legitimate Business Interest

The Company has a legitimate interest in managing its workforce effectively, ensuring operational compliance, verifying attendance through geofencing, and maintaining secure and functional internal communication tools. These interests are balanced against the employee's right to privacy and are proportionate to the purposes described in this Policy.

14.3 Legal Obligation

Certain data processing activities — such as maintaining attendance records, retaining financial and operational documentation, and cooperating with lawful regulatory requests — are required to comply with applicable labor, tax, and corporate governance laws.

14.4 Consent (where applicable)

For certain features — such as biometric authentication and optional notification preferences — processing is based on the employee's voluntary consent. Consent can be withdrawn at any time without affecting the legality of processing prior to withdrawal.

15

Compliance with Data Protection Laws

The Company is committed to aligning its data practices with applicable legal frameworks:

15.1 India – Digital Personal Data Protection Act (DPDP Act), 2023

As an Indian enterprise, we align our data processing practices with the DPDP Act. Key obligations include:

15.2 GDPR Principles (where applicable)

Where employees are based in or data is transferred to regions subject to the GDPR, we follow its core principles: lawfulness, fairness and transparency; purpose limitation; data minimization; accuracy; storage limitation; integrity and confidentiality; and accountability.

15.3 Ongoing Compliance Review

We periodically review our data practices against evolving legal requirements and will update this Policy as necessary to reflect changes in applicable law or organizational practices.

16

Children's Privacy

This Application is designed and intended exclusively for use by authorized adult employees of the Company. We do not knowingly collect, store, or process personal data from individuals under the age of 18. Accounts are created only by HR or Admin personnel in the context of a formal employment relationship, which by law requires that the individual be of legal working age in their jurisdiction.

If it is ever discovered that personal data has been inadvertently collected from a minor, we will take immediate steps to delete such data and review how the situation arose to prevent recurrence.

17

Data Breach and Incident Response

Despite our security measures, no system is entirely free from risk. In the event of a data security incident, the following process will be followed:

17.1 Detection and Containment

Upon detection of a suspected or confirmed data breach, the responsible technical and administrative personnel will take immediate steps to contain the breach, prevent further unauthorized access, and preserve evidence for investigation.

17.2 Assessment

The nature and scope of the breach will be assessed to determine: what data was affected, how many individuals are impacted, the likely consequences for those individuals, and the root cause of the incident.

17.3 Notification

17.4 Remediation

Following the incident, we will implement corrective measures to address the root cause, improve security controls, and update policies and procedures as necessary to reduce the risk of recurrence.

18

Cross-Border Data Transfers

Our backend infrastructure is hosted on Amazon Web Services (AWS). AWS data centers are located across multiple regions globally. Data may be processed or stored in regions outside India, including in countries within the United States or European Union, depending on the AWS region configured for our services.

Where data is transferred across borders, we ensure that adequate safeguards are in place, including reliance on AWS's standard contractual clauses and compliance certifications. We will update this Policy if significant changes are made to the regions in which data is processed.

Employees who have questions about where their specific data is stored may contact the Application Administrator.

19

Changes to This Policy

We reserve the right to update or amend this Privacy Policy at any time to reflect changes in our data practices, applicable laws, or organizational operations. When material changes are made:

We encourage employees to review this Policy periodically. Continued use of the Application following notification of changes constitutes acknowledgment of the updated Policy.

20

Contact Information

For any questions, concerns, or requests related to this Privacy Policy or the handling of your personal data, please contact:

Application Administrator / Data Contact
Email: prasanna@citadelnetinc.com
Organization: Citadel Net Inc.
Response Time: Within 5 business days

For internal HR-related concerns regarding your employment records, please contact your designated HR representative directly.