TrustDialer

Privacy Policy

Last updated: October 3, 2026

This page holds the privacy policies of two Android apps from the same developer:

TrustDialer privacy policy

This Privacy Policy applies to the Google Play build of TrustDialer. Section 15 also covers the TrustDialer website, support requests, and direct-download licenses.

The free tier of the Google Play build shows banner ads provided by Google (Google Mobile Ads / AdMob). Section 7 explains what that means for your data.

1. Who this policy covers

TrustDialer is an Android phone app designed to be used as a default dialer.

This policy describes how the Google Play build of TrustDialer accesses, uses, stores, and shares data.

Contact for privacy questions:

2. Summary

TrustDialer is designed as a local-first app.

In the current Google Play build:

  • there is no TrustDialer account
  • there is no automatic TrustDialer cloud sync
  • apart from Google Play billing (section 9), the only third-party SDK that sends data off the device is Google’s advertising SDK, used for free-tier banner ads (see section 7); there is no separate analytics or crash-reporting SDK
  • there is no remote upload of contacts or call history to TrustDialer-operated servers as part of normal app use
  • SMS backup, SMS restore, caregiver SMS alerts, and TrustDialer messaging shortcuts are not included

3. Information the app may access on your device

Depending on the Android role and permissions you grant, TrustDialer may access information stored on your device, including:

  • contacts
  • call history and missed calls
  • blocked-number state where Android allows dialer apps to manage it
  • filtered-call review entries created locally by the app after it rejects a call
  • backup data and diagnostics data that you choose to create locally
  • an optional emergency medical card that you or a caregiver fill in (see section 8)

TrustDialer uses this information to provide visible phone-app features such as calling, recents, favorites, speed dial, call filtering, protected family modes, local backup, and diagnostics.

4. How TrustDialer uses data

TrustDialer uses data on-device to:

  • show contacts, favorites, recent calls, and missed calls
  • let you place and receive calls through the dialer experience
  • support whitelist and blacklist call-filtering behavior
  • power grandma mode, kid mode, protected launcher, and emergency features
  • create encrypted backups and restore previews for supported Play-build data
  • generate local diagnostics reports when you ask for them

5. What TrustDialer does not do by default

In the current Google Play build, TrustDialer does not:

  • create a TrustDialer cloud account for you
  • sell your personal data
  • use analytics or crash-reporting SDKs
  • send your contacts, call history, backups, caregiver settings, or medical card to the advertising SDK
  • run automatic cloud backup of contacts or call history
  • upload your contacts, call logs, or filtered-call history to TrustDialer-operated servers as part of normal app use

6. When data may leave your device

Apart from the advertising described in section 7, data leaves your device only when you explicitly choose an action that shares or exports it, such as:

  • exporting or sharing a backup file
  • sharing a diagnostics report
  • viewing free-tier ads, which are requested from Google as described in section 7
  • opening another app through email, map, messaging, WhatsApp, or Viber intents

When you choose one of these actions, the third-party app or provider you select may handle the shared data under its own privacy policy.

7. Advertising

If you use the free tier, TrustDialer shows banner ads delivered by the Google Mobile Ads SDK (AdMob), operated by Google.

  • Ads appear only in the standard interface on the keypad, call history, and contacts screens. No ad is shown during a call, on the emergency medical card, or anywhere in grandma mode or kid mode.
  • TrustDialer Plus subscribers do not see ads.
  • To serve and measure ads and prevent fraud, Google’s SDK may collect device identifiers such as the Android Advertising ID, approximate location derived from your IP address, app interactions with ads, and diagnostic information. The app declares the com.google.android.gms.permission.AD_ID permission and the Android Privacy Sandbox advertising permissions that the SDK needs.
  • Google processes this data under its own privacy policy: https://policies.google.com/privacy. For how Google uses data from apps that use its services, see https://policies.google.com/technologies/partner-sites.
  • Where the law requires consent (for example in the EEA, the UK, and Switzerland), TrustDialer uses Google’s User Messaging Platform to ask for your advertising consent before ads are requested. You can change that choice later with the ad privacy choices button on the TrustDialer Plus screen.
  • You can reset or delete your Advertising ID, or opt out of personalized ads, in Android settings under Privacy > Ads (or Google > Ads on some devices).

