Privacy Policy
Last updated: June 17, 2026. This policy describes our practices regarding information collection, usage, and permissions.
Summary for Play Store Approval
Mobile Caster is a local-first application designed for screen and camera mirroring. All media streams are transmitted directly over WebRTC peer-to-peer connections inside your local network. No video or audio feeds are stored, inspected, or processed by any remote servers.
1. Information Collection and Use
Mobile Caster does not collect, harvest, or transmit any personally identifiable information (PII) or sensitive user data. All streaming media traffic (screen capture, camera images, and microphone audio) is handled locally.
2. Permissions Requested and Rationale
To operate correctly, the Mobile Caster Android app requires access to several native permissions. Here is a clear description of why they are requested and how they are used:
- Camera Permission: Used solely to capture your phone’s camera feed when you select the camera stream option. This feed is streamed in real-time to your desktop receiver.
- Microphone Permission: Used to capture device audio or ambient sound to include with your stream when audio casting is active.
- Screen Capture (MediaProjection API): Required to capture your phone's screen layout so it can be casted to the receiver. A persistent notification and confirmation prompt are displayed to the user before screen sharing begins.
- Local Network / Wi-Fi Access: Needed to establish P2P WebRTC data channels between your mobile phone and your computer (using direct USB routing, Wi-Fi router IP routing, or hotspot point-to-point connections).
3. Third-Party Services
We leverage trusted industry-standard SDKs to provide advertisements and basic crash reporting. These services may collect information as detailed below:
Google AdMob
Used for delivering interstitial, app-open, and banner ads inside the mobile application. AdMob may collect device advertising IDs (e.g., GAID) to serve personalized or non-personalized advertisements.
Firebase Analytics & Crashlytics
Used to monitor app health, performance metrics, and track user actions anonymously. This helps us locate and fix app crashes and optimize the user interface. No video/audio feeds are processed by Firebase.
4. Data Retention and Security
Since all media content is transmitted directly from device-to-device via WebRTC and is never uploaded to external servers, we hold no media data. Signaling tokens used to coordinate peer-to-peer negotiation are ephemeral and disposed of immediately once the connection is established.
5. Contact Us
If you have any questions or feedback regarding this Privacy Policy or security practices, please contact us at:
contact@devsol.in