Your data and choices

Privacy policy

Notice version 2026-10-14-regional · Updated 26 October 2026 · Contact: kunal26das@gmail.com

This policy describes the Touché Android app and this support website. Touché is operated by its developer, reachable at the address above. Available services depend on the app build and configuration; builds with purchasing and advertising disabled do not activate those services.

Intended audience and age information

Touché is a general-purpose notification utility intended for people aged 13 and over. It does not ask for your age or date of birth. An installation without an earlier age choice is not treated as a confirmed adult.

Some upgraded installations retain an age band selected in an earlier version, stored only on the device and excluded from Android backup. Touché does not ask for a new choice or provide a way to change that saved band. If the earlier choice was Under 13, the app keeps local notification controls and history available without initializing Firebase, RevenueCat, Google’s consent platform or the advertising SDK. Purchase prompts, cloud sign-in, cloud sync and cached paid processing remain inactive. Saved history, rule configurations and previously created provider records are not deleted by this restriction.

Where no age was collected, or an earlier selection was 13–17, Touché uses conservative under-age settings with Google’s consent and advertising services. This restricted-treatment signal is supplied to those services; Touché does not send a birthday or the saved age band as an account or purchase profile attribute. Ads for these sessions are not personalized. Required provider privacy choices remain separate from Touché’s notification and Accessibility permissions. Optional usage analytics and crash-report sharing are unavailable when an earlier saved band is 13–17 or Under 13, or the local eligibility state cannot be read. No new age is collected or inferred from a privacy choice.

A parent or guardian can use the support and deletion instructions for a child’s information from an earlier version. External pages opened in a browser have their own request processing, including the website processing described below.

Notifications and device settings

With Android notification access, Touché reads available notification titles, messages, sender app and category identifiers, timestamps, formats and related metadata. It saves bounded history and uses your choices to request dismissal after delivery. Protected notifications, including calls and alarms, are kept. Android and the source app may limit the information available.

Touché reads eligible installed-app identities and icons to show its app list. Search terms, local notification counts, saved history, advanced profiles, keyword conditions and schedules stay on the device. Notification content and app inventories are not supplied as advertising, billing or usage-analytics parameters.

The optional Accessibility service reads text, app and notification-category names, and switch states on supported Android Settings screens to apply only the notification-setting changes you choose after tapping Apply. It also checks the active app and window focus to stop when you leave Settings. Accessibility data, operation results and consent are processed only on your device and are not uploaded, shared or used for advertising. The app explains this access on first entry and before setup; choosing Not now leaves notification history and auto-dismiss available. Granting access does not apply pending changes. You can turn off notification access and the separate Accessibility service in Android Settings.

Optional on-device assistance

In builds that include on-device assistance, Pro users can choose to download AI components for notification catch-up and search by meaning. Recognized rule requests are interpreted directly on the device, and cleanup suggestions use local counts; those tools need no AI download. Processing runs on the device, including language identification. The language identifier does not send text, language labels or usage metrics to a provider. Requests, notification text, generated drafts, digest excerpts and search embeddings are not sent to an AI server, advertising services, billing providers or usage analytics. Cleanup suggestions use local notification counts and examples. Suggestions do not change notification rules until you review and save them.

Google Play delivers the app and optional AI adapter code. Model files are downloaded from Hugging Face and its content-delivery providers over HTTPS after you choose Download. Those providers receive network request information such as your IP address and the requested model file; the download does not include notification content or AI requests. Models are stored in private, backup-excluded app storage and can be removed from the AI screen. Search embeddings are held only in app memory so an interrupted search can resume. The cache expires after ten minutes without use and is cleared when you start a new chat, your account or Pro access changes, or its model is removed or replaced. Deleted or changed source notifications invalidate related entries and results. Closing the assistant stops model processing; it does not keep a search running in the background. Chat messages are held only for the current conversation and are not saved to disk. Saved rules remain when a model is removed. Future model revisions require an app update and a new explicit download. Subscription verification can require internet even after model setup.