The direct-download and Huawei builds of TrustDialer show no ads and do not request the Advertising ID.

8. Emergency medical card (health data)

TrustDialer can store an optional emergency medical card so first responders can read it without unlocking the phone. It is off by default and is filled in only if you or a caregiver choose to. It can hold your name, date of birth, preferred language, blood type, allergies, medications, medical conditions, and free-text emergency notes.

  • The card is stored only on your device, in TrustDialer’s private app storage.
  • It is never uploaded, synced, sent to TrustDialer, or shared with the advertising SDK or any other SDK.
  • It is included in a backup only when you select that section, and backups are encrypted with the password you choose.
  • While the card is enabled it is readable from the lock screen by anyone holding the phone. That is the purpose of an emergency card and why it is off until someone turns it on.
  • Turning the card off in settings stops it being shown; clearing the fields deletes the stored values.

9. Google Play billing and subscriptions

TrustDialer Plus subscriptions in the Google Play build are handled through Google Play billing.

TrustDialer can read subscription status needed to unlock features in the app, but payment processing is handled by Google Play rather than by TrustDialer directly.

For Google Play app review, TrustDialer Plus can also be unlocked temporarily with a review access code. The code is checked on the device only; entering it sends nothing to TrustDialer or any other service.

This policy is linked from the Google Play store listing and inside the app under Settings > Version > Privacy policy.

10. Backups and diagnostics

Backups and diagnostics are user-initiated features.

  • backup files are created only when you choose to export them
  • encrypted backups use the password that you choose
  • diagnostics sharing happens only when you explicitly share a report
  • filtered-call review history stays local unless you choose to share it indirectly, such as through screenshots or exported reports

11. Data retention and deletion

TrustDialer stores its local app data on your device until you delete it, overwrite it, uninstall the app, or use in-app controls that clear or replace it.

Because the current Google Play build does not create a TrustDialer cloud account or TrustDialer cloud backup, TrustDialer does not maintain a separate server-side account data store for normal app use.

Data collected by Google’s advertising SDK is retained and deleted under Google’s policies. You can reset or delete your Advertising ID in Android settings at any time. To ask about deleting any data related to TrustDialer, email support@trustdialer.com.

12. Security

TrustDialer is designed to minimize unnecessary data movement.

Security measures in the current app design include:

  • local-first storage for core phone data used by the app
  • password-protected encrypted backup export when you choose to create a backup
  • no analytics or crash-reporting SDKs; the advertising SDK communicates with Google over encrypted (HTTPS) connections

No mobile app can guarantee absolute security. You remain responsible for protecting your device, screen lock, backup password, and any third-party service you choose for shared files.

13. Android roles and permissions

Because TrustDialer is a dialer, some features depend on Android roles and permissions, including:

  • default dialer role
  • contacts access
  • call log access
  • calling-related permissions
  • notifications and incoming-call presentation permissions

TrustDialer requests these only to support user-visible phone and support features in the Play build.

14. Children and family use

TrustDialer includes caregiver-oriented and family-oriented features such as grandma mode and kid mode.

However, the app is intended to be configured and managed by an adult, parent, caregiver, or other responsible device owner. It is not a child-only social network, cloud account, or advertising platform. TrustDialer is not directed at children under 13, and no ads are shown in kid mode.

15. Website, support, and direct-download licenses

This section covers the TrustDialer website at https://trustdialer.com and the direct-download (TrustDialer Full) build distributed there. It does not change anything above about the Google Play build.

The website may receive information that you submit or that normal website operation creates:

  • your name, email address, and message when you contact support
  • your name and email address when you request a trial license or direct-download access
  • order, billing, and license details when you buy a website license
  • server logs with IP address, browser information, requested pages, and basic security records
  • diagnostics reports, screenshots, or files that you choose to send to support

This information is used to:

  • answer support requests
  • issue, deliver, validate, and support trial and paid website licenses and direct downloads
  • prevent abuse and protect the website, for example by limiting repeated trial requests (the rate limit uses a one-way hash of your email and IP address that expires after one hour)
  • keep business, accounting, and security records

