Effective Date: May 20, 2026
Policy Reference ID: ADYAPAN-CRM-PP-2026
This Privacy Policy ("Policy") is a legally binding document that governs the data collection, processing, and protection practices of Adyapan (hereinafter referred to as the "App", "Software", "we", "us", or "our").
The App is strictly classified as an Internal Enterprise CRM tool. It is designed exclusively for authorized personnel ("Authorized Employees") of our organization.
ENTERPRISE USE ONLY: This app is intended for authorized employees and enterprise use only. There is no sign-up or registration mechanism within the App for the general public. Access is securely provisioned and distributed solely by the Enterprise Administrator. Any unauthorized person cannot create an account or use this application.
Centralized Admin Portal Oversight: The App does not operate as a standalone consumer product. It functions strictly as a mobile client tethered to our centralized Enterprise Admin Portal. All employee accounts, permissions, lead assignments, and data visibility are strictly controlled, audited, and revoked exclusively via this Admin Portal by authorized Enterprise Management.
By accessing, authenticating, or utilizing the App, you explicitly consent to the data processing modalities outlined in this document.
We process Personal Data based strictly on the "Legitimate Interests" of the Enterprise Administrator to monitor, audit, and optimize their internal sales and telecalling operations. Data is collected exclusively to eliminate manual data entry and automate CRM workflows.
To fulfill its core B2B operational mandate, the App requires specific, explicit device-level permissions. We employ a principle of Data Minimization, collecting only what is absolutely critical.
3.1.1 — Core Functionality Declaration (Google Play Policy Compliance)
READ_CALL_LOG is the singular, irreplaceable, core feature of this application. This is not a supplementary or convenience feature — the entire business purpose of Adyapan CRM depends on it. Without this permission:
The app cannot function as a CRM tool in any meaningful capacity.
Employees would have to manually enter call outcomes, durations, and timestamps — defeating the purpose of an automated CRM.
The Enterprise Administrator would receive zero automated reporting on employee calling activities.
This permission is used exclusively within the scope of a legitimate, closed Enterprise B2B CRM system as defined by Google Play's Sensitive Permissions Policy. Adyapan is not a consumer call-log reader, a parental monitoring app, or a backup tool. It is a purpose-built internal enterprise telecalling CRM.
3.1.2 — Why No Alternative API Exists
We have evaluated all available Android telephony APIs as alternatives. No alternative satisfies our requirements:
API Considered
Why Insufficient
PhoneStateListener / TelephonyCallback
Provides call STATE (ringing, offhook) but NOT call duration, historical log, or missed call detection after the fact
CallLog.Calls without READ_CALL_LOG
Not accessible — requires READ_CALL_LOG by Android OS design
Manual user input
Unreliable, error-prone, defeats CRM automation purpose
Notification listeners
Cannot read telephony call metadata
Conclusion: READ_CALL_LOG is the only Android API capable of retrieving verified, tamper-proof call duration, timestamp, and connection status post-call — which are the three mandatory data points for this CRM.
3.1.3 — Dual-SIM Routing (READ_PHONE_STATE)
The App reads READ_PHONE_STATE exclusively to detect how many SIM cards are installed in the employee's device. This enables employees to pre-configure a default corporate SIM in Settings > Call Settings for all outbound CRM calls. This eliminates per-call SIM selection dialogs, improving operational efficiency. No voice content, IMEI, IMSI, or subscriber identity is transmitted externally.
3.1.4 — Exact Data Fields Accessed From Call Log
We access ONLY the following fields from CallLog.Calls:
Field
Purpose
NUMBER
To match against CRM lead database
DATE
To record call timestamp
DURATION
To log call duration for reporting
TYPE
To determine: incoming / outgoing / missed
We do NOT access: contact names, contact photos, call notes, voicemail content, conference participants, or any other call log field.
3.1.5 — On-Device Filtering: Personal Calls Are NEVER Processed
This is the most critical data minimization guarantee. The App implements a strict allowlist-based filter:
After every call event, the App reads the most recent entry from CallLog.Calls.
The retrieved phone number is immediately cross-referenced against the CRM Lead Database stored locally on the device (Room Database).
If the number EXISTS in the CRM Lead Database → call record is logged and synced.
If the number does NOT exist in the CRM Lead Database → call record is immediately discarded. It is never stored, never transmitted, never logged.
This means: calls to family, friends, personal contacts, emergency services, or any non-CRM number are completely invisible to our system. We have zero technical capability to access these calls — by design.
3.1.6 — Data Retention and Non-Disclosure
Call log data is securely synchronized exclusively with the Enterprise Administrator's private Firebase database.
We categorically do NOT sell, rent, license, or transmit call log data to any third-party data brokers, marketing agencies, analytics platforms, or unauthorized external entities — under any commercial arrangement or otherwise.
Call records are retained only for the duration of the Enterprise Administrator's active account. Upon account deletion, all records are permanently purged within 30 days.
3.1.7 — Prohibition on Interception
The App does NOT record, intercept, or store the audio content, voice, or conversation of any phone call.
The App does NOT use any call recording API, audio capture service, or microphone during calls.
The App does NOT read call logs in the background. Log access occurs only in the foreground, immediately after a call ends, triggered by the PHONE_STATE broadcast.
Operational Necessity: Authorized Users are required to log their daily attendance (Clock-in/Clock-out).
Processing Modality: Spatial coordinates are captured instantaneously and exclusively upon explicit user interaction with the Attendance module. The App does not engage in persistent background spatial tracking.
Operational Necessity: Required strictly for attaching digital assets (e.g., PDF brochures, client documents) to specific CRM profiles within the App's secure environment.
Operational Necessity: Required to render an instantaneous post-call disposition matrix (a popup dialog) immediately following a telephony event, allowing the Authorized User to categorize the lead outcome without manual application switching.
Operational Necessity: The App utilizes Firebase Cloud Messaging (FCM) to deliver real-time enterprise notifications to Authorized Users, including alerts for new lead assignments, attendance reminders, admin broadcasts, and system-critical CRM updates.
Data Processed: FCM processes a unique device token (a pseudonymous identifier) and the notification payload (title + body text). No PII is transmitted within the notification channel beyond what is operationally necessary.
Third-Party Disclosure: FCM is operated by Google LLC. Its data practices are governed by the Google Privacy Policy (https://policies.google.com/privacy). We disclaim liability for Google's own processing of device tokens.
User Control: Authorized Users may disable push notifications at any time via their device's system notification settings.
Operational Necessity: The App optionally employs an external Large Language Model (LLM) API — specifically the Anthropic Claude API — to generate contextually personalized WhatsApp outreach messages for CRM leads who have expressed interest or were not reachable.
Data Transmitted to Anthropic: When this feature is invoked by the user, the following minimal data points may be transmitted to Anthropic's servers: (a) the lead's first name only (or anonymized as "student" if unavailable), (b) the selected communication language, and (c) the lead's call disposition status (e.g., "Interested", "Busy"). This is the absolute minimum required to generate a contextually relevant message.
Data NOT Transmitted: Phone numbers, email addresses, location data, attendance records, college/city details, call logs, and all other PII are categorically NOT transmitted to Anthropic's API under any circumstance.
Anthropic's Data Policy: Anthropic's data usage is governed by their Privacy Policy (https://www.anthropic.com/privacy). Under Anthropic's commercial API agreement, API inputs and outputs are not used to train their models by default.
Fallback Behavior: If the AI API is unavailable, returns an error, or the lead has no name (manual dial), the App automatically falls back to pre-defined, locally-stored multilingual message templates. No data is left pending or retried automatically. No network call is made in fallback mode.
User Control (Strictly Opt-In): The AI message generation is strictly opt-in. The Authorized User must explicitly tap "Generate" to invoke this feature. No data is transmitted passively or in the background.
Operational Necessity: The App integrates with WhatsApp to allow Authorized Users to send follow-up messages and PDF brochures to CRM leads.
Mechanism: The App uses Android's standard Intent system (ACTION_VIEW) to open the WhatsApp application with a pre-populated message. The App does NOT use WhatsApp's Business API, any unofficial automation library, or any mechanism that bypasses user confirmation.
Data Routing: When an Authorized User explicitly taps "Send", the lead's phone number and the pre-generated message text are passed to the WhatsApp application installed on the user's device. This data then becomes subject to Meta's Privacy Policy (https://www.whatsapp.com/legal/privacy-policy).
No WhatsApp Account Access: The App does not access, read, store, or intercept any WhatsApp messages, contacts, media, or account information.
Operational Necessity: CRM lead data, call records, and attendance summaries are periodically synchronized to a private Google Sheets spreadsheet exclusively controlled by the Enterprise Administrator for reporting and oversight purposes.
Data Synchronized: Name, phone number, call disposition status, call duration, notes, and attendance timestamps are synced.
Access Control: The Google Sheets document is private and accessible only to the Enterprise Administrator via their authenticated Google Account. No public sharing links are generated by the App. No data is visible to Google for advertising purposes under Google Workspace agreements.
Google's Data Policy: Google Sheets is operated by Google LLC under the Google Workspace Terms of Service (https://workspace.google.com/terms/premier_terms.html).
Operational Necessity: The App collects the device's unique ANDROID_ID — a pseudonymous hardware-derived identifier — exclusively to enforce the Single-Device Login Policy (one account per device). This prevents unauthorized credential sharing between multiple employees.
Processing Modality: The ANDROID_ID is captured at first login and securely stored in the Enterprise Cloud Database (Firebase Firestore) associated with the employee's account. On every subsequent app launch, the current device's ANDROID_ID is compared against the stored value. If a mismatch is detected (indicating login from a new device), the session is immediately terminated.
Data NOT Used For: The ANDROID_ID is categorically not used for advertising, cross-app tracking, behavioral profiling, or any purpose beyond single-device enforcement.
Data Minimization: Only the ANDROID_ID string is stored. No other device hardware identifiers (IMEI, serial number, MAC address) are accessed or collected.
User Control: To authorize a new device, the employee must contact their Enterprise Administrator to reset the active device binding.
We warrant and represent that the App is in strict, unwavering compliance with the Google Play Developer Program Policies, specifically the Sensitive Information and Permissions Policy.
Mandatory Prominent Disclosure: Prior to the invocation of any Android runtime permission request for highly sensitive data (specifically READ_CALL_LOG, READ_PHONE_STATE, ACCESS_FINE_LOCATION, and CAMERA), the App programmatically interrupts the UI flow to display an explicit Prominent Disclosure.
Call Log Disclosure Verbiage: The disclosure explicitly states: "Adyapan is an Enterprise CRM app. We need access to your Call Logs and Phone State to automatically track incoming and outgoing calls with leads... This data is strictly used for your internal CRM productivity."
Location & Camera Disclosure Verbiage: The disclosure explicitly states: "Adyapan CRM needs access to your Location to verify your physical presence at the office when clocking in, and access to your Camera to capture a mandatory check-in selfie for enterprise verification."
Affirmative Action Requirement: The system permission dialog is strictly invoked ONLY subsequent to the user providing explicit, affirmative consent by tapping "I Understand" on the Prominent Disclosure dialog.
We acknowledge that the combination of READ_CALL_LOG, READ_PHONE_STATE, SYSTEM_ALERT_WINDOW, and FLAG_SECURE may appear powerful when viewed in isolation. We proactively address this concern:
Why This Combination Does NOT Constitute Surveillance
Each permission serves a distinct, non-overlapping enterprise operational purpose. They do not synergize to create surveillance capability:
Permission
Sole Purpose
What It CANNOT Do
READ_CALL_LOG
Log CRM lead call outcomes (duration, status)
Cannot read personal calls (allowlist filter active)
READ_PHONE_STATE
Detect dual-SIM for call routing
Cannot intercept audio, IMEI not transmitted
SYSTEM_ALERT_WINDOW
Show post-call status popup (2-second UI)
Cannot overlay other apps persistently or spy on content
FLAG_SECURE
Protect employee CRM data FROM surveillance
Actively PREVENTS screen capture by unauthorized parties
Critical Distinction: Protection vs. Surveillance
FLAG_SECURE is an anti-surveillance tool, not a surveillance tool. It protects the employee's CRM data FROM being captured by third parties. Its purpose is the exact opposite of surveillance.
What Surveillance / Spyware Apps Do — That This App Does NOT:
❌ Read ALL call logs (personal + business) — We filter: CRM leads only
❌ Run invisibly in background without user knowledge — We are fully visible, user-installed
❌ Upload call audio or voice recordings — We have zero microphone access
❌ Track GPS location continuously — Location accessed only on explicit attendance tap
❌ Access SMS, emails, or messaging apps — Zero messaging access
❌ Access contact list or phonebook — Zero contacts access
❌ Send data to unknown third-party servers — Data goes only to enterprise's own Firebase
❌ Hide the app icon or run as a hidden service — App is fully visible in launcher
Industry Precedent: This Is Standard Enterprise CRM Architecture
The combination of permissions used by Adyapan CRM is industry-standard for enterprise telecalling CRM applications. Comparable enterprise CRM platforms (Salesforce Mobile, Zoho CRM, Freshsales) use identical or broader permission sets for the same legitimate business purposes. Our implementation is, in fact, more restricted than industry peers, as we apply on-device allowlist filtering that most competitors do not implement.
Employee Awareness and Consent
Every employee who uses this App is an adult, professional, enterprise-contracted individual who has been briefed by their employer about CRM monitoring.
The App is not installed remotely or secretly. Employees download and install it voluntarily from Google Play Store.
The Prominent Disclosure is shown to every new user before any permission is requested.
Employees can request account deletion at any time via Settings.
The App utilizes Google Firebase (Cloud Firestore, Realtime Database, Authentication, Cloud Messaging) as its primary backend infrastructure.
Encryption: All data payloads transmitted between the App and Firebase servers are encrypted in transit via Transport Layer Security (TLS/HTTPS). Data at rest is encrypted using AES-256 standards managed by Google Cloud.
Liability Limitation: While we deploy enterprise-grade security protocols, no digital transmission is cryptographically infallible. We disclaim liability for breaches occurring due to underlying operating system vulnerabilities or user negligence.
Retention Lifecycle: Data is retained strictly for the duration of the Enterprise Administrator's active subscription.
Right to Erasure and Account Deletion: Any Authorized User may enact a formal request for account and data purging directly through the App by navigating to Settings > Legal & Security > Request Account Deletion. This action will generate a formal deletion request email to the Enterprise Administrator. Upon verified request, all associated PII (Personally Identifiable Information) and telephony logs will be permanently expunged from our active production databases within thirty (30) calendar days.
This Software is strictly intended for adults acting in a professional capacity. It is expressly prohibited for use by any individual under the age of eighteen (18) or the age of legal majority in their jurisdiction. We employ zero mechanisms to solicit data from minors.
In the unlikely event of a verified cryptographic breach or unauthorized data exfiltration affecting PII or telephony logs, the Enterprise Administrator will be formally notified within seventy-two (72) hours of discovery. We disclaim liability for breaches originating from compromised employee hardware or Authorized User negligence.
By utilizing this Software, the Enterprise Administrator and all Authorized Employees agree to indemnify, defend, and hold harmless Adyapan and its developers from any claims, damages, or regulatory fines arising from the misuse of the CRM, including but not limited to violations of local telemarketing laws (e.g., calling individuals on a Do Not Call registry). Adyapan acts strictly as a data processor; the Enterprise Administrator retains full liability as the data controller.
This Policy and any disputes arising hereunder shall be governed exclusively by and construed in accordance with the laws of India, including but not limited to the Digital Personal Data Protection Act, 2023 (DPDP Act) and the Information Technology Act, 2000. Any legal action, suit, or proceeding arising out of or relating to this Privacy Policy shall be instituted exclusively in the competent courts located in Hyderabad, Telangana, India.
Adyapan acknowledges and complies with the provisions of the Digital Personal Data Protection Act, 2023 enacted by the Government of India.
Data Fiduciary: Adyapan School acts as the Data Fiduciary as defined under the DPDP Act, responsible for determining the purpose and means of processing personal data.
Data Principal Rights: Authorized Users (Data Principals) have the following rights under the DPDP Act:
Right to Access: Obtain a summary of personal data being processed and the processing activities undertaken.
Right to Correction: Correct inaccurate or misleading personal data.
Right to Erasure: Request erasure of personal data no longer necessary for the purpose it was collected (via Settings > Legal & Security > Request Account Deletion).
Right to Grievance Redressal: Have grievances addressed by our Data Protection Officer within a reasonable timeframe.
Right to Nominate: Nominate another individual to exercise these rights in the event of the Data Principal's incapacity.
Consent Basis: Personal data of employees is processed on the basis of legitimate interest and employment contract obligations, consistent with DPDP Act provisions for employment contexts.
Cross-Border Data Transfers: Data may be processed on servers located outside India (Firebase/Google Cloud, Anthropic API). Such transfers are made in compliance with applicable data transfer frameworks and DPDP Act provisions.
Grievance Officer: For DPDP Act-related grievances, contact our Data Protection Officer at the address listed in Section 15.
Authorized Users are strictly bound to comply with all regional and international telemarketing regulations, including but not limited to the Telecom Regulatory Authority of India (TRAI) guidelines, the Telephone Consumer Protection Act (TCPA), and applicable Do-Not-Call (DNC) registries. Adyapan provides the technical infrastructure to log calls but assumes zero liability for the legal validity or authorization of the outbound calls made by the Enterprise Administrator's personnel.
THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. IN NO EVENT SHALL THE DEVELOPERS OR DATA PROTECTION OFFICERS BE LIABLE FOR ANY CLAIM, DAMAGES, OR OTHER LIABILITY ARISING FROM, OUT OF, OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
If any provision of this Privacy Policy is held by a court of competent jurisdiction to be invalid, illegal, or unenforceable, the remaining provisions of this Policy shall remain in full force and effect.
Adyapan commits to the following absolute guarantees regarding data minimization:
We do NOT sell, rent, barter, or commercially exploit any user or lead data to third-party data brokers, advertisers, or marketing agencies — under any circumstances.
We do NOT use lead contact information for any purpose other than the enterprise CRM workflows explicitly described herein.
We do NOT access personal SMS messages, email content, social media accounts, or any data beyond the explicitly listed permissions.
We do NOT engage in persistent background location tracking, keystroke logging, or behavioral profiling of Authorized Users.
All AI-generated content (via Anthropic Claude) is ephemerally processed. No lead data is stored, logged, or retained by Anthropic beyond the immediate API call under the commercial API agreement.
The App does NOT contain any advertising SDKs, cross-app tracking libraries, or third-party analytics tools beyond Google Firebase.
We reserve the unilateral right to amend this Privacy Policy to reflect evolving legal and regulatory paradigms. Authorized Users will be notified of material changes. Continued use of the App post-modification constitutes binding acceptance.
For matters pertaining to data protection, compliance audits, or privacy inquiries, direct all correspondence to:
Data Protection Officer: Sai Charan
Developer: Gulshan Kumar
Corporate Email: gulshan@adyapan.com
Website: https://adyapanschool.com/
Registered Address: Sattva Magnus, behind Reliance Bazaar Shaikpet, Sabza Colony, Ambedkar Nagar, Toli Chowki, Hyderabad, Telangana 500008, India
Grievance Redressal (IT Rules, 2021): As mandated under Rule 5(9) of the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, our Grievance Officer will acknowledge any privacy complaint within 24 hours and resolve it within 30 calendar days of receipt.
© 2026 Adyapan School. All Rights Reserved.
Absolute Ownership: The entire software architecture, source code, UI/UX design, underlying algorithms, and associated business logic of the "Adyapan" application are the exclusive intellectual property of Adyapan School.
Strict Prohibitions: Any unauthorized reproduction, redistribution, decompilation, reverse-engineering, modification, or commercial cloning of this software, in whole or in part, is strictly prohibited.
Zero Tolerance for IP Theft: Any infringement will be met with immediate legal prosecution under the Indian Copyright Act, 1957, the Information Technology Act, 2000, and applicable international intellectual property treaties, seeking both injunctive relief and maximum financial damages.
Employee Liability Exemption: The Enterprise Administrator and Developers bear zero liability for any unlawful telemarketing practices, data breaches, or policy violations committed by individual employees using this software. The individual Authorized User assumes full personal legal responsibility for their actions while utilizing the App.
Adyapan implements the following device-level security mechanisms to protect enterprise data integrity:
Root Detection: The App performs an automated root detection check at every launch. If the device is determined to be rooted (using indicators such as presence of su binaries or Magisk installations), the App immediately terminates and denies access. This prevents data exfiltration via root-level exploits.
Single-Device Enforcement (One Account Per Device): Each employee account is cryptographically bound to a single device using the device's unique ANDROID_ID. Concurrent login from a second device triggers automatic session termination on the previous device and forces re-authentication. This prevents credential sharing.
Screenshot and Screen Recording Prevention (FLAG_SECURE): The App sets the FLAG_SECURE window flag across all primary screens. This programmatically prevents:
System screenshot capture (Print Screen / hardware button combination)
Screen recording by third-party apps
Display in the Recent Apps (task switcher) preview
Google Assistant / AI overlays from reading screen content
Code Obfuscation: The release build of the App applies ProGuard code minification and obfuscation, making reverse-engineering and decompilation significantly more difficult.
Cleartext Traffic Prohibition: The App enforces android:usesCleartextTraffic="false" at the network security level. All outbound network communications are mandatorily routed over HTTPS/TLS. Plaintext HTTP connections are categorically blocked.
Encrypted Preferences Storage: Sensitive application credentials and configuration data stored on-device are encrypted using the androidx.security.crypto.EncryptedSharedPreferences library, backed by AES-256 encryption managed by the Android Keystore system.
Adyapan makes the following categorical declarations to Authorized Users and regulatory authorities:
Zero Cookies: The App does not deploy, set, read, or transmit HTTP cookies of any kind — session, persistent, tracking, or analytical.
Zero Cross-App Tracking: The App does not employ any cross-application tracking identifier (e.g., IDFA, GAID, fingerprinting) for advertising or profiling purposes.
Zero Ad SDKs: The App does not contain any advertising Software Development Kits (SDKs) from Meta Audience Network, Google AdMob, AppLovin, Unity Ads, or any other ad monetization platform.
Zero Behavioral Profiling: The App does not build, infer, or transmit behavioral profiles, interest graphs, or psychographic models of any Authorized User or CRM lead.
Zero Data Brokering: No data collected by this App is sold, licensed, or transmitted to data brokers, data enrichment services, or marketing intelligence platforms under any commercial arrangement.
Analytics Scope: The only analytics infrastructure present in the App is Google Firebase Analytics (implicitly included with Firebase SDK). This is used exclusively for crash diagnostics and app stability monitoring, not for advertising targeting. Firebase Analytics data is not shared with Google's advertising products under Firebase's standard enterprise data processing terms.
Biometric Data: While the App includes the androidx.biometric library as a dependency, this library is used exclusively to provide a secure, system-level biometric authentication prompt for app-lock features if implemented. The App does not collect, store, transmit, or process raw biometric data (fingerprint templates, facial geometry, iris scans, etc.). All biometric processing is performed entirely on-device by the Android OS Biometric subsystem. No biometric data ever leaves the device.
Accessibility Service: The App does not declare, register, or use an Android AccessibilityService. It does not read the screen content of other applications, intercept user input in other apps, or perform any action that requires accessibility service permissions.
Camera Usage Scope: The camera permission is used exclusively for capturing an attendance verification selfie within the Attendance module. The App does not perform facial recognition, biometric identification, or any AI-based analysis on captured images. Images are stored solely for enterprise attendance record purposes and are accessible only to the Enterprise Administrator.
Adyapan explicitly declares that it does NOT collect, infer, process, or store any of the following sensitive personal data categories as defined under the DPDP Act, 2023, GDPR Article 9, and global privacy frameworks:
Sensitive Category
Collection Status
Health / Medical records
❌ NOT collected
Religious or caste beliefs
❌ NOT collected
Political opinions or affiliation
❌ NOT collected
Racial or ethnic origin
❌ NOT collected
Genetic or biometric identity data
❌ NOT collected
Sexual orientation or gender identity
❌ NOT collected
Financial account / banking details
❌ NOT collected
Criminal records or legal history
❌ NOT collected
Trade union membership
❌ NOT collected
Immigration or citizenship status
❌ NOT collected
The only personal data collected is strictly limited to what is described in Section 3 of this Policy for enterprise CRM operational purposes.
In alignment with international data protection standards and the Digital Personal Data Protection Act, 2023, Authorized Users have the following rights regarding their personal data:
Right to Data Portability: Any Authorized User may formally request a complete export of their personal data held by Adyapan CRM in a structured, commonly used, machine-readable format (e.g., CSV or JSON).
How to Request: Submit a written data export request to the Data Protection Officer at the contact address listed in Section 15 with the subject line: "Data Portability Request — Adyapan CRM".
Fulfillment Timeline: We will fulfill verified data portability requests within thirty (30) calendar days of receipt and identity verification.
Scope of Exportable Data: The export will include: employee profile information, call records attributed to the requesting user, attendance records, and lead disposition notes entered by the requesting user.
Data NOT Exportable: Enterprise-confidential data (other employees' records, admin configurations, lead databases owned by the Enterprise) will not be included in individual data export requests, as these belong to the Enterprise Administrator as Data Controller.
No Fee: Data portability requests are processed free of charge for the first request per calendar year.