Privacy Policy

DialMaster – Smart Auto Dialer & Call Assistant

Last Updated: November 15, 2025 • Developer: ZeengoCorp Innovations • Support: support@dialmaster.in

Table of Contents

1. Introduction & Scope

DialMaster – Smart Auto Dialer & Call Assistant (the “App”, “we”, “our” or “DialMaster”) provides a semi-automatic call workflow that launches calls through the device's native dialer (ACTION_DIAL). This document explains our privacy practices, the data we collect and process, the choices available to you, and the measures we take to protect your data.

Scope: This Policy applies to all users of the App on Android and iOS, and to any server-side processing related to account management, monetization and analytics performed by or on behalf of the developer.

2. App Identity, Purpose & Scope of Processing

  • App name:DialMaster – Smart Auto Dialer & Call Assistant
  • Developer:ZeengoCorp Innovations (a registered company)
  • Support email:support@dialmaster.in
  • Primary Purpose:Help users manage outbound call workflows, import contact lists locally, sequence calls, launch calls via the device's dialer, capture call outcomes and notes, and provide monetization via ads and subscriptions. DialMaster intentionally avoids background call tracking, call recordings, and server-side storage of contact lists (except for explicitly opt-in backup).

3. Definitions

Personal Data:

Any information that identifies or could reasonably identify an individual.

Device Data:

Data generated by or stored on your device (contacts, notes, local coins ledger).

Controller/Processor:

DialMaster is the data controller for account and subscription data; third-party ad and analytics providers act as controllers/processors for ad and telemetry data.

4. Data We Collect (Detailed)

We collect only the minimum information necessary to operate the App, validate purchases, serve ads, and improve the product. All data categories are described below with purpose and storage details.

A. Authentication & Account Data (Collected via Google Sign-In)

  • • Google account ID / Firebase UID: Used to map purchases and subscriptions to your account; stored server-side in Firebase Authentication and Firestore.
  • • Display name & email: Used for support, account identification and communication.
  • • Profile image (optional): Displayed in the app where applicable.

B. Device-Local Data (Stored Only On Device — Room DB / Local Encrypted Store)

The following items are stored locally and are not uploaded to our servers unless you explicitly enable an opt-in backup feature:

  • • Contacts imported by the user (CSV/XLSX import or device contacts access when the user chooses).
  • • Notes added after calls and call outcome flags set by the user.
  • • Local coins balance and transaction history used for app operations.

These items remain on the device. If you uninstall DialMaster without backing up, this data may be irretrievably deleted.

C. SDK / Telemetry / Analytics Data

We integrate analytics, crash reporting and ad SDKs which automatically collect technical and engagement data:

  • • Device model, OS version and app version.
  • • Advertising identifier (GAID/IDFA) for ad serving and measurement.
  • • IP address (approximate location and fraud checks).
  • • Crash reports and stack traces.
  • • Event logs (screens viewed, ad impressions, subscription events).

D. Purchases & Monetization

When you purchase a subscription or coin pack, we collect:

  • • Purchase token / transaction ID
  • • Subscription plan identifier, dates
  • • Coin allocation history

E. Consent & Preference Data

  • • UMP/IAB consent strings (EU/EEA/UK)
  • • Ad personalization preferences
  • • CCPA do-not-sell / share flags for CA residents

5. Data We Do NOT Collect (Assurances)

To be clear, DialMaster does NOT collect or process the following data:

✕
No call logsWe do not access your device's call history (incoming or outgoing).
✕
No call recordingsWe do not record or transmit audio from calls or the microphone.
✕
No SMSWe do not read, send or store SMS messages.
✕
No hidden dialingDialMaster only launches calls through ACTION_DIAL. The user initiates the final call action.
✕
No contact uploadsContacts remain local unless explicitly opted into a cloud backup.
✕
No sensitive dataWe do not collect health, biometric, or other special categories of personal data.

7. How We Use Your Data

We use personal and technical data for limited, specified purposes:

  • Authenticate accounts (Google Sign-In)
  • Validate purchases
  • Deliver rewarded ads (coin grants)
  • Serve targeted or generic ads
  • Detect and mitigate fraud
  • Crash reporting and product analytics
  • Customer support and dispute resolution

8. Advertising, Mediation, Header-Bidding & RTB

To support a free tier, DialMaster uses an advanced advertising stack comprised of mediation, header-bidding and RTB technologies. This enables multiple demand partners to bid in real time to serve ads. This policy covers mediation layers (e.g., AppLovin MAX), Prebid Mobile, and RTB.

Ads shown only to free users

Paid subscribers receive an ad-reduced or ad-free experience. Rewarded ads are used to grant in-app coins and are subject to fraud detection.

What data may be processed

IP address, device model and OS, advertising identifiers (GAID/IDFA), ad request metadata, and approximate location derived from IP.

Consent & CCPA

EU/EEA/UK users will see a Google UMP/IAB TCF dialog. California residents may opt-out of the “sale” or “sharing” of personal information using in-app settings.

9. Third-Party Services & SDKs

DialMaster integrates third-party services for authentication, analytics, crash reporting, ad serving and mediation. These services include (but are not limited to):

Firebase (Auth, Firestore, Crashlytics)
Google Mobile Ads / AdMob
Google Ad Manager (GAM)
AppLovin MAX
Prebid Mobile
RevenueCat
Unity Ads, ironSource
InMobi, PubMatic, Smaato

10. Local Data (Device-only) – Room DB

By design, DialMaster keeps user contact imports, call notes and coin balances on the device. These items are stored in a local encrypted database (Android: Room + encryption; iOS: secure store). They do not leave your device unless you explicitly opt-in to cloud backup.

11. Data Retention

  • A
    Authentication/profile: retained until account deletion.
  • B
    Purchase records: retained for billing reconciliation (typically up to 7 years).
  • C
    Analytics logs: retained according to provider settings (you may request deletion).
  • D
    Local contacts: remain on your device until deleted or uninstalled.

13. Security Measures

We employ a range of administrative, technical and physical safeguards, including:

HTTPS/TLS EncryptionFirebase App CheckFirestore Security RulesEncryption at RestReward Validation Tokens

14. User Rights & How to Exercise Them

Depending on your jurisdiction, you may have the right to Access, Rectify, Delete, Port, or Restrict/Object to the processing of your data, as well as to Opt-out of targeted advertising.

To exercise any rights, contact support@dialmaster.in.

15. Children's Privacy

DialMaster is not intended for use by children under 16. We do not knowingly collect personal information from children.

16. Cookies & Trackers

Browser cookies are rarely used. Ad/analytics SDKs use mobile identifiers (GAID/IDFA) which you can limit in OS settings.

Contact Information

Developer: ZeengoCorp Innovations
Email: support@dialmaster.in