Payments for website licenses are processed by the payment provider you choose at checkout, such as Stripe, PayPal, Revolut, Wise, or bank transfer. TrustDialer does not receive or store your full card details. Each provider handles payment data under its own privacy policy.

Website information may also be processed by hosting and email providers when that is needed to operate trustdialer.com.

Website licenses are checked on the phone. Entering a license in the app does not send it to TrustDialer. The direct-download build shows no ads and does not request the Advertising ID.

Support, order, and license records are kept only as long as needed to provide licenses and support, prevent abuse, and meet legal and accounting obligations. Server logs are kept for a limited period for security. To ask for access to or deletion of your website records, email support@trustdialer.com.

16. Changes to this policy

This policy may be updated when TrustDialer changes its data practices, distribution channels, or Play-build behavior.

When the policy changes, the date at the top of this page is updated.

17. Contact

For privacy questions about TrustDialer or the TrustDialer website, use:

TrustDialerSms privacy policy

TrustDialerSms section last updated: October 2, 2026

This Privacy Policy applies to the Google Play build of TrustDialerSms. Section S15 also covers the direct-download and Huawei builds and support requests.

The free tier of the Google Play build shows banner ads provided by Google (Google Mobile Ads / AdMob). Section S7 explains what that means for your data.

S1. Who this policy covers

TrustDialerSms is an Android SMS and MMS app designed to be used as your default SMS app. It comes from the same developer as the TrustDialer phone app.

This policy describes how the Google Play build of TrustDialerSms accesses, uses, stores, and shares data.

You can open this policy from Setup > Privacy inside the app. It is published on the TrustDialer website at https://trustdialer.com/privacy-policy/, next to the TrustDialer policy.

Contact for privacy questions:

S2. Summary

TrustDialerSms is designed as a local-first app. Your messages and contacts stay on your phone.

In the current Google Play build:

  • there is no TrustDialerSms account and no sign-in
  • there is no automatic TrustDialerSms cloud sync or cloud backup
  • the developer runs no server that receives your messages, contacts, attachments, or settings
  • there is no analytics, crash-reporting, or telemetry SDK
  • apart from Google Play billing (section S9), the only third-party SDKs that send data off the device are Google’s advertising SDK and its consent SDK, used for free-tier banner ads (see section S7)
  • TrustDialerSms reads your SMS and MMS messages only while it is your default SMS app (see section S8)
  • a message is sent only when you tap send in the composer or reply from a notification

Messages you send and receive travel through your mobile carrier, as with any SMS app.

S3. Information the app may access on your device

Depending on the Android role and permissions you grant, TrustDialerSms may access information stored on your device, including:

  • SMS and MMS messages in Android’s message storage, while TrustDialerSms is your default SMS app
  • contact names and phone numbers
  • photos you pick for MMS attachments through Android’s picker
  • Android’s blocked-numbers list, plus optional names and notes you add to blacklist entries
  • SIM information on dual-SIM phones, so you can choose which SIM sends a message
  • notification settings
  • backup files you choose to export or restore
  • app settings such as language, theme, drafts, the phone name used in backup file names, and auto-delete rules
  • blocked-number details (numbers, names and notes) shared on your phone by the TrustDialer app, if it is installed (see section S8)

S4. How TrustDialerSms uses data

TrustDialerSms uses this data on your device to:

  • show your conversation inbox and message threads, and search them
  • send the SMS and MMS messages you write and show their delivery status
  • receive new messages and show notifications with reply and mark-read actions
  • show contact names and suggest recipients while you write
  • send from the SIM you choose on dual-SIM phones
  • pin, archive, mute, and block conversations, and keep your blacklist
  • delete messages when you ask, or through an auto-delete rule you turn on (see section S8)
  • create and restore encrypted backups when you ask (see section S10)
  • open the right conversation when you start a message from TrustDialer

S5. What TrustDialerSms does not do

