TV Remote Universal Privacy Policy
Effective 22 October 2026
PUBLISHER DETAILS REQUIRED BEFORE PLAY PUBLICATION
Legal publisher name: Fisstzapp
Privacy contact email:zeesigntech017@gmail.com
This policy explains what TV Remote Universal stores on your phone, how it communicates with a device you choose, and how advertising services may process information when enabled. Review the publisher fields above and ensure this text matches the release build and Play Console disclosures before publishing.
TV Remote Universal is an Android application published. This policy describes the app's current data practices and its Google advertising components. For privacy questions, contact [monitored privacy email]. Replace the publisher name and email before publication and use the final public policy URL in Google Play and the app.
Information stored on your device
The app stores saved remote names, selected control profiles, device addresses needed for a saved network connection, and app preferences, including the selected app language, in private app storage. Android TV pairing identity material is held by Android Keystore. These data are used to restore your remotes and establish connections you request. They are not uploaded to a TV Remote Universal server. They remain until you remove the relevant remote or clear app data; uninstalling removes app-private data, subject to Android's backup/device behavior.
When you enter text and explicitly send it, the app transmits it to the focused TV input over the selected control connection. The app does not intentionally save the text. Do not send sensitive information to a shared TV.
Device permissions and control traffic
Depending on the feature you use, Android permissions and system APIs may provide internet/local-network communication, Bluetooth discovery or connection, and infrared transmission. The app uses them to discover, pair with, or send commands to a device you select. Network addresses and protocol traffic are exchanged directly between your phone and the selected device for local control. The app does not use location, contacts, camera, or microphone data in its current feature set. Availability and Android permission behavior vary by OS version.
Firebase Remote Config
When the publisher connects a Firebase project, the app fetches Remote Config values that control ad placement switches, sizes, and frequency policy. Ad unit IDs are compiled into the selected debug or release build and are not fetched from Firebase. Firebase Remote Config uses a Firebase Installation ID (FID) to select and return configuration values; Firebase may also process service request information such as IP address under its service terms. The app does not put TV names, saved remote records, commands, or other remote-control content into Remote Config requests. The FID is an installation identifier, not a TV Remote Universal account. The project-specific Firebase configuration is not included in this checkout, so Firebase Remote Config is not active in the current unconfigured build. If enabled for release, users can clear app data or uninstall the app; Firebase provides installation-ID deletion mechanisms, but this app currently has no in-app Firebase ID deletion control. See Firebase privacy and security (https://firebase.google.com/support/privacy/) and Firebase Android Data disclosure (https://firebase.google.com/docs/android/play-data-disclosure).
Advertising and consent
The project includes Google Mobile Ads and Google's User Messaging Platform (UMP). Production AdMob IDs have not yet been supplied, and the importable Remote Config template keeps the master and placement switches off, so the current release configuration is intentionally not buildable for production and makes no production ad requests. Ad unit IDs are compiled into the selected build type and are not fetched from Firebase. When configured and enabled, Google Mobile Ads may collect or receive information such as IP address, device identifiers (including advertising identifiers where available and permitted), ad interactions, diagnostics, and privacy-preserving ad attribution/topic signals to provide, measure, and protect advertising. Google and its service providers process such information under their own terms and privacy disclosures. An ad request is made only after UMP reports that ads may be requested. The app supports a labeled adaptive banner and at most one general native ad (bottom takes precedence over middle) on eligible Home, Remotes, Add, and Settings screens. Pairing/setup and active remote-control screens are excluded. Native ad space is reserved with a loading shimmer only while an enabled, consented online request is pending; failed/offline requests leave no ad slot. Separate language and onboarding native placements use their own compiled ad unit IDs and Remote Config flags. When enabled, the language placement may load during the first-run startup screen, with a maximum four-second wait before the language chooser; the onboarding placement is preloaded while the language chooser is visible and can appear in the onboarding flow. Both require UMP permission and validated internet, and a failed or unavailable request leaves no ad slot. A Remote Config gated App Open ad may appear on eligible warm returns to Home, never first/cold launch or during setup, pairing, or active remote control, and is rate-limited. Transition interstitials can be enabled only for configured workflow breaks; when enabled, consented, and online, a bounded transition state may appear while loading and navigation continues after dismissal or a four-second timeout. All placements are off by default.
UMP may store consent and privacy choices on the device and display consent or privacy-option forms. Where UMP requires a privacy-options entry point, it is available at Settings > Privacy choices. You can also manage advertising settings in Android settings. See Google's advertising technologies at https://policies.google.com/technologies/ads and Google's privacy policy at https://policies.google.com/privacy.
Sharing, analytics, and retention
The app has no TV Remote Universal account, operator backend, or TV data synchronization. We do not receive saved remotes or commands. The current source does not include Firebase Analytics or a crash-reporting SDK. If Firebase Remote Config is activated, Firebase receives installation/configuration requests as described above. Google Mobile Ads and UMP can communicate with Google when ad configuration is enabled and the relevant feature is used; those services' processing is governed by Google's policies. Device-local data is retained until you delete it as described above. Network TV connection records should be removed from the app before disposing of a device.
After three successfully dispatched button taps or a successful TV connection, the app may request Google's Play In-App Review flow at a safe point after leaving active control or setup. Play decides whether to display its native review card and handles any rating or review text submitted there. TV Remote Universal does not read or store the rating or review text. The app stores only local usage milestone counters and a review-request timestamp to avoid repeated prompts. Google Play documents review submission data and its handling in its in-app review data safety notes (https://developer.android.com/guide/playcore/in-app-review).
Children's privacy
TV Remote Universal is a general-purpose utility and is not designed specifically for children. The publisher must complete the Play Console target-audience and Families declarations accurately before publication. Do not enable child-directed or personalized advertising without completing the applicable legal, SDK, and Play policy review.
Your choices and questions
You can remove saved remotes in the app, clear the app's data through Android Settings, uninstall the app, and change privacy choices where UMP presents that option. For privacy questions or requests, contact the publisher at [monitored privacy email]. The publisher must use the same monitored contact in this policy and the Play listing.