USB Camera Privacy Policy
Effective date: On the public release of version 1.0.0
Last updated: October 13, 2026
This Privacy Policy explains how USB Camera handles information when you use the App.
1. In short
The App has no account system and integrates Firebase Analytics and Firebase Crashlytics. Starting with 1.1.0, ad-enabled builds show an AdMob banner at the bottom of Settings and the gallery list. Builds with Firebase configured send app usage events, version and device technical information, and diagnostics for crashes, ANRs, and non-fatal exceptions explicitly recorded by the App to Google/Firebase for analytics and stability work. Previewing, capturing, recording, and gallery management happen on your Android device. The App does not use these events to upload photos, videos, microphone audio, full RTSP/RTMP URLs, or streaming keys.
2. Information the App handles
| Information | Why it is used | Storage and retention | Sent to us? |
|---|---|---|---|
| USB UVC camera frames | Preview, photo capture, recording, and streaming initiated by you | Processed in device memory while previewing; captures are local files until you delete them or Android clears app data | No |
| RTSP camera frames and source audio | Preview; relay to RTMP/RTMPS when you start streaming (no RTSP photo or video capture) | Processed in memory, not saved to the in-app gallery | No; sent to your selected server when streaming |
| RTMP/RTMPS URL and streaming key | Send USB or RTSP video to your selected destination | Encrypted on-device with Android Keystore and AES-GCM until you remove it or clear app data | No; sent to the destination service when streaming |
| Network information for update checks | Retrieve the latest and minimum supported versions when a remote update URL is enabled | The configuration host may log IP address, request time, and necessary HTTP information under its hosting practices | Sent to the update configuration host when enabled |
| Microphone audio in recordings and USB streaming | Written into a local video or sent to your selected server only when you enable audio and start recording or USB streaming | Recordings are local files until deletion or app-data clearing; streaming audio is processed during the session | No; sent to your selected server during USB streaming |
| Photos and videos captured by you | View, delete, and share from the in-app gallery | App-specific storage until deletion, uninstall, or app-data clearing | No; a user-selected app receives a file when you explicitly share it |
| RTSP URL entered by you, which may contain a username and password | Connect to a network camera and remember a saved endpoint | Encrypted on-device with Android Keystore and AES-GCM until you remove it or clear app data | No; it is sent to the RTSP device/server you choose when you connect |
| Basic USB information (product/manufacturer names, vendor/product IDs, video-class flag) and preview diagnostics (random per-connection ID, elapsed time, frame counts, dimensions/format, and failure reason) | Enumerate and open authorized devices and diagnose connection or missing-preview problems | Device access happens during the session; releases with the new diagnostics send analytics to Firebase/Google under the project and Google retention rules | Yes, to Firebase/Google when the new diagnostics are enabled; excludes device serial numbers and local USB paths |
| App usage events, app version, and device technical information | Measure use of app opening, connection, preview, photo, and video features | Sent to Firebase/Google and handled under the Firebase project and Google retention rules | Yes, to Firebase/Google |
| Crash, ANR, and explicitly recorded non-fatal exception diagnostics | Diagnose crashes and stability issues | Sent to Firebase Crashlytics and handled under the Firebase project and Google retention rules | Yes, to Firebase/Google |
The App does not read existing photos or videos from the system gallery and does not request contacts, location, phone, or SMS permissions.
External RTSP endpoints
You enter RTSP addresses yourself. When you connect, the address, authentication information in it, and playback requests are sent to the camera or streaming server selected by you. Those systems are not operated by us and have their own privacy and security practices. RTSP transport security depends on your device, network, and the endpoint’s supported protocol. Do not use sensitive credentials on an untrusted network.
Streaming, update checks, and Firebase
- Starting a stream sends USB video and enabled phone-microphone audio, or video and available audio from your RTSP source to your selected RTMP/RTMPS platform. Its visibility, retention, and deletion depend on that platform and your settings. Stopping transmission does not delete content already retained by the platform. This version supports both USB and RTSP streaming input.
- RTMP does not encrypt the connection; RTMPS uses TLS to protect transmission to the destination. Use only destinations you trust and are authorized to use.
- The remote update URL is empty by default, so no update request is made. When enabled, startup and manual checks read version JSON without attaching camera URLs, photos, videos, or streaming keys. Choosing Update opens the store; the App does not download or install APKs itself.
- Firebase uses app-instance/installation identifiers and device, system, and event information. Advertising-ID collection and ad-personalization signals remain disabled for Firebase. AdMob processing is described below.
- Firebase/Google may process data outside your country or region. See Firebase Privacy and Security and the Google Privacy Policy. Uninstalling does not automatically delete diagnostics or analytics already received by the service; contact the privacy email below for related requests.
Firebase Analytics may derive coarse regional statistics from IP addresses; the App does not request precise GPS-location permission. Disabling advertising-ID collection does not disable app-instance identifiers or usage events.
3. Permissions
- Camera (
CAMERA): Used for Android video-capture permission checks needed to support USB camera preview. The current version primarily displays video from a USB UVC camera that you authorize. - USB device access: Android shows a system permission prompt when a USB device is connected. The App accesses only devices you explicitly authorize.
- Microphone (
RECORD_AUDIO): Requested only when you choose to record or stream USB video with sound. You can still record without sound when supported if you deny it. - Network (
INTERNET): Used for the RTSP connection and RTMP/RTMPS streaming you initiate, enabled update checks, and, when enabled in the build, for sending analytics and diagnostics to Firebase Analytics and Crashlytics. Custom analytics and remote update checks depend on build configuration; this policy will be updated before enabling those services. There is no account service or media cloud sync.
Camera, USB, and microphone access is used only for camera features you initiate and is not provided to advertising services. Ad-enabled builds declare AD_ID permission and use the network to load ads and manage privacy choices.
Ads and privacy choices from 1.1.0
Ad-enabled builds show a Google AdMob banner at the bottom of the main Settings page and gallery list, outside image details, video playback, preview, photo, recording, and streaming screens. Ads load while either page is visible and the app is foregrounded, including while a camera is connected, recording, or streaming. Unavailable ads do not block camera features.
Google Mobile Ads SDK may send Google and its advertising partners IP addresses (which may infer approximate location), advertising or other device/installation identifiers, device and app information, ad impressions, clicks and other interactions, and diagnostics. These are used for advertising, measurement, analytics, fraud prevention, and security. We do not supply photos, video, microphone audio, USB device information, camera URLs, or streaming keys to ad requests, or request precise-location permission for ads. Processing may occur outside your country. Retention and deletion follow the Google Privacy Policy; see How Google uses partner data.
Google User Messaging Platform updates privacy status and, where applicable, presents required privacy choices while Settings or the gallery list is visible and media work is idle. Ads load only when UMP permits requests. When required, reopen choices using Ad privacy choices in Settings. Ad personalization depends on your choices and applicable requirements. Settings and the gallery list may show ads during the free Pro period; ad removal is a future subscription benefit that is not yet available.
4. Sharing and third-party services
When you tap Share in the gallery and choose a destination, the App uses Android’s system sharing mechanism to grant that app access to the selected photo or video. The receiving app’s own privacy policy governs what it does with the file.
The current version uses Android/AndroidX, Jetpack Compose, Media3 ExoPlayer, libusb, libuvc, FFmpeg, and mbedTLS for the system UI, RTSP playback, and USB video functionality, and uses Firebase Analytics and Firebase Crashlytics for analytics and crash diagnostics. Firebase/Google may process app instance identifiers, app version, device technical information, usage events, and crash diagnostics. App events are not intentionally populated with photos, videos, audio, full RTSP/RTMP URLs, usernames, passwords, or streaming keys. Google Play, Android, and an RTSP endpoint you choose may also process necessary technical information under their own policies.
5. Retention, deletion, and uninstall
- You can delete photos and videos in the in-app gallery.
- You can remove saved RTSP or RTMP addresses from their lists.
- We keep no remote copy of app-local media or settings.
- Firebase Analytics and Crashlytics data is handled under the Firebase project configuration and Google retention/deletion mechanisms; it is not stored on a media server operated by us.
- Uninstalling the App or clearing its data in Android settings normally removes app-specific data; actual behavior may vary by Android version or device manufacturer.
- In version 1.0.3 with the new protections, backup rules exclude saved RTSP/RTMP endpoint settings and captures in both internal and app-specific external storage from system cloud backup and device migration. Earlier versions may still back up this data under Android/Google settings; the new rules do not remove existing backups or copies you actively share. System backup of other non-sensitive settings follows Android and your account settings, not a server operated by us.
- If you have already shared a file with another app, we cannot delete that app’s copy for you.
The current version has no remote account and therefore no server-side account-deletion process. If we add accounts, cloud sync, streaming services hosted by us, or payments, we will update this policy and the Google Play Data safety declaration before those features launch.
6. Security
We use measures appropriate to the current features, including:
- encrypting saved RTSP and RTMP/RTMPS URLs on the device with an Android Keystore key and AES-GCM;
- writing photos and videos to app-specific storage and granting another app a file URI only after you explicitly share it;
- in version 1.0.3 with the new protections, hiding RTSP paths and raw playback exceptions in app logs, suppressing raw FFmpeg diagnostics, and filtering URLs, credentials, and free-text failure details before analytics; Media3 RTSP debug logging is enabled only in debug builds. Crashlytics may collect exception types, stack traces, and device environment information needed to diagnose a crash.
No local storage, operating system, network, or external device can be guaranteed completely secure. Protect your device credentials and use suitable accounts and network security for RTSP devices.
7. Children’s privacy
The App is a general-purpose tool for people using external cameras and is not primarily designed for children under 13. We do not knowingly collect children’s personal information. When recording people, children, or audio, you are responsible for obtaining any required consent and complying with applicable law.
8. Your responsibility and external content
The App can display a camera feed selected by you and save content you intentionally capture. You are responsible for having the right to access the device and RTSP address, and for the content you record, save, share, or distribute. The App does not moderate, host, or provide your captures to other users.
9. Changes
If the App’s permissions, data flows, or features materially change, we will update the “Last updated” date and, where appropriate, notify users through the App or its store listing. Changes take effect when posted.
10. Contact
For questions, requests, or complaints about this policy, contact:
- Contact email: camnow.team@gmail.com