Introduction & Core Principles
Protecting user privacy and maintaining data security are foundational obligations for any digital platform or mobile application. This Privacy Policy Guide provides a transparent, exhaustive explanation of how user data is collected, stored, processed, and safeguarded. By using the platform, users agree to the collection and use of information in accordance with this policy and applicable data protection legislation, including the Digital Personal Data Protection (DPDP) Act.
Our core privacy commitment rests on three primary pillars:
- Transparency: Plainly declaring what information is gathered and why.
- Security: Employing modern cryptographic standards to defend against unauthorized access.
- User Control: Empowering individuals with rights over their personal identification and financial records.
1. Information Collection & Data Gathering
To provide seamless functional features, account administration, and transactional processing, explicit data points must be gathered during interaction with the platform.
┌───────────────────────────────────┐
│ DATA COLLECTION ARCHITECTURE │
└─────────────────┬─────────────────┘
│
┌───────────────────────────┼───────────────────────────┐
▼ ▼ ▼
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ User-Provided │ │ Automated Device │ │ Financial & │
│ Data │ │ Telemetry │ │ Transaction Data │
├──────────────────┤ ├──────────────────┤ ├──────────────────┤
│ • Full Legal Name│ │ • IP Address │ │ • Bank Account │
│ • Phone & OTP │ │ • Device Model │ │ • Unified UPI ID │
│ • Email Address │ │ • OS Version │ │ • Wallet Address │
│ • Age (18+) │ │ • App Logs │ │ • Deposit Logs │
└──────────────────┘ └──────────────────┘ └──────────────────┘
A. Information You Provide Directly
- Account Registration: When creating an account, users supply essential personal identifiers, including primary phone numbers, email addresses, and account credentials.
- Identity Verification (KYC): For legal compliance and security checks, legal names, date of birth (verifying the mandatory 18+ age requirement), and national identification records may be required prior to withdrawal processing.
- Support Interactions: Records of communications sent to our customer service desk, including chat logs, submitted support tickets, and email correspondence.
B. Data Collected Automatically
- Device Telemetry: Information automatically transmitted by your hardware, including device model, operating system build, unique device identifiers (UUID), screen resolution, and network operator.
- Log & Usage Data: IP addresses, timestamped access records, system crash reports, performance metrics, and navigational pathways within the application interface.
- Cookies & Session Tokens: Temporary session identifiers used to maintain user authentication states across app instances.
C. Financial & Transactional Data
- Payout Credentials: Bank account numbers, IFSC codes, bank names, and registered UPI identifiers mapped for processing fund payouts.
- Cryptographic Addresses: External public wallet details (e.g., TRC-20 wallet addresses) registered for digital asset transactions.
- Transaction History: Detailed ledger records tracking deposits, withdrawal requests, bonus claim timestamps, and internal wallet movements.
2. Comprehensive Data Usage Matrix
Every piece of collected data serves a distinct operational, security, or legal objective. The table below details the precise relationships between data categories, operational purposes, and storage lifecycles.
| Data Category | Specific Data Points Collected | Primary Operational Purpose | Legal / Compliance Basis | Retention Period |
| Personal Identity | Full name, phone number, email address, age verification | Account creation, authentication, age enforcement (18+ only) | User Consent & Contract Terms | Duration of active account + 2 years |
| Financial Details | Bank account number, IFSC code, UPI ID, crypto wallet address | Processing verified withdrawals, payouts, and deposit routing | Contractual Obligation & Fraud Prevention | 7 years (Financial Audit Compliance) |
| Device Diagnostics | IP address, device ID, operating system version | Preventing duplicate accounts, detecting abuse, fixing app crashes | Legitimate Security Interest | 90 days rolling storage |
| Support Logs | Chat logs, email tickets, submitted inquiry forms | Customer dispute resolution, quality control, agent training | Customer Service Quality | 1 year from ticket resolution |
| Transaction Logs | Timestamps, transaction amounts, reference IDs | Balance accounting, wager turnover audits, tax accounting | Regulatory & Legal Requirement | 7 years minimum |
3. Step-by-Step Data Handling & Payment Verification
To maintain security during sensitive actions like managing withdrawal destinations or modifying credentials, strict operational sequences must be executed.
1.Identity & Account Verification:Prerequisite before any financial payout request.
The user initiates an account action (such as linking payment details). The application cross-references the registered phone number and forces a One-Time Password (OTP) verification check to validate ownership.
2.Data Encryption & Transmission:Securing sensitive credentials in transit.
All submitted bank account details, UPI identifiers, or wallet strings are immediately encrypted at the application level using 256-bit AES encryption standards before transmission across TLS 1.3 secured channels.
3.Database Vaulting & Access Restrictions:Securing data at rest.
Encrypted data is stored in partitioned database vaults. Direct database access is blocked for general administrative accounts and restricted strictly to automated settlement scripts.
4.Dispute & Inquiry Escalation:Handled directly by Panther Support Team.
If an anomaly occurs during transaction settlement, the user contacts the Panther Support Team. Customer service agents review tokenized logs without directly exposing full account payment numbers to external personnel.
4. Advanced Security Infrastructure & Fraud Prevention
We employ multi-layered technical controls to prevent unauthorized access, data leaks, and identity misuse.
+---------------------------------------+
| UNIFIED SECURITY SHIELD |
+-------------------+-------------------+
|
+----------------------------+----------------------------+
| | |
v v v
+-------------------+ +-------------------+ +-------------------+
| 256-Bit TLS | | Multi-Factor | | Automated Anti- |
| Encryption | | Authentication | | Fraud Engine |
+-------------------+ +-------------------+ +-------------------+
| Encrypts data in | | Requires OTP code | | Flags multi-accs, |
| transit between | | verification for | | device cloning, |
| app and server. | | withdrawal edits. | | and proxy IPs. |
+-------------------+ +-------------------+ +-------------------+
- Multi-Factor Authentication (MFA): Critical account actions—such as adding a bank account, altering a UPI ID, or requesting wallet changes—require secondary validation via mobile OTP.
- Anti-Fraud & Anti-Cloning Systems: Automated algorithms monitor account activity to detect suspicious behavior, including multi-account creation on identical IP ranges, virtual machine emulation, or proxy manipulations.
- Strict Age Restrictions (18+ Policy): Minors are prohibited from registering or executing financial transactions. Accounts found violating age limits are terminated immediately, and collected details are purged.
- Data Isolation: Financial details are isolated from general app analytics engines, preventing accidental exposure during internal software performance checks.
5. Third-Party Data Sharing & External Integrations
Personal data is never sold, leased, or traded to third-party marketing organizations. Limited sharing occurs strictly under the following controlled circumstances:
- Payment Gateways & Banking Partners: Financial data is transmitted securely to licensed banking entities and payment gateways solely to facilitate deposits and process requested payouts.
- SMS & Communication Gateway Providers: Mobile numbers are shared with automated SMS infrastructure providers to deliver registration verification codes, transaction alerts, and security OTPs.
- Legal Compliance & Enforcement: Data may be disclosed to law enforcement or regulatory authorities if mandated by court orders, formal legal subpoenas, or applicable anti-money laundering (AML) legislation.
6. User Rights, Privacy Control & Support Escalation
Users maintain full control over their personal records in accordance with global privacy governance frameworks.
Your Data Rights
- Right to Access: You may request a structured export of all personal data linked to your user account.
- Right to Rectification: You can request corrections to outdated or misstated personal information, such as updated mobile numbers or email records.
- Right to Erasure (Account Deletion): Users may request full account closure and data deletion, provided there are no active legal investigations or mandatory financial audit holds.
Assistance & Support Inquiries
For questions regarding this policy, data correction requests, or transaction support, users can reach out directly to dedicated customer service channels.
===================================================================
CUSTOMER SUPPORT DIRECTORY
===================================================================
Designated Team: Panther Support Team
Primary Channel: Official In-App Support Portal
Verification: Requires Registered Phone Number + Account ID
Escalation Hours: 24 / 7 Response Availability
===================================================================
7. Policy Updates & Modifications
This Privacy Policy is subject to periodic reviews and updates to reflect changing regulatory requirements, platform improvements, or operational changes. Any material modifications will be announced via in-app notifications or official announcements. Continued use of the service following posted updates constitutes formal acceptance of the revised privacy framework.