Privacy policy
How Private Video Recorder handles recordings, permissions and advertising data.
Developer: Web Bharat Media
Package: com.privatevideo.recorder
Effective date: 15 October 2026
Contact: contact@webbharat.com
1. Camera, microphone and recording status
Camera access is used for recordings you explicitly start. Microphone access is optional and used when you enable audio. Notifications provide recording status and a Stop action. Android privacy indicators remain visible. The app does not start recording from device boot or incoming messages.
2. Video storage, sharing and deletion
Recordings and recording preferences are stored on your device. We do not operate a cloud-upload service for your videos and do not intentionally send saved videos or camera frames to advertising services. Sharing and exporting send a selected file to a destination you choose; that destination has its own data practices.
You can delete recordings in the app gallery. Uninstalling removes app-private recordings and settings. Export files you want to keep before uninstalling. We do not maintain a developer server copy of your recordings.
3. Optional gallery authentication
Gallery locking uses Android biometric or device-credential authentication. The app does not receive your fingerprint or phone password. This is a gallery access control, not additional video-file encryption.
4. Advertising and third-party services
The app uses Google AdMob and Google's User Messaging Platform (UMP). The app may show a full-screen App Open advertisement on its startup loading screen and a banner in Settings. Ads are not shown during an active recording session. The startup ad is skipped if it is not ready in time, and does not appear over the recording controls. The app does not require a licence key or payment to select the 120-minute duration option.
According to Google's SDK disclosure, Google Mobile Ads may collect and share:
- IP address, which can be used to estimate general location;
- Device and account identifiers, such as Android advertising ID and app set ID, depending on device availability and settings;
- App/product and advertisement interactions;
- Diagnostics, including performance, crashes, hangs and energy-use information.
Google uses this information for advertising, analytics/measurement and fraud prevention. Its SDK data is encrypted in transit using TLS. Processing varies with device settings, region, consent and ad configuration. No separate Firebase Analytics SDK is included in this app.
Read Google's Privacy Policy, Google advertising information and Google Mobile Ads data disclosures.
5. Your advertising privacy choices
The app requests current consent information and presents Google's consent form where required before requesting ads. Where applicable, Settings shows an Ad privacy choices entry point so you can review or change choices. You can also use your Android advertising-ID settings to reset or delete that identifier. Ads not loading, consent/network errors or no-fill do not disable recording or reduce the available duration range.
6. Retention, support and privacy requests
You control the retention of local video files by deleting or exporting them. Google's retention and account/privacy controls apply to data received by Google; we cannot directly delete records maintained by Google.
If you email us for support, we receive the message and information you choose to include. Please do not send private recordings unless necessary and you have permission. We use support information to respond to the request and keep it only for as long as needed to resolve the issue or meet applicable obligations. Email contact@webbharat.com to request deletion of information you sent us. The app itself does not require an account.
7. Children and responsible use
The app is a general recording utility, not a service designed specifically for children. Record only where you have the required permission. If you believe a child has sent personal information to us, contact us so we can review and address it.
8. Updates to this policy
We may update this policy when app features, SDKs or data practices change. The effective date above identifies the current policy. Material changes will be reflected in the app or this page as appropriate.