DialMaster – Smart Auto Dialer & Call Assistant
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@zeengocorp.com
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 Data
When you purchase a subscription or coin pack, we collect:
- Purchase token / transaction ID (for verification).
- Subscription plan identifier, start/expiry dates.
- Coin allocation and redemption history (for auditing).
E. Consent & Preference Data
- UMP/IAB consent strings for EU/EEA/UK users.
- Ad personalization preference (personalized / non-personalized).
- CCPA do-not-sell / share flag for California residents.
5. Data We Do NOT Collect (Assurances)
To be clear, DialMaster does NOT collect or process the following data:
- No call logs: We do not access your device’s call history (incoming or outgoing).
- No call recordings: We do not record or transmit audio from calls or the microphone.
- No SMS: We do not read, send or store SMS messages.
- No background call tracking or hidden dialing: DialMaster only launches calls through ACTION_DIAL — the user initiates the final call action.
- No contact uploads: Contacts remain local unless you explicitly opt into a cloud backup feature (opt-in only).
- No sensitive personal data: We do not collect health, biometric, or other special categories of personal data.
6. Legal Bases for Processing (EU / GDPR)
Where applicable (e.g., EU residents), we rely on the following legal bases:
- Consent: For personalized advertising, optional backups, and UMP/IAB consent flows.
- Contract: Processing necessary to perform our contract with you (e.g., provide subscription benefits, in-app purchases, and entitlement checks).
- Legitimate interests: For fraud prevention, app analytics (improving product reliability), and security — balanced against user rights.
You may withdraw consent at any time for future processing, without affecting prior lawful processing.
7. How We Use Your Data
We use personal and technical data for limited, specified purposes:
- Authenticate accounts and map subscriptions (Google Sign-In + Firebase).
- Validate purchases and enforce subscription entitlements (Play Store, App Store).
- Deliver and validate rewarded ads (coin grants).
- Serve ads (personalized or non-personalized depending on consent) to free-tier users; paid subscribers receive reduced or no ads as described in the app settings.
- Detect and mitigate fraud (reward spoofing, purchase tampering).
- Crash reporting and product analytics to improve stability and UX.
- Customer support and dispute resolution.
We never use local contacts or notes for ad targeting or analytics unless you explicitly consent to a backup that transmits that data to our servers.
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 in the App. This policy is written to be technology-agnostic and future-proof — it covers mediation layers (e.g., AppLovin MAX), Prebid Mobile header-bidding, server and client side bidding, real-time bidding (RTB), and any equivalent future ad tech integrations.
Ads shown only to free users
Ads are displayed to free-tier users to keep the core application free to use. Paid subscribers receive an ad-reduced or ad-free experience according to the subscription tier they select. Rewarded ads are used to grant in-app coins and are subject to fraud detection and validation.
What data may be processed by ad partners
- IP address, device model and OS, app version.
- Advertising identifiers (GAID/IDFA).
- Ad request metadata (ad unit ID, impressions, clicks, rewarded events).
- Approximate location derived from IP (not GPS unless expressly requested).
Consent & the UMP / IAB TCF
EU/EEA/UK users will be shown a consent dialog (Google UMP / IAB TCF compatible). If you decline personalized ads, you will still receive non-personalized ads. You may change consent preferences in App Settings.
CCPA & California Residents
California residents may opt-out of the “sale” or “sharing” of personal information by using our in-app settings or contacting support. We will honor validated requests in accordance with applicable law.
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, Cloud Functions, Analytics, Crashlytics)
- Google Mobile Ads / AdMob
- Google Ad Manager (GAM)
- AppLovin MAX (mediation)
- Prebid Mobile (header-bidding)
- Demand partners / DSPs (AppLovin, Unity Ads, ironSource, InMobi, PubMatic, Smaato, Vungle, Playwire)
- RevenueCat (subscription management across platforms)
- Other analytics and fraud prevention providers
Each third party has its own privacy policy and may independently collect and process data. We recommend you review their policies for details about their data handling practices. Where required by law, we enter data processing agreements and appropriate safeguards to govern transfers and processing.
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.
If you enable cloud backup, we will request separate opt-in consent, inform you of the backup provider, and provide a clear recovery and deletion process.
11. Data Retention
We retain data only as long as necessary for the stated purposes and to comply with legal obligations:
- Authentication/profile: retained until account deletion.
- Purchase/subscription records: retained for billing reconciliation and legal compliance (typically up to 7 years where required by law).
- Analytics/crash logs: retained according to our analytics provider settings (you may request deletion).
- Local contacts & notes: remain on your device until you delete them or uninstall the App.
13. Security Measures
We employ a range of administrative, technical and physical safeguards to protect data, including:
- HTTPS/TLS encryption for all network transmissions.
- Firebase App Check to mitigate unauthorized clients.
- Firestore security rules and authenticated endpoints for server data.
- Encryption at rest for sensitive server data where feasible.
- Reward validation tokens and anomaly detection for ad rewards.
No system is perfectly secure; if a breach occurs we will follow our incident response procedures and notify affected users where required by law.
14. User Rights & How to Exercise Them
Depending on your jurisdiction, you may have the following rights:
- Access: request a copy of your account profile data.
- Rectification: correct inaccurate information.
- Deletion: request erasure of server-side data.
- Portability: request export of server-side account data (not local contacts unless backup enabled).
- Restriction/Objection: restrict or object to certain processing (e.g., legitimate interest processing).
- Opt-out: opt out of targeted advertising (via settings or contacting support).
To exercise any rights contact support@zeengocorp.com. We will verify requests to prevent unauthorized access.
15. Children’s Privacy
DialMaster is not intended for use by children under the age of 16. We do not knowingly collect personal information from children. If you become aware that a child under the applicable age has provided us with personal data, contact us and we will take steps to remove such data.
17. Purchases, Subscriptions & Billing
All purchases are processed by platform billing providers (Google Play / Apple App Store). We only store purchase tokens and subscription status for entitlement verification and fraud prevention. We do not process or store payment card details.
Refunds: Platform stores (Google / Apple) handle refunds. Contact the store for refund requests; we will assist where feasible.
Subscription behaviors such as auto-renewal, price changes and cancellation are governed by the store’s policies. We recommend reviewing the platform billing FAQ for details.
18. Rewards, Coins & Fraud Prevention
DialMaster includes an in-app coin system:
- 1 coin = 1 contact import (per product design).
- Rewarded ad grant example: 1 rewarded ad = 50 coins (configurable and shown in-app).
- Coins are non-transferable and non-refundable.
We implement reward validation and anti-fraud controls. Attempted manipulation or reward spoofing may result in coin reversal, temporary suspension or account termination.
19. Account Deletion, Data Export & Portability
To delete your server-side account data, contact support@zeengocorp.com with subject “Delete My Account”. We will respond and begin the deletion process. Device-local data (contacts & notes) must be removed via the app UI or by uninstalling the app unless you enabled cloud backup — in which case the backup will be deleted subject to the backup provider’s retention policies.
20. Dispute Resolution & Governing Law
These terms and this privacy policy are governed by the laws of the jurisdiction where the developer is domiciled, unless otherwise required by local law. For users in specific jurisdictions, local consumer protection laws may apply. Any disputes will first be attempted to be resolved through good-faith negotiation with support.
21. Amendments to This Policy
We may update this policy to reflect product changes, legal updates, or partner changes. Where changes are material, we will notify users via the App and update the “Last Updated” date at the top of this page.
22. Contact Information
If you have questions about this policy or want to exercise your rights, contact us:
Support: support@zeengocorp.com
Developer: ZeengoCorp Innovations (a registered company)
Website: https://www.zeengocorp.com
Advertising Partners We Work With
The App uses mediation and header-bidding with multiple partners. Below is a representative list — check the in-app “Advertising Partners We Work With” page for a live list and links.
- AppLovin (MAX)
- Google AdMob
- Google Ad Manager (GAM)
- Prebid Mobile
- Unity Ads
- ironSource
- InMobi
- PubMatic
- Smaato
- Vungle
- Playwire
- Other demand partners integrated via MAX / Prebid
Each partner maintains its own privacy policy. The data they may collect typically includes advertising identifiers, IP address, device model, app and ad interactions, and timestamps used for real-time auctions.