In the current Google Play build, TrustDialerSms does not:

  • create a TrustDialerSms cloud account for you
  • sell your personal data
  • use analytics, crash-reporting, or telemetry SDKs
  • upload your messages, contacts, attachments, or backups to TrustDialerSms-operated servers
  • give your messages, contacts, attachments, blacklist entries, or backups to the advertising SDK or to advertisers
  • send messages without your action
  • run automatic cloud backup of your messages or contacts

S6. When data may leave your device

Apart from the advertising described in section S7 and the Google Play billing described in section S9, data leaves your device only when you choose an action that sends, shares, or exports it, such as:

  • sending an SMS or MMS, which travels through your mobile carrier to the people you write to
  • sharing or forwarding a message, conversation, or attachment to an app you choose
  • exporting a backup to a destination you choose (see section S10)
  • using spam-report search, which opens a Google web search for the sender’s number in your browser
  • opening this privacy policy from the app, which loads https://trustdialer.com/privacy-policy/ in your browser

When you choose one of these actions, the app or provider you select handles the data under its own privacy policy.

S7. Advertising

If you use the free tier of the Google Play build, TrustDialerSms shows banner ads delivered by the Google Mobile Ads SDK (AdMob), operated by Google.

  • Ads appear only in the Inbox and inside conversations. Setup, backup, help, and the message composer stay ad-free.
  • TrustDialerSms Plus subscribers do not see ads.
  • Ad requests do not include your messages, contacts, attachments, or blacklist. TrustDialerSms never gives SMS, MMS, or contact data to the advertising SDK.
  • To serve and measure ads and prevent fraud, Google’s SDK may collect device identifiers such as the Android Advertising ID and app set ID, approximate location derived from your IP address, app interactions, and diagnostic information. The app declares the com.google.android.gms.permission.AD_ID permission and the Android Privacy Sandbox advertising permissions that the SDK needs (ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, ACCESS_ADSERVICES_TOPICS).
  • Google processes this data under its own privacy policy: https://policies.google.com/privacy. For how Google uses data from apps that use its services, see https://policies.google.com/technologies/partner-sites.
  • Where the law requires consent (for example in the EEA, the UK, and Switzerland), TrustDialerSms uses Google’s User Messaging Platform to ask for your advertising consent before ads are requested. You can change that choice later with the Privacy choices button on the TrustDialerSms Plus screen.
  • You can reset or delete your Advertising ID, or opt out of personalized ads, in Android settings under Privacy > Ads (or Google > Ads on some devices).

The direct-download and Huawei builds of TrustDialerSms show no ads and never start the advertising SDK.

S8. SMS, MMS, and contacts

Working as your SMS app is the core of TrustDialerSms, so message access follows these rules:

  • Android gives TrustDialerSms access to your SMS and MMS messages when you make it your default SMS app. Before Android shows that prompt, or any SMS permission prompt, TrustDialerSms shows a “Messages and contacts” notice that explains the access. You can choose Continue or Not now.
  • TrustDialerSms asks for SMS permissions only while it is your default SMS app. If you make another app your default SMS app, TrustDialerSms stops reading your messages, including for the inbox, backup export, and message counts.
  • Your messages stay in Android’s message storage on your phone, and your contacts stay in Android’s contacts. TrustDialerSms does not copy them to any server.
  • While TrustDialerSms is your default SMS app, it downloads incoming picture messages (MMS) from your mobile carrier through Android’s MMS service and stores them only on your device, in Android’s message storage. Nothing in this goes to TrustDialerSms.
  • TrustDialerSms deletes messages only when you ask it to, or through an auto-delete rule you turn on (a TrustDialerSms Plus feature in the Google Play build). Auto-delete removes messages older than the age you choose and skips messages you have locked.
  • If TrustDialer, the phone app from the same developer, is installed on the same phone, TrustDialerSms can read the blocked-number details that TrustDialer shares on the device, and keeps blacklist names and notes in step with it. This exchange happens only between the two apps on your phone, through Android interfaces protected by a TrustDialer permission. Nothing in it goes over the network.

S9. Google Play billing and subscriptions

TrustDialerSms Plus is an optional yearly subscription in the Google Play build, handled through Google Play billing. It removes ads and unlocks Backup & restore and Auto-delete.

TrustDialerSms reads the subscription status needed to unlock these features and remembers the last status on your device, so Plus stays available while Google Play billing reconnects. Payment processing is handled by Google Play rather than by TrustDialerSms, and TrustDialerSms does not receive your payment details. You can manage or cancel the subscription in Google Play.

For Google Play app review, TrustDialerSms Plus can also be unlocked temporarily with a review access code. The code is checked on the device only; entering it sends nothing to TrustDialerSms or any other service.

This policy is linked from the Google Play store listing and inside the app under Setup > Privacy.

S10. Backups

Backup & restore is a TrustDialerSms Plus feature in the Google Play build. Backups are user-initiated:

  • backup files are created only when you choose to export them
  • each backup is encrypted with a password that you choose
  • a backup can include app settings, contacts, and messages; messages are included only while TrustDialerSms is your default SMS app
  • the file goes only to the destination you pick: a folder through Android’s file picker, Google Drive, or Gmail through Android’s share sheet. That provider stores the file under its own privacy policy, and TrustDialerSms does not operate it.
  • restoring a backup writes the sections you select back to this phone

S11. Data retention and deletion

TrustDialerSms stores its own data, such as settings, drafts, blacklist names and notes, auto-delete rules, and cached attachment files, in its private storage on your device until you delete it, clear the app’s storage, or uninstall the app.

Your messages and contacts are kept in Android’s own message and contacts storage, not inside TrustDialerSms. Uninstalling TrustDialerSms does not delete them; delete them in your messaging app or contacts app.

Because the Google Play build does not create a TrustDialerSms cloud account or TrustDialerSms cloud backup, TrustDialerSms does not keep a server-side copy of your data.

Data collected by Google’s advertising SDK is retained and deleted under Google’s policies. You can reset or delete your Advertising ID in Android settings at any time. To ask about deleting any data related to TrustDialerSms, email support@trustdialer.com.

S12. Security

TrustDialerSms is designed to minimize unnecessary data movement.

Security measures in the current app design include:

  • local-first storage for messages, contacts, and settings
  • password-protected encrypted backup export when you choose to create a backup
  • no analytics or crash-reporting SDKs; the advertising SDK communicates with Google over encrypted (HTTPS) connections

No mobile app can guarantee absolute security. You remain responsible for protecting your device, screen lock, backup password, and any third-party service you choose for shared files.

S13. Android roles and permissions

Because TrustDialerSms is an SMS app, it uses these Android roles and permissions:

  • default SMS app role
  • SMS permissions to send, read, and receive SMS, and to receive and download incoming MMS (SEND_SMS, READ_SMS, RECEIVE_SMS, RECEIVE_WAP_PUSH, RECEIVE_MMS)
  • contacts, to show names, suggest recipients, and restore contacts from your backups
  • phone state, to let you choose the SIM on dual-SIM phones
  • notifications
  • start after a restart, so scheduled auto-delete keeps running
  • the TrustDialer contact-groups permission, for the on-device exchange with TrustDialer (see section S8)
  • internet and network-state access, Google Play billing, and the advertising permissions described in section S7, used by Google’s advertising, consent, and billing libraries

TrustDialerSms does not request location, camera, microphone, call-log, or storage permissions. You choose attachments through Android’s picker.

TrustDialerSms requests these only to support its visible messaging features. You can deny optional permissions such as contacts or phone state; some features are then limited.

S14. Children

TrustDialerSms is a general-purpose messaging app intended for adults. It is not directed at children.

S15. Direct-download and Huawei builds, and support requests

This policy is written for the Google Play build. The direct-download and Huawei builds of TrustDialerSms work the same way on the device, with these differences: they show no ads, never start the advertising or consent SDKs, do not use Google Play billing, and include all features without a subscription.

If you contact support by email, we receive your email address and the content of your message and use them to answer you.

S16. Changes to this policy

This policy may be updated when TrustDialerSms changes its data practices, distribution channels, or Play-build behavior.

When the policy changes, the date at the top of this page is updated.

S17. Contact

For privacy questions about TrustDialerSms, use: