Dialward — Privacy Policy

Last updated: 8 September 2026 · Applies to the Android app com.dialward.app, published by ZYRO APPS.

The short version. Your contacts, your call log, and your spam and block lists are read on your phone and are never uploaded, shared, or sold. Dialward has no account and no sign-up. The only information that leaves your device is anonymous crash and usage diagnostics, which we use to find and fix bugs.

1. What stays on your device

Dialward works from data that already exists on your phone, plus a few lists you create yourself. All of it is stored in the app's private storage on your device. None of it is transmitted anywhere.

Your contacts. Read from your phone's address book so an incoming call can show a name instead of a bare number, and so you can search and dial. Dialward keeps no copy of your address book.
Your call log. Read from your phone so the Recent list can show incoming, outgoing, and missed calls. Dialward keeps no copy of your call history.
Your spam list. Numbers you mark as spam, along with any name, category, and report count you enter.
Your block list. Numbers you choose to block.
Your favourites and any call log entries you have hidden.
App settings — your chosen language, whether the caller ID card is enabled, and whether you have completed onboarding.

Uninstalling Dialward deletes all of this permanently. There is no server copy to delete, because one was never made.

2. What leaves your device

Dialward uses two Google services to understand whether the app is working correctly:

Firebase Crashlytics — collects a report when the app crashes, so the crash can be diagnosed and fixed.
Google Analytics for Firebase — collects anonymous usage events, such as which screens are opened and how often the app is launched.

Together, these send the following categories of information:

Category	What it contains	Why
Crash logs	The technical stack trace of a crash, plus the device model and Android version it happened on.	To diagnose and fix bugs.
Diagnostics	App performance and stability information, such as launch times and error states.	To monitor app health.
App interactions	Anonymous events such as screen views and session counts.	To understand which features are used.
Device and other identifiers	A Firebase installation identifier and your device's Advertising ID.	To group the above events by installation.

All of this is transmitted over an encrypted connection. It is used only to analyse and improve Dialward. It is not sold, and it is not shared with advertisers or data brokers. Dialward contains no advertising.

Your Advertising ID is a device identifier managed by Google. You can reset it or opt out of personalised advertising at any time in Settings → Google → Ads on your Android device.

3. What we never collect

To be explicit, none of the following is ever transmitted off your device, to us or to anyone else:

Your contacts, or any name, number, or photo from your address book
Your call log or call history
Your spam list, block list, favourites, or hidden entries
The contents of any call
Your phone number
Your name, email address, or any account credential — Dialward has no accounts
Your precise location

Dialward does not use a shared or crowd-sourced spam database. Numbers are identified only from your own address book and the lists you build yourself, which means nothing about who calls you is ever sent anywhere for lookup.

4. Permissions, and what each one is for

Permission	Why Dialward needs it
`READ_CONTACTS`	To show a caller's name instead of a bare number, and to search your address book.
`READ_CALL_LOG`	To build the Recent calls list and to identify a repeat caller.
`READ_PHONE_STATE`	To detect an incoming call so the caller ID card can appear.
`CALL_PHONE`	To place calls from the dialer.
`ANSWER_PHONE_CALLS`	To answer or reject a call from the caller ID card.
`SYSTEM_ALERT_WINDOW`	To draw the caller ID card over the incoming-call screen.
`POST_NOTIFICATIONS`, `USE_FULL_SCREEN_INTENT`	To show the ringing and ongoing-call notifications.
`FOREGROUND_SERVICE`, `FOREGROUND_SERVICE_SPECIAL_USE`	To keep the caller ID card on screen for the length of the call.
`INTERNET`, `ACCESS_NETWORK_STATE`	Used only to send crash and diagnostic reports described in section 2.
`AD_ID`	Required by Google Analytics for Firebase in order to read the Advertising ID.

Every permission above except INTERNET, ACCESS_NETWORK_STATE, and AD_ID is used entirely on your device. Granting Dialward access to your contacts or call log does not give it, or us, the ability to send that information anywhere.

5. If you set Dialward as your default phone app

Dialward can act as your device's default phone app, which lets it show its own in-call screen and manage calls directly. This does not change what data is collected or transmitted — it only changes which screen your phone shows during a call. You can change your default phone app at any time in your Android settings.

6. Retention and deletion

Data on your device is kept until you delete it. You can remove individual entries from the spam and block lists inside the app at any time, and uninstalling Dialward erases everything it has stored.

Crash and analytics data is retained by Google's Firebase services under their standard retention periods and is then deleted automatically. Because this data is not linked to an account, a name, or a phone number, we cannot look up an individual person's records. If you want your device's analytics data removed, contact us at the address below with your device's Advertising ID and we will pass the deletion request to Google.

You can stop analytics and crash collection entirely at any time by uninstalling the app.

7. Children

Dialward is a general-purpose phone utility intended for users aged 18 and over. It is not directed at children, and we do not knowingly collect information from children.

8. Third-party services

Dialward includes software from Google, whose handling of the data described in section 2 is governed by their own policies:

Dialward integrates no other third-party SDKs, no advertising networks, and no analytics providers beyond those named above.

9. Changes to this policy

If the app's data practices change, this policy will be updated and the date at the top of the page will change with it. Material changes will also be described in the app's release notes on Google Play.

10. Contact

Questions about this policy, or requests relating to your data, can be sent to:

ZYRO APPS
admin@zyroapps.com