Privacy Policy & Disclosure Statement

Effective Date: July 19, 2026

This Privacy Policy outlines the explicit legal guidelines, data governance frameworks, and security protocols enforced by OTP Master ("we", "our", "us", or "the Application"). This document constitutes a binding disclosure regarding how the Application collects, processes, transmits, and manages user information, credentials, and session metrics.

IMPORTANT LEGAL NOTICE & PROPRIETARY DISCLAIMER:
This Application operates independently as an automation utility tool. It is not affiliated, associated, authorized, endorsed by, or in any way officially connected with any E-commerce platform, or any of its subsidiaries or affiliates. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

1. Data Collection Categories

To deliver automated account management workflows, synchronization pipelines, and interface functionality, the Application collects the following strict classifications of data:

Primary Identity Data: Name, authenticated email addresses, and contact numbers captured during explicit user registration routines.
User-Provided Third-Party Credentials: Encrypted merchant storefront login names, corresponding access credentials, and structural platform supplier identification codes.
Ephemeral Network Identifiers: Dynamic browser context cookies, browser fingerprints, and temporary session keys generated exclusively during operational validation sequences.

2. Purpose of Processing and Scope of Use

Data processing is conducted strictly under the legal grounds of contractual necessity to fulfill your execution requests. We utilize data solely within the following technical boundaries:

To securely establish, authenticate, and maintain your primary dashboard user session.
To execute automated backend routine sequences to your designated third-party supplier profiles on your explicit instruction and authorization.
To isolate, fetch, transform, and render active return parcel delivery codes, counts, and associated Air Waybill (AWB) numeric strings inside your localized layout workspace.

3. Data Protection, Transmission, and Security Architecture

We deploy rigorous technical and organizational security protocols to safeguard your processing metrics:

Encryption Protocols: All network exchanges, payload data transmissions, and external endpoint communication loops are strictly executed over Transport Layer Security (TLS/HTTPS) encrypted channels.
Isolation Protocols: Third-party merchant credentials and dynamic cookie arrays are kept inside secured, access-controlled cloud database structures designed to resist unauthorized exfiltration.
Storage Minimization: We do not keep logs of historical transactional parameters beyond the short operational window required to serve your immediate screen synchronizations.

4. Non-Disclosure & Third-Party Provisions

We strictly enforce a zero-monetization policy regarding user data:

We absolutely do not sell, trade, rent, lease, or distribute user identification arrays, operational logs, or merchant credentials to any third-party marketing brokers or analytics firms.
Data routing occurs solely between the Application's isolated backend server infrastructure and the targeted official merchant platform endpoints required to fetch your requested data state.
We reserve the right to disclose personal parameters only if explicitly mandated by operation of law, subpoena, or clear judicial decree issued by a competent court of jurisdiction.

5. User Rights, Data Eviction, and Retention Limits

You maintain absolute structural control over all submitted assets:

Users have the immediate right to inspect, modify, or permanently purge saved store profile configurations directly via the dashboard configuration engine.
Executing a profile deletion command instantly forces a database deletion sequence, clearing associated credentials and cookies from all active server data engines.
Upon request for account closure, all primary account identifiers and operational files will be securely purged within standard system maintenance window updates.

6. Regulatory Compliance & Global Standards

This policy is engineered to meet the stringent user data handling guidelines required by the Google Play Store developer distribution policies, with explicit focus on transparency regarding the handling of personal, sensitive, and financial merchant credentials.

7. Legal Entity Contact Information

For official legal notifications, formal data access requests, or specific question arrays concerning this privacy policy framework, please direct communications to our compliance channel:

Compliance Email: support@otpmaster.in