Your information

Privacy Policy for TouchMute

Last updated: 18 October 2026

Responsible developer / data controller: Igor Vasić (individual publisher). For privacy questions or requests, contact vasicigorjsp@gmail.com.

TouchMute helps prevent accidental screen touches by placing a transparent touch-blocking overlay over other apps. This policy explains how TouchMute handles information when you use the app and when you contact the developer.

Information handled on your device

Touch blocking and settings work offline. TouchMute has no ads and does not require a TouchMute account. Purchases are not active in the current app configuration; RevenueCat is not initialized. A future version may enable optional purchases. When the purchase service is enabled, RevenueCat starts with the app, including for people using Free; its identifier and entitlement checks are not limited to opening the purchase screen. Purchasing, refreshing purchase status and restoring access require network communication. TouchMute does not use a separate advertising or crash-reporting service. RevenueCat processes purchase information, including purchase analytics used to operate the paid plans.

TouchMute saves your settings locally on your device. These include the selected unlock method, volume-button behavior, swipe-down controls option, activation delay, keep-screen-on preference, vibration, lock indicator and automatic-unlock timer. These settings are used only to provide the behavior you choose.

The active touch-blocking state, timers and queued purchase-result messages are held in memory. These messages are not a saved transaction history and do not survive the app process ending. The tutorial video is bundled with the app; playing it does not upload information or require a streaming connection. Android may temporarily preserve the current app screen and tutorial playback position when recreating an activity.

Accessibility access

TouchMute asks you to enable its Accessibility service so it can create a touch-blocking overlay and handle optional Volume-button unlock sequences. While a session is active, it receives Volume-button events to apply your selected behavior. It also uses window-change information, including the window's package and class name, to recognize the system notification panel and dismiss it when swipe-down controls are disabled.

This information is processed on your device for these functions. TouchMute does not store a history of key presses or window changes and does not transmit them. It does not retrieve the text or contents of other apps' windows, capture screenshots, record your screen, read notification contents or record audio.

You choose whether to enable Accessibility access in Android settings. You can turn it off there at any time. Without this access, TouchMute cannot start touch blocking.

Other permissions and controls

Draw over other apps is used for the optional Allow swipe-down controls setting. This allows the touch-blocking layer to remain over app content while compatible system controls can open above it. The basic blocking mode uses the Accessibility overlay. You can revoke Draw over other apps in Android settings.

Vibration permission provides optional brief vibration feedback. TouchMute does not request access to your location, contacts, camera, microphone or media library.

Turning the screen off ends the current TouchMute session. TouchMute is not an Android security lock screen.

Storage, retention and deletion

Settings remain in the app's local storage until you change them, clear the app's storage in Android settings or uninstall TouchMute. Clearing storage or uninstalling removes the app's saved settings from that installation. TouchMute is configured to exclude its app data from Android cloud backup and device transfer.

Session state and timers are not saved as a usage history. The developer has no remote copy of your app settings and cannot retrieve them for you.

Optional purchases and RevenueCat

This section describes the planned purchase service for a future version. It does not describe processing performed by the current inactive configuration. Consult the policy supplied with that version for its final practices. When enabled, Google Play handles payment and purchase confirmation. TouchMute does not receive your full payment-card details. RevenueCat provides purchase verification and entitlement management on the developer's behalf. The SDK generates a random anonymous App User ID and keeps it on your device; this is a purchase-service identifier, not a TouchMute login account.

When the purchase service is enabled, the SDK communicates the identifier, purchase records and Google Play purchase tokens to RevenueCat. Requests also include technical information such as device model/brand, Android and SDK versions, app version and language/locale. These support purchase validation, delivery and restoration of Annual/Lifetime access, service operation and purchase analytics. The app does not supply your name, email address or phone number as RevenueCat customer attributes; automatic advertising-identifier collection and optional SDK diagnostics are disabled. Accessibility key/window information is not used for purchases or sent to RevenueCat.

When the purchase service is enabled, RevenueCat stores purchase-service records on its servers. Its anonymous identifier and customer/entitlement cache are kept in the app's private local storage, separately from TouchMute's user settings. An anonymous identifier still identifies a purchase-service customer; it does not mean that no identifier is collected. Previously confirmed Lifetime access can work offline indefinitely while valid local entitlement data remains; there is no automatic three-day Lifetime cutoff. Annual access lasts until the confirmed expiry available to TouchMute. Initial purchase and restoration require internet. Refunds and revocations are learned when online purchase status is refreshed, so they cannot be detected immediately offline. Reinstallation, cleared app data or another device requires online restoration using the same Google Play account used for the purchase.

RevenueCat states that application data uses TLS in transit and its customer data is stored in AWS data centers in the United States. Processing can therefore involve international transfers. See RevenueCat's privacy information for its service and processing practices and Google's privacy policy for Google's independent handling. The developer remains responsible for requests concerning TouchMute data processed on its behalf.

Clearing app data or uninstalling removes this installation's settings and SDK cache; it does not delete remote purchase records. Purchase-service records are retained as needed to provide and restore access and meet applicable legal obligations; no fixed deletion deadline is promised here. Request access, correction or deletion through vasicigorjsp@gmail.com. We may need sufficient purchase information to locate the relevant anonymous customer record. The developer will review your request and delete information under their control where applicable, including requesting action from the purchase-service provider when relevant. Legal retention exceptions may apply. A data-deletion request does not cancel an Annual subscription, issue a refund or delete Google's own transaction history; manage subscriptions and refund requests through Google Play.

If you contact support

If you email the developer, the developer receives your email address, the contents of your message and any information or attachments you choose to send. This information is used to respond to your request and resolve the issue you report. Email is handled through the email providers involved in delivering and storing the conversation; it is separate from the app's offline operation. Please avoid sending passwords, payment details or information that is not needed for your request.

Support correspondence is retained while needed to handle the request and relevant follow-up, or to meet applicable legal obligations. You may request access, correction or deletion by emailing vasicigorjsp@gmail.com. Requests are assessed under applicable law; information that must be retained for a legal obligation may be kept for that purpose.

Google Play and Android

Google Play, Android and your device manufacturer may independently process information under their own policies. Their operation is separate from the information handled by TouchMute described above.

Changes to this policy

This policy will be updated when TouchMute's information-handling practices change. The update date above identifies this policy version. Questions about this policy can be sent to vasicigorjsp@gmail.com.