Storage, retention and export

Free use keeps the latest 200 captures. Pro supports up to 5,000 retained entries during paid capture. After paid access ends, previously retained paid entries remain readable alongside up to 200 rolling free captures, with an absolute limit of 5,200. Expiry alone does not erase saved history or advanced-rule configurations. Old entries can be replaced as the applicable limit is reached; deleted or previously pruned entries cannot be recovered.

Android app backup and device transfer are disabled for Touché’s private app data. Clearing app storage or uninstalling removes local history and settings. Turning off notification access stops new captures but does not delete saved history. Notification history is not a complete backup of your device notifications.

Pro export writes a CSV containing saved notification text, timestamps, identifiers and outcomes to the document location you choose. A selected cloud document provider may upload that file under its own policy. Exported copies are outside Touché’s private storage; you control where they are stored and shared and must delete them separately.

Optional account and preference sync

Google sign-in is optional. It is unavailable on installations retaining an earlier Under 13 choice. If you use it, Firebase Authentication processes your sign-in identity, such as your account identifier, email and available profile information. Cloud Firestore stores your pause choice and basic app/category auto-dismiss choices, including package names, category identifiers and synchronization timestamps. These identifiers can reveal which apps or categories you configured.

Cloud preferences are associated with your account and protected by owner-only access rules. The Firestore database is configured in Mumbai, India; authentication and other provider processing can occur elsewhere. Signing out stops preference syncing but does not delete existing cloud records. Local history, notification text, search queries, counts, channel labels, advanced profiles and Accessibility information are not included in preference sync. See Firebase privacy and security and Google’s Privacy Policy.

Purchases

When purchasing is enabled for an eligible installation, Google Play handles purchases and RevenueCat verifies and restores purchase access. These services process purchase tokens, product and transaction information, entitlement status, an app user identifier, and relevant device/network information. Touché does not receive your payment-card details. Google Play remains responsible for payment ownership. Without Touché sign-in, RevenueCat uses a generated anonymous app identifier. If you optionally sign in with Google inside Touché, the app sends your opaque Firebase account identifier to RevenueCat to recognize the same account for purchase access across installations and purchase reporting. Signing out switches the app back to a guest purchase session without cancelling a Play subscription.

The account identifier is used for RevenueCat identity. Touché does not send RevenueCat your email, Google or Firebase authentication tokens, notification text, rules or app inventory, and does not add profile information as customer attributes. A local cache keeps previously confirmed access for the matching account session for a limited period so a background notification service does not need to start a billing network request. See RevenueCat’s Privacy Policy and Google’s Privacy Policy.

Advertising and privacy choices

When enabled for eligible free use, Google AdMob can show a sponsored card in the Apps grid. Ads are excluded from notification history, search results, notification details and access-consent screens. Pro and the separate ad-removal purchase suppress these ads. An unresolved purchase status does not enable ads.

Google’s advertising SDK can process IP addresses and approximate location derived from them, device or advertising identifiers, ad interactions and performance diagnostics for advertising, measurement and fraud prevention. Advertising services may process data outside your country. Touché does not add notification-derived targeting, search terms, app lists or Accessibility information to ad requests.

Google’s consent platform presents applicable choices before eligible ad requests. Use Ad privacy choices in Settings when available to review or change those choices; Android also provides advertising-ID controls. Sessions with no collected age or a saved 13–17 band use under-age ad settings and no personalized ads. A saved adult band follows the available privacy choices. All sessions use Google’s most restrictive G ad-content rating setting; a rating setting is not a review of every individual ad. See Google’s Privacy Policy and Google Mobile Ads data disclosures.

Your optional privacy choices

Usage analytics and crash-report sharing are separate, optional purposes. You can use Touché with both off. Open Settings → Privacy to choose each separately and select Save choices; unsaved changes do not change reporting. Advertising consent and Android notification and Accessibility permissions remain separate.

