Effective date: October 5, 2026
Who is responsible
This policy applies to the uRemote mobile app and this website. The controller is Grzegorz Gaworowski, using the name GGMobile (“we”, “us”). Contact commonlistapp@gmail.com for privacy questions or requests. Ordinary free or Pro use does not require a uRemote account or sign-in. Optional reviewer accounts are described below.
TV control and local information
The app uses your local network to find and control TVs you choose to pair. TV names, local IP addresses, saved devices, favourite TV apps and preferences are stored on your phone. The selected free TV, local date and remaining daily allowance are also stored on the device to apply free-plan limits. Pairing credentials are stored in the operating system’s secure storage. Commands and text you enter for the TV are sent to that TV over the local network; we do not operate a cloud TV-control or media server.
We do not send TV names, addresses, pairing codes, credentials, typed text or your TV app list in our custom Firebase events or to RevenueCat. Network permission is managed by your operating system. TV manufacturers and the apps running on your TV have their own data practices.
Media and screen access
uRemote does not select, play or send local media files on iOS or Android and does not scan your media library. The app does not capture your screen. System screen mirroring follows your phone’s operating-system controls and data practices.
Offer and purchase checks
RevenueCat checks offers, purchases and access rights. Its SDK creates a random app user identifier and contacts the service when uRemote starts and when access or offers are refreshed, even if you have not purchased and optional diagnostics are off. This is a pseudonymous identifier, not a guarantee that no personal data is processed.
RevenueCat processes that identifier, technical connection information and, where applicable, purchase receipts, product and transaction identifiers, subscription status and history. We use this for purchase verification, restored access and purchase reporting. The app does not send your name or email as RevenueCat attributes or explicitly collect advertising identifiers for RevenueCat. Apple or Google processes payment details; we do not receive your full card information. See RevenueCat’s privacy information.
Optional reviewer sign-in
The Reviewer access screen is for preconfigured app-review accounts. If you choose to sign in, your login email and password are sent over an encrypted connection to Firebase Authentication. Google processes the account identifier, authentication tokens and technical connection information, including IP addresses and app or device metadata, to verify the account, maintain the session and prevent abuse. The app checks a server-issued reviewer permission before granting access. There is no public account registration.
The app does not store your password or include it in analytics, crash reports or RevenueCat attributes. Firebase maintains the signed-in session on the device. We do not send the reviewer email or Firebase account identifier to RevenueCat or use it to link purchases. Sign out through Settings > uRemote Pro; this removes reviewer access and does not cancel or change store purchases. Authentication is needed only for this optional sign-in and operates independently of the diagnostics switch. Contact us to remove an issued reviewer account.
Optional usage analytics and crash reports
The “Help improve uRemote” setting is off by default and controls Google Analytics for Firebase and Firebase Crashlytics together. In Polish it is labelled “Pomóż ulepszać uRemote”. If you enable it, analytics records predefined usage categories, such as screens opened, connection outcomes, control modes, command categories, durations and counts. The SDK also uses app-instance identifiers and general app, device and interaction information. Google Analytics may derive approximate location from a connection’s IP address. We do not request precise GPS location or use analytics for targeted advertising.
Crash reporting helps diagnose failures using installation identifiers, app and OS versions, device characteristics, error types and stack traces. Our custom error reports omit exception-message text and use predefined context labels. Native SDK reports may contain additional technical diagnostic details. We do not attach pairing information or typed TV text to reports.
Firebase SDKs may make technical requests for installation identifiers and service configuration even when optional reporting is off. These requests can process IP addresses and app or device metadata needed to operate the SDK. The optional switch does not disable every SDK connection.
Vizio application catalog
When you open the application library for a connected Vizio SmartCast TV, the app may request a public catalog from scfs.vizio.com over HTTPS. The provider receives normal connection information such as your IP address. Catalog matching to TV chipset and firmware happens on the phone. The request does not send the TV’s identity, pairing token or your keyboard text.
Your controls
- You can use the remote without enabling optional analytics and crash reports. Turn the switch on or off in Settings.
- Disabling the switch stops our optional reporting, resets locally held Analytics data and requests deletion of unsent crash reports. Restart the app after disabling it so the native crash-reporting setting fully takes effect. It does not automatically delete data a provider already received.
- Use the saved TV’s menu to forget one television, or remove saved connections in Settings to clear pairings. Operating-system secure storage and backups may persist separately from an app uninstall; use the explicit removal controls for saved pairings.
- You can revoke local-network access in your device settings. TV control needs network access to your TV. Purchase checks still need internet access and operate separately from diagnostics consent.
This website and support
This website uses Firebase Hosting. Google processes connection information, including IP addresses, to serve pages and protect hosting from abuse. We do not add website analytics, advertising trackers, tracking cookies, account registration or a contact form. The pictured remote is a labelled demo screenshot and does not connect to a TV. Email links open your email app.
If you contact us, we receive your email address and the information you choose to send. We use it to answer and investigate your request. Avoid sending passwords, pairing credentials, private screen content or full payment details.
Purposes and legal bases
- Consent: optional usage analytics and crash reporting. You may withdraw it without affecting earlier lawful processing.
- Providing a requested service: local remote-control functions, offer and purchase checks, restoring purchased access, authenticating an optional reviewer account and related support.
- Legitimate interests: securely delivering this website and technical services, preventing abuse, understanding purchase activity and answering general enquiries, subject to your rights.
- Legal obligations: records or disclosures required by applicable law.
Providing optional diagnostic data is voluntary. We need sufficient information to handle a support request and store purchase information to verify purchased access. We do not make automated decisions about you that have legal or similarly significant effects.
Providers and international processing
Google provides Firebase Authentication, Firebase Hosting, Firebase Crashlytics and Google Analytics. Vizio serves its public application catalog. RevenueCat provides purchase infrastructure. Apple and Google operate their respective stores and payment services. Email providers handle support correspondence. Providers may process service information under their own terms. Relevant information may also be disclosed where legally required.
These providers operate internationally, including in the United States. Firebase Authentication processes account data in the United States. Their applicable data-processing terms describe safeguards for international transfers, including standard contractual clauses where relevant. Review Firebase’s data-processing terms, Google Analytics data-processing terms and RevenueCat’s data-processing addendum. You may contact us for information about the safeguards relevant to your data. We do not sell your personal information.
How long information is kept
- Local TV details and preferences remain until you remove or reset them; system backup and secure-storage behaviour depends on the device.
- Optional usage information is kept for the period needed to examine app reliability and usage trends, subject to Google Analytics retention controls. Withdrawal stops new collection; existing aggregate reports and provider deletion schedules may differ. Contact us about deletion of data that can be linked to you.
- Firebase states that Crashlytics retains crash traces and associated identifiers for 90 days before starting removal from live and backup systems, and that Hosting keeps IP addresses for a few months.
- Firebase Authentication keeps logged IP addresses for a few weeks. It retains other authentication information until we request deletion of the account; removal from live and backup systems can then take up to 180 days. Signing out or uninstalling does not delete the account.
- Purchase records are kept as needed to provide and restore the purchased entitlement, resolve purchase disputes, prevent abuse and meet applicable legal recordkeeping duties. The needed period depends on the entitlement and applicable law.
- Support messages are kept to resolve the request and relevant follow-up, or longer when needed for a legal obligation or dispute. We review continuing need rather than keeping every enquiry indefinitely.
The Firebase privacy and retention information explains provider-specific practices. Deleting the app does not cancel a subscription or automatically delete store records.
Privacy requests and your rights
Depending on applicable law, you may request access, correction, deletion, restriction, portability or object to processing based on legitimate interests. You may withdraw optional reporting consent in the app. Contact commonlistapp@gmail.com to exercise your rights. We may ask for limited information necessary to verify and locate the relevant records; a random installation or purchase identifier may be needed because ordinary store purchases do not use an app sign-in account. For an issued reviewer account, provide its login identifier; never send its password.
You can complain to a competent data-protection authority, including the Polish supervisory authority (UODO). Some records must be retained to comply with law or address claims. We will explain any applicable limitation.
Security, children and changes
We minimise information sent by the app and use device and provider security features. No system is completely secure; protect your phone, network and pairing credentials. uRemote is a general-purpose utility and is not specifically directed to children. Contact us if a child has provided personal information inappropriately so we can address it.
We may update this policy as the app or its services change. The effective date identifies this version. We will give additional notice or obtain a new choice where required before materially changing consent-based processing.