Summary
SmartUs uses Google AdMob, Google User Messaging Platform, and Google Analytics for Firebase. These SDKs may transmit data off the device. SmartUs does not require a user account and does not operate a server that receives saved TV connection records.
The table below summarizes the data types disclosed for the current Android release of SmartUs by Falido.
Collected and shared data
| Google Play category | Collected | Shared | Primary purposes |
|---|---|---|---|
| Approximate location Estimated from IP address |
Yes | Yes | Advertising or marketing; analytics; fraud prevention, security, and compliance |
| App interactions SDK-reported app launches, sessions, screen or product interactions, and ad interactions |
Yes | Yes | Advertising or marketing; analytics; fraud prevention, security, and compliance |
| Diagnostics App and advertising SDK performance information |
Yes | Yes | Advertising or marketing; analytics; fraud prevention, security, and compliance |
| Device or other IDs App-instance ID, Advertising ID, app set ID, and other Google SDK identifiers where available |
Yes | Yes | Advertising or marketing; analytics; fraud prevention, security, and compliance |
These data types are treated as required rather than optional for the global Google Play disclosure because some automatic SDK collection can occur without an app-wide opt-out available to every user. Advertising consent choices may still vary by region.
Data not collected by SmartUs
SmartUs does not request or intentionally collect names, email addresses, phone numbers, precise location, contacts, messages, photos, videos, audio, files, financial information, health information, calendar information, browsing history, or installed-app lists.
Local TV connection data
TV display name, connection type, local IP address or host, pairing token or key, random local record and app-to-TV connection identifiers, network device identifier, Wi-Fi MAC address, and protected secure-pairing credentials may be stored in private app or operating-system-protected storage. SmartUs does not upload these records to a Falido-operated server or pass them as event parameters to Google AdMob or Firebase Analytics.
Relevant connection data, pairing material, wake packets, and commands are sent directly to the user's selected TV or local network only as needed for discovery, pairing, reconnection, wake, and control. The Android app does not log custom TV identifiers or remote-control command values to Firebase Analytics.
Security
Google states that data transmitted by the Google Mobile Ads SDK and Firebase Analytics is encrypted in transit using TLS. Local TV traffic depends on the protocol offered by the TV and may use either encrypted or unencrypted WebSocket communication on the user's local network.
SmartUs does not display Google-served banner ads on the active remote-control screen. A banner may appear on the setup and discovery screen and is separated from interactive app controls.
Retention and deletion
Saved TV records remain until the user deletes a TV, resets pairing, clears app storage, or uninstalls SmartUs, subject to operating-system handling of protected key material. Data processed by Google services is retained under the applicable Google settings and policies.
See Data Deletion for instructions and the request channel.
Contact
Questions about this summary can be sent to furkanalidonmezz@gmail.com.