Skip to content

TxTTone Privacy Policy

Last Updated: August 9, 2026 • Version 2.1

Charles Hall ("we," "our," or "us") operates the TxTTone mobile application (the "App").

This Privacy Policy explains how information is accessed, processed, stored, disclosed, and safeguarded when you use TxTTone.

Please read this Privacy Policy carefully. If you do not agree with this Privacy Policy, do not use the App.

1. Information We Access and Process

1.1 Contact Information

TxTTone may access your device's contact list to allow you to select contacts and assign custom notification sounds or ringtones.

Contact information used by TxTTone for contact-based sound features is processed locally on your device. TxTTone does not transmit your contact list to our servers for contact matching or sound-assignment functionality.

When features that use native per-contact ringtones are enabled, TxTTone may write a ringtone URI to the standard Android CUSTOM_RINGTONE field for an applicable contact. This allows the device's native dialer to use the assigned ringtone.

TxTTone does not modify unrelated contact information for this purpose.

1.2 Notification Information

TxTTone uses Android Notification Access to detect notifications so that it can apply the sound rules you configure.

Android may make notification information available to TxTTone through the notification-listener system. TxTTone uses the information needed for its sound-routing features, which may include:

TxTTone does not intentionally use message bodies as part of its normal sound-selection functionality and does not transmit message bodies to our servers.

Notification processing for sound selection occurs locally on your device.

TxTTone does not operate a server that receives or stores your messages for notification-sound personalization.

1.3 Enhanced Sound Handling and Usage Access

TxTTone provides an optional feature called Enhanced Sound Handling, which may be used with Sound Takeover to improve the timing and reliability of custom notification-sound handling for supported apps.

When Enhanced Sound Handling is enabled, TxTTone may use Android's Usage Access capability to observe limited device usage-event information needed to recognize relevant app activity.

This information may include:

TxTTone uses this information locally to determine when notification-sound handling should be prepared.

TxTTone does not use Usage Access to read the contents of your messages, build an advertising profile of your app activity, or sell your app-usage history.

Usage-event information used by Enhanced Sound Handling is processed locally as needed for feature operation. TxTTone does not transmit raw Usage Access event streams to our servers or third-party analytics services for this purpose.

Enhanced Sound Handling is optional. You may disable the feature within TxTTone or revoke Usage Access through Android system settings.

If Usage Access is not granted, other TxTTone features may continue to work, although Enhanced Sound Handling may be unavailable or less effective.

1.4 Audio Files

TxTTone allows you to select and use audio files as notification sounds and ringtones.

Audio files selected for TxTTone's playback features are stored or accessed locally on your device. We do not upload your sound library to our servers for playback functionality.

You may also record or import custom audio clips within the App. User-created or user-imported audio stored in TxTTone's private app storage is not transmitted to our servers for playback functionality.

You are responsible for the audio content you choose to use.

You may delete private TxTTone audio by removing it within the App or by clearing TxTTone's app data through Android settings.

1.5 Native Ringtone Copies

When TxTTone needs to make an audio file available to Android's native ringtone system, the App may create a managed copy in:

Ringtones/TxTTone/

This is shared device storage.

Files placed in shared storage may remain after TxTTone is uninstalled because Android does not necessarily remove shared media files during app uninstall.

You may manually delete these files using a compatible file manager or media-management application.

1.6 System Settings, Sound Takeover, and Ringtone Handling

Depending on the features you enable, TxTTone may interact with Android's notification, ringtone, contact, and system-setting functionality.

This may include the following:

These actions are performed locally on your device.

Compatibility may vary by application, Android version, device manufacturer, notification configuration, and system settings.

1.7 Purchase and Entitlement Information

TxTTone uses Google Play Billing for optional digital purchases.

Available purchases may include:

Google handles payment processing.

TxTTone may receive purchase-status and entitlement information from Google Play so the App can determine whether you own purchased features.

We do not directly receive or store your full payment-card information.

TxTTone may cache limited entitlement information locally so purchased features can remain available between app sessions. Purchase status may also be revalidated through Google Play.

TxTTone may grant promotional, upgraded, or grandfathered entitlements to eligible users.

When Google Analytics for Firebase is enabled and connected to Google Play, purchase-related events may also be processed for analytics. This may include information such as product identifier, product name, price, currency, and quantity. TxTTone does not directly receive your full payment-card information through this analytics process.

1.8 Usage, Analytics, Advertising, and Diagnostic Information

Core TxTTone sound personalization is primarily performed locally on your device.

However, third-party SDKs integrated into the App may collect, receive, or process certain technical information.

These services may include:

Depending on the service and configuration, technical information may include:

TxTTone does not intentionally send notification message bodies, contact names, phone numbers, contact identifiers, or user audio files to Firebase Analytics for analytics purposes.

TxTTone's production diagnostic logging is designed so that notification message contents, contact or sender identity, phone numbers and contact identifiers, and user audio filenames, file paths, or content URIs are not included in TxTTone's diagnostic logs or custom Crashlytics breadcrumbs.

Production precursor and Enhanced Sound Handling diagnostics do not retain or transmit raw Usage Access event streams, notification extras, notification objects, message contents, or contact information. Technical precursor processing is performed locally on the device for feature operation.

Crashlytics may still receive technical information generated by the application or Android runtime, such as stack traces, app version, device information, and technical application state associated with a crash.

Third-party providers process information according to their own terms and privacy practices.

2. How We Use Information

We use information accessed or processed through TxTTone to:

3. Local Storage and Backups

3.1 Local App Data

TxTTone may store the following information locally on your device:

This locally stored feature information is not transmitted to our servers unless otherwise stated in this Privacy Policy.

3.2 Local Backup

TxTTone may provide a local backup feature that allows you to export supported settings and sound-library information to a backup file.

You choose where that backup file is stored, which may include local storage or a third-party cloud-storage provider you select.

TxTTone does not operate its own cloud backup service for these backups.

Backup files are not intended to contain notification message bodies.

You are responsible for protecting and managing any backup files you create.

3.3 Security

We use reasonable technical measures intended to protect information handled by TxTTone.

Third-party services may use encrypted network connections when transmitting information.

No method of electronic storage, processing, or transmission can be guaranteed to be completely secure.

4. Third-Party Services

4.1 Google AdMob

TxTTone may use Google AdMob to display advertisements to users who do not have an applicable ad-free entitlement.

AdMob may collect, receive, or share information used for advertising, analytics, and fraud prevention. Depending on Google's services and configuration, this may include:

Purchasing Remove Ads or TxTTone Pro may remove advertisements from TxTTone, depending on the applicable entitlement.

AdMob processes information according to Google's applicable privacy policies and advertising controls.

4.2 Firebase Analytics

TxTTone may use Firebase Analytics to understand general App usage and feature engagement.

Firebase Analytics may process information such as:

For Google Play in-app purchases, purchase-related analytics may include information such as product identifier, product name, price, currency, and quantity.

We do not intentionally use Firebase Analytics to collect message bodies, your contact list, or your user audio files.

4.3 Firebase Crashlytics

TxTTone may use Firebase Crashlytics to help diagnose crashes and application failures.

Crashlytics may receive technical information such as:

TxTTone does not attach custom Crashlytics breadcrumbs containing notification message contents, contact or sender identity, phone/contact identifiers, or user audio filenames, paths, or URIs.

TxTTone's production logging is configured to prevent its diagnostic logging paths from exposing this information.

Crashlytics is not used by TxTTone to collect the contents of your messages.

4.4 Google Play Billing

TxTTone uses Google Play Billing for digital purchases and purchase verification.

Google is responsible for processing payment information associated with Google Play purchases.

TxTTone receives only the information needed to determine and maintain the relevant purchase entitlement.

Payment information and transaction records maintained by Google Play are subject to Google's own privacy, retention, and account policies.

5. Permissions and Special Access

TxTTone may request or rely on the following Android permissions, roles, or special-access capabilities depending on the features you use.

Notification Access

Used to detect notifications and apply contact-based, app-based, playlist, Sound Takeover, and related sound rules.

Usage Access / PACKAGE_USAGE_STATS

Optional.

Used by Enhanced Sound Handling to observe limited app-usage events such as package/component activity, event type, and timing so TxTTone can prepare notification-sound handling for supported apps.

Usage Access is not used by TxTTone to read message bodies.

READ_CONTACTS

Used to allow you to select contacts and support contact-based sound and ringtone functionality.

WRITE_CONTACTS

Used when TxTTone needs to write a ringtone URI to a contact's Android CUSTOM_RINGTONE field.

READ_PHONE_STATE

Used for supported call-related features so TxTTone can respond to incoming call state.

TxTTone does not use this permission to record calls or read call audio.

WRITE_SETTINGS

Used when required to support ringtone-related system behavior, fallback behavior, or restoration features.

READ_EXTERNAL_STORAGE / READ_MEDIA_AUDIO

Used where applicable to allow you to select compatible audio files from your device.

Permission requirements vary by Android version.

POST_NOTIFICATIONS

Used on supported Android versions when TxTTone needs permission to post its own notifications.

INTERNET

Used for functionality such as advertising, Google Play Billing, analytics, crash reporting, and related network services.

ACCESS_NETWORK_STATE

Used to determine network connectivity for supported network-dependent services.

Call Screening Role

Optional.

If you choose to grant the Android call-screening role, TxTTone may use it to receive earlier call-state information for supported ringtone-handling features.

You may decline or revoke optional permissions and special access through Android system settings.

Some features may become unavailable when the access they require is disabled.

6. Data Sharing and Disclosure

We do not sell your contact list, notification message bodies, or user audio files.

Information may be disclosed or processed in the following circumstances.

6.1 Service Providers

Third-party service providers may process or receive information for:

For example, AdMob may receive or share certain advertising-related information, including approximate location derived from IP address, app interactions, diagnostic information, and device or other identifiers, as described in this Policy.

These providers operate under their own privacy practices.

6.2 With Your Direction or Consent

Information may be shared when you intentionally direct TxTTone to interact with another application, storage provider, or service, or when you otherwise consent to the disclosure.

6.3 Legal Requirements

We may disclose information where required by applicable law, legal process, court order, or valid governmental request.

6.4 Business Transfers

If TxTTone or its associated business assets are transferred through a merger, acquisition, reorganization, or sale, information associated with the business may be transferred as permitted by applicable law.

7. Children's Privacy

TxTTone is not intended for children under 13.

We do not knowingly seek to collect personal information directly from children under 13 through TxTTone's core local personalization features.

Third-party services integrated into the App may process technical or advertising information under their own policies.

If you are a parent or guardian and believe a child has provided personal information inappropriately, contact us at:

devtexttone@gmail.com

8. Your Choices

8.1 Permissions and Special Access

You may manage TxTTone's permissions and special-access capabilities through Android system settings.

Revoking access may disable features that depend on that access.

8.2 Local Data

You may remove locally stored TxTTone data by:

Some shared-storage ringtone copies and ringtone assignments written to contacts may remain after uninstall and may require manual removal.

8.3 Enhanced Sound Handling

You may disable Enhanced Sound Handling within TxTTone or revoke Usage Access through Android system settings.

8.4 Advertising

Users with an applicable Remove Ads or TxTTone Pro entitlement may receive an ad-free TxTTone experience.

You may also use advertising and privacy controls provided by Android, Google, or applicable advertising providers.

8.5 Purchase Restoration

Where supported, TxTTone may restore or revalidate eligible purchases through Google Play.

9. Data Deletion Requests

TxTTone does not require or provide a separate TxTTone user account.

To request deletion of personal data associated with TxTTone that we control and can reasonably identify, contact:

devtexttone@gmail.com

Please state that your request concerns TxTTone data deletion and provide enough information for us to understand and respond to the request. Do not send passwords, payment-card information, message contents, contact lists, or other unnecessary sensitive information.

Data stored only on your device can generally be deleted without contacting us by:

Some data may require additional local action:

Information processed by Google Play, Firebase, AdMob, or other third-party providers may be subject to those providers' own deletion, retention, legal, fraud-prevention, and account requirements.

Purchase and transaction records maintained by Google Play are controlled by Google and may remain subject to Google's applicable retention requirements even if locally cached TxTTone entitlement information is cleared.

We may retain information where reasonably necessary or legally required for purposes such as security, fraud prevention, dispute resolution, compliance with law, or enforcement of legal rights. Where applicable, we will limit retained information to what is necessary for those purposes.

10. Data Retention

10.1 Local App Data

Local App data is stored on your device until removed through the App, app-data clearing, or uninstall, subject to the exceptions described below.

10.2 Shared Ringtone Files

Files created in Ringtones/TxTTone/ may remain until manually deleted.

10.3 Per-Contact Ringtone Assignments

Ringtone URIs written to a contact's CUSTOM_RINGTONE field may remain after uninstall until changed or cleared.

10.4 Purchase Entitlement Information

Limited purchase-entitlement information may remain associated with your Google Play account according to Google Play's policies and may be cached locally by TxTTone.

10.5 Analytics, Advertising, and Crash Information

Analytics, advertising, diagnostic, purchase-event, and crash information processed by third-party providers is retained according to the applicable settings, legal requirements, and retention practices of those providers.

11. International Data Transfers

Third-party service providers may process information in countries other than the country in which you live.

Where required, those providers are responsible for implementing applicable safeguards for international processing and transfers.

12. Changes to This Privacy Policy

We may update this Privacy Policy when TxTTone's features, data practices, legal requirements, or third-party services change.

When material changes are made, we may notify users through the App, store listing, website, or another appropriate method.

The "Last Updated" date at the top of this Policy indicates when the current version became effective.

13. California Privacy Rights

California residents may have rights under applicable California privacy law, including rights relating to access, correction, deletion, and information about certain disclosures of personal information.

TxTTone does not sell personal information for monetary consideration.

Advertising providers may process information for advertising as described in this Policy. Depending on the circumstances and applicable law, some advertising-related disclosures may be subject to additional California privacy rights.

Where applicable, you may exercise available advertising/privacy controls through your device or Google account.

You may also contact us at:

devtexttone@gmail.com

14. EEA, United Kingdom, and Switzerland

If you are located in the European Economic Area, United Kingdom, or Switzerland, applicable law may provide rights regarding personal data, including rights to:

These rights may be subject to legal limitations and exceptions.

To make a request concerning information controlled by us, contact:

devtexttone@gmail.com

Where consent is legally required for a particular activity, consent will be requested as appropriate rather than assumed solely from use of the App.

15. Contact Us

If you have questions, concerns, data-deletion requests, or other requests regarding this Privacy Policy, contact:

Charles Hall • TxTTone • Privacy Policy • Version 2.1 • August 2026