Privacy Policy
This app is a DVR monitoring app for a DVR system you configure and are authorized to use.
Data We Store
- DVR alias, host, HTTP/ISAPI port, RTSP port, and username that you enter manually.
- DVR password that you enter manually. The mobile app stores it in platform secure storage.
- Your local app preferences such as Wi-Fi-first low-data behavior and theme mode.
- Your ad and local usage metrics preferences if you turn them on.
- Camera display names that you save in the app.
- Diagnostics logs that help troubleshoot connection issues.
- Remote log upload endpoint and token if you configure log upload. The token is stored in platform secure storage.
Data We Do Not Intentionally Collect
- We do not intentionally send usage metrics to Google Analytics or another cloud analytics service in the current build.
- We only show ads in support areas, not on the live camera screen.
- We do not intentionally upload passwords.
- We do not intentionally share your DVR credentials or camera feeds with third parties.
Local Storage
Saved settings and logs stay on the device unless you manually export or upload them. The mobile DVR password and remote log upload token are stored separately in platform secure storage.
Data Retention and Deletion
Local settings, camera names, preferences, and diagnostics logs remain on the device until you clear them in the app, delete the app, or clear the app's data in system settings. Remote log upload only happens when you configure an HTTPS endpoint and manually send logs. For any uploaded logs, use the support channel that received the logs to request deletion.
Remote Log Upload
If you choose to upload logs, the app sends only the diagnostic log entries to the HTTPS endpoint you specify.
Ads and Consent
When a build has production AdMob IDs, it can show a support banner outside the live monitoring surfaces. The app requests updated consent information on launch and presents a consent message where required before requesting an ad. A privacy-options control is shown when the consent platform requires it. The support-banner switch hides the banner; it does not by itself disable the Google Mobile Ads SDK or withdraw consent.
For an ad-enabled build, the Google Mobile Ads SDK may collect and share the device IP address (which can indicate approximate location), app interactions, diagnostics, and device identifiers including the Android advertising ID and app set ID. Google uses these for advertising, analytics, and fraud prevention, and says its SDK transmits them using TLS. The app does not intentionally include DVR passwords or camera video in ad requests. See Google's Mobile Ads data disclosure and Google's privacy policy.
A build without production AdMob IDs does not initialize Mobile Ads or request ads. It also omits the advertising identifier and AdServices permissions from the Android manifest.
Usage Metrics
When usage metrics are enabled, the app stores lightweight local event labels to help with future product analytics wiring. These are not shared unless you explicitly enable a future upload path.
Privacy Contact
For privacy questions or deletion requests, email info@findtw.com. You can also read the support page.