Executive Summary

This document maps DialMaster’s data practices to the Google Play Data Safety categories and contains ready-to-publish declarations. App collects minimal personal data and shares limited technical data with advertising & analytics partners for operational and monetization purposes.

1. Data Types Collected (Complete Listing)

Below are the exact categories and examples to declare in Play Console.

Category	Examples	Declared?	Purpose
Personal info	Google account ID, display name, email	Collected	Authentication, account mapping, support
Contacts	Imported contact lists (CSV/XLSX or device contacts)	Not Collected	Stored locally on device only (Room DB)
Call logs	Incoming/outgoing call history	Not Collected	Not accessed or transmitted
Messages (SMS)	SMS inbox/outbox	Not Collected	Not accessed
Audio recordings	Recorded call audio, microphone	Not Collected	Not recorded
Device IDs	Advertising ID, Firebase Instance ID	Collected	Ad delivery, measurement, analytics
IP address	Client IP seen by servers and ad SDKs	Collected	Approx location, fraud prevention, ads
App activity	Screens visited, ad impressions, clicks	Collected	Analytics, UX improvement, ad reporting
Crash logs	Stack traces, crash diagnostics	Collected	Stability and bug fixing
Purchases	Purchase tokens, transaction IDs	Collected	Billing verification, entitlement
Location	Approximate location from IP only	Collected	Ad targeting, regulatory checks

2. Data Explicitly NOT Collected

Contacts: Not uploaded or stored on servers (unless opt‑in backup enabled).
Call logs: Not accessed or transmitted.
SMS / Messages: Not accessed.
Audio recordings & microphone capture: Not recorded by the App.
Precise GPS location: Not collected. Only approximate IP‑derived location.

3. Shared With Third Parties?

Declared: Yes — We share limited technical and advertising data with advertising, mediation, analytics and crash reporting partners.

Purpose of sharing

Ad delivery, auctioning (RTB), frequency capping and personalization (with consent).
Analytics & crash reporting for product improvement.
Fraud detection and reward validation for rewarded ads.

Example partners: AppLovin MAX, Google AdMob, Google Ad Manager (GAM), Prebid Mobile, Unity Ads, ironSource, InMobi, PubMatic, Smaato, Vungle, Playwire, Firebase (Analytics & Crashlytics), RevenueCat (iOS).

4. Encryption & Security

Encryption in Transit: All network traffic uses HTTPS/TLS (TLS 1.2+ recommended) for API calls, SDK transmissions and purchase verification.
Encryption at Rest: Sensitive server data stored in Firestore is encrypted at rest by Google Cloud. Local device storage uses platform encryption (Android: encrypted Room / Keystore; iOS: Keychain / Secure Enclave).

5. Data Deletion Option

Server‑side data

To request deletion of server‑side account data (profile, subscriptions, purchase history), users should email: support@dialmaster.in with the subject line Delete My Account.

Local data

User local data (contacts, notes, coins) can be deleted via the App's UI or by uninstalling the App.

View full Data Deletion Policy →

6. Ready Play Console Field Mapping

Data collected	Personal info; Device IDs; App activity; Purchases; Location (approximate); Crash logs
Data shared	Yes — Advertising & Analytics partners
Encryption in transit	Yes — TLS 1.2+ (HTTPS)
Encryption at rest	Yes — Google Cloud / Local secure storage
User deletion request	Yes — support@dialmaster.in
Sensitive data	No

Terms & Conditions Privacy Policy Contact Support