Australia and New Zealand: on a fresh installation with no earlier choices or dismissed privacy prompt, reporting can run by default after Touché displays a short notice. This applies only when the current mobile-network and SIM country both indicate the same eligible country. These checks run on your device without a location permission or a separate country lookup service; they are country hints, not proof of residence or age. The notice offers Continue, Turn off and Choose. Analytics starts after the notice is displayed and recorded; crash submission can start on a later launch. Continue closes the notice. Turn off saves refusals for both purposes. Choose or dismissing the regional notice stops the defaults until you explicitly save choices. A known under-18 band or unreadable privacy or eligibility state prevents activation.

Touché checks regional eligibility at startup, when you return to the app, when Android reports a country change and before sending an app-authored usage event. If the country signals stop agreeing on an eligible country, reporting authorized only by the regional default stops; already approved crash batches may still upload or retry. This regional policy expires at 12 May 2027, 18:30 UTC. After expiry, reporting needs a separate explicit choice. Existing choices and earlier dismissals are preserved.

Other or uncertain locations: both purposes stay off until you allow them. The privacy prompt offers Allow all, Reject all and Choose. Dismissing that prompt does not grant permission or change existing choices. We rely on your consent for this opt-in route. In the assessed Australia and New Zealand route, we use notice and an opt-out for the bounded reliability and usability purposes described below. A regional default is not recorded as your consent.

You can turn either purpose off in Privacy without losing app features. A new explicit decision records its purpose, choice, notice version, decision time and source on your device, outside Android backup. A regional activation records notice delivery and its policy version separately. These records are not analytics events or linked to your account. Updates preserve earlier explicit choices, including refusals; imported choices do not acquire an invented historical consent date. This notice does not itself authorize a new purpose.

Optional usage analytics

Usage analytics runs only when your saved choice or the regional notice route above allows it. Firebase Analytics (Google Analytics for Firebase) receives bounded feature-usage events to identify usability problems and failures in navigation, setup, search, filtering, purchases and exports. Events use fixed categories and coarse loading-time ranges. We do not send notification contents, search text, installed-app or category identifiers, rule names or conditions, exported data, account identifiers, email addresses or raw error messages as analytics parameters.

When enabled, the Analytics SDK can also process an app-instance identifier, session and app-lifecycle information, app and device information, approximate location derived from IP addresses, and automatic purchase, subscription or ad-interaction events. Touché does not set an Analytics user ID or connect analytics events to the Google account used for preference sync. Analytics sharing with Google products and services is off. Analytics advertising storage, ad-user-data use, ad personalization and advertising-ID collection are disabled. This choice is separate from advertising consent. Analytics stays disabled for installations retaining an earlier Under 13 or 13–17 choice or whose local service-eligibility state cannot be read.

Save usage analytics off in Settings → Privacy to stop new collection and reset the SDK’s local analytics data and app-instance identifier. This does not delete events already received by Google. The Touché Analytics property is configured to retain event data for 2 months and user data for 14 months, with the user-data period reset by new activity. These settings were checked on 14 October 2026; continued activity can extend retention, and these controls do not limit every standard aggregated report. Analytics information may be processed outside your country. Contact support about access or deletion requests; because we do not link Analytics to your signed-in account, we may need information sufficient to locate a relevant record. See Google Analytics retention controls, Firebase privacy and security and Google’s Privacy Policy.

Optional crash reports

Crash reports in Settings → Privacy is separate from usage analytics and advertising choices. When a saved choice or the regional notice route permits it, Touché submits saved crash reports to Firebase Crashlytics on a later app launch. Changes apply on the next app process launch. Turning the choice off prevents newly approved batches on later launches. Previously approved batches may finish uploading or retry even after the choice is turned off; they cannot be recalled.

Automatic sending remains disabled. On an eligible app launch, Touché makes one decision to send saved reports if both startup and current permission allow it, or delete pending reports if they do not. The first regional-notice launch deletes the pre-notice batch; displaying the notice does not send that batch. Similarly, a launch that begins without permission does not send its pending batch if you allow sharing later during the same launch. The SDK may record crashes locally while sharing is off, including when another Firebase feature initializes it; pending reports are deleted on the next eligible launch with sharing still off. A later permitted launch may submit retained reports. Installations with a retained Under 13 choice or an unreadable local eligibility state keep online services inactive. A retained 13–17 choice also blocks optional report submission, although eligible account features may still initialize Firebase and local crash recording.

Reports help diagnose app failures and can contain automatic crash stacks and exception messages, supported app-not-responding diagnostics, app and device information, and generated installation identifiers. Touché does not add custom logs, custom diagnostic fields, account identifiers, usage-analytics breadcrumbs or manually reported nonfatal exceptions. We keep notification content, search text and other private content out of authored diagnostic messages. However, automatic exception messages can originate in third-party code, and we cannot guarantee that every such message is redacted.

Firebase states that it retains crash traces and associated identifiers for 90 days before starting removal from live and backup systems; this does not mean every copy is erased exactly on day 90. This choice does not enable usage analytics or advertising consent. Because submission depends on permission, a later launch and successful delivery, reports do not represent every installation or a complete measure of app stability. Contact support about diagnostic-data access or deletion requests; we do not attach your signed-in account to crash reports. See Firebase Crashlytics data disclosures and Firebase privacy and security.

Reporting providers and overseas processing

Google processes reporting data under the applicable Analytics Data Processing Terms and Firebase Data Processing and Security Terms. Their safeguards address processing instructions, security, subprocessors and available rights-request tools. Touché remains responsible for its purposes, configuration and handling of privacy requests. These arrangements do not make reporting anonymous or promise that every privacy obligation has been independently certified.

Reporting data may be processed in the United States and other countries where Google or its service providers maintain facilities. There is no Australia-only or New Zealand-only storage commitment. Locations vary by service; see Google’s facility locations and Firebase’s subprocessor locations. Touché uses provider safeguards rather than asking you to waive protections for overseas processing. Contact support to raise a concern or exercise applicable access, correction or deletion rights.

This website and support

This site uses Firebase Hosting. We do not add analytics scripts, advertising, tracking cookies or external fonts to these pages. Hosting necessarily processes web requests, which can include your IP address and browser information, to deliver and protect the site.

If you email support, or contact us as a parent or guardian for a child, we receive your email address and whatever information you include and use it to respond and resolve your request. Please avoid sending private notification text, passwords or payment details. Support correspondence is retained as needed to handle the request and related follow-up; you can ask for deletion, subject to records that must be retained for legal or security reasons.

Access, correction and deletion

You, or a parent or guardian acting for a child, can contact kunal26das@gmail.com to request access, correction or deletion of the account and cloud information associated with Touché, or to raise a privacy concern. Depending on your location and the applicable law, you may also have rights to portability, object to or restrict processing, withdraw consent, or complain to a data-protection authority. To opt out of regional reporting or withdraw an explicit reporting choice, open Settings → Privacy, turn off the relevant choice and save. Withdrawal does not affect the lawfulness of processing already carried out before withdrawal; the reporting and retention limits above still apply. We may need to verify ownership before acting on a request.

The account deletion instructions explain how to request removal of the Firebase account, cloud preferences and associated RevenueCat account identifier, subject to required purchase-record retention. Local data and exported files need to be removed on your own device or document service. Account deletion and uninstalling do not cancel a Google Play subscription. Purchase, fraud-prevention or legally required records can remain with the relevant provider under its retention rules.

If you are a parent or guardian and believe a child’s information was sent to our support or cloud services, contact us so we can review the records, verify your authority where necessary, and address the request. The retained local restriction does not remove previously stored provider records.

Policy changes

We will update this page when these practices change and revise the date above. Material changes to in-app permissions or processing will also be reflected in the applicable app disclosures or choices.