Sankari Arthika FinTrack

Legal

Privacy Policy

Sankari Arthika FinTrack - Privacy Policy

2. Information Handled, Purpose, and Defense Mechanisms

To manage credit lines, deliver accurate financial tracking, and shield users against fraud, we process the specific categories of data outlined below:

  • 1. Mobile Phone Number

    Required
    Why We Collect & How We Use It
    Essential for account creation, binding your registered credit card details, sending One-Time Passwords (OTPs) for multi-factor authentication, and delivering urgent transaction alerts.
    Protection Standards
    Secured using military-grade encryption protocols (AES-256) in transit and at rest, stored in isolated database units with restricted access.
  • 2. Email Address

    Optional
    Why We Collect & How We Use It
    Facilitates account recovery, enables distribution of digital monthly spending reports, and provides customer service updates.
    Protection Standards
    Protected through secure authorization tokens. Your email will never be rented, sold, or shared with third parties for marketing purposes.
  • 3. Camera & Image Data

    Optional
    Why We Collect & How We Use It
    Allows you to upload physical identity records during KYC compliance, scan card statements, or archive receipt images for expense categorization.
    Protection Standards
    Operational strictly on an active foreground basis when initialized by you. We do not access camera hardware in the background, and captured images pass through encrypted channels.
  • 4. Emergency Contact Details

    Required
    Why We Collect & How We Use It
    Serves as a backup identification line used strictly to verify account ownership during emergency security lockouts or suspicious access attempts.
    Protection Standards
    Anonymized and stored in cryptographically hashed formats. Emergency contacts are never contacted for marketing, loans, or third-party promotional activities.
  • 5. Identifiers: User ID, Device ID, & Advertising ID

    Optional
    Why We Collect & How We Use It
    User and Device IDs preserve secure session tokens and prevent multi-device hijack attempts. Advertising IDs deliver tailored financial offers within the application.
    Protection Standards
    Identifiers are decoupled from your real-world identity. You retain full control to opt out or reset your Advertising ID via your system settings.
  • 6. Approximate Location Data

    Optional
    Why We Collect & How We Use It
    Verifies that login attempts and transaction entries originate from permitted regional territories within India, neutralizing malicious remote takeovers.
    Protection Standards
    Processed strictly at a coarse/city level without storing precise GPS trajectories or tracking your daily movement logs.
  • 7. Crash Reporting & System Logs

    Required
    Why We Collect & How We Use It
    Captures unexpected system failures and stack traces, allowing our engineering team to rectify software errors and optimize application performance.
    Protection Standards
    Stripped of all Personally Identifiable Information (PII) before transmission to diagnostic servers.
  • 8. Installed Application Inventory

    Required
    Why We Collect & How We Use It
    Scans for unauthorized remote desktop applications or malicious overlay apps that target financial applications to extract credit credentials.
    Protection Standards
    Executed locally via real-time security hash lookups; no static list of your personal applications is permanently archived or stored on external servers.
  • 9. SMS Access Permission

    Optional
    Why We Collect & How We Use It
    Automatically extracts financial alerts (credit card statements, billing reminders, transaction notices) to generate your unified dashboard.
    Protection Standards
    Text parsing occurs locally on your handheld device. Non-financial and personal messages are completely filtered out and never transmitted or recorded.
  • 10. Device Infrastructure Profile (Storage Status, Battery Level, Bluetooth, Hardware Specs, Memory, Network Condition, Sensor Metrics)

    Required
    Why We Collect & How We Use It
    Evaluates hardware profiles, battery behaviors, network conditions, and sensor inputs to create a robust security token that prevents automated bot scripts and fraudulent access.
    Protection Standards
    Synthesized into an irreversible digital fingerprint used purely for system integrity, anti-bot defenses, and UI rendering performance.

3. Data Governance, User Rights, & Retention Policy

Data Security in Transit
All network traffic between your device and our endpoints is fortified with Transport Layer Security (TLS 1.3).
Retention Lifecycle
Data is preserved strictly for the duration necessary to satisfy financial statutory regulations and service requirements under Indian laws.
User Consent Rights
You retain the right to withdraw consent, modify permissions, or request complete account erasure via our dedicated support channels. Eligible data will be scrubbed within 15 working days.