Privacy Policy
Last updated: July 31, 2026
P2P HomeCam is designed to turn a spare phone or tablet into a home camera. The app attempts a direct peer-to-peer connection first. If a direct connection is unavailable, an encrypted TURN relay is used only after the viewer approves it.
1. What the app does
The app has two roles: a Camera phone that captures video and audio, and a Viewer phone that watches the registered camera. A lightweight signaling server helps the two devices exchange connection information such as Room ID, offers, answers, and ICE candidates.
2. Information we process
- Camera and microphone streams on the Camera phone.
- Room ID, temporary socket IDs, role information, room authentication hash, and WebRTC signaling messages.
- Saved camera names, PIN-protected pairing data, viewer preferences, quality settings, audio sensitivity, camera direction, and motion recording settings stored on your device.
- Motion recording files stored on the Camera phone when motion recording is enabled.
3. Live video and audio
Live video and audio are sent through WebRTC. The app attempts a direct connection first. If that attempt fails, the viewer is asked whether to use the TURN relay. Only after approval, encrypted WebRTC packets temporarily pass through the relay server. The relay server does not decrypt, record, or store live video or audio. Short-lived TURN credentials and connection metadata such as public IP address, connection time, and network error information may be processed temporarily to establish the connection, protect the service, and prevent abuse. Motion recordings remain on the camera phone and are not stored by the signaling or TURN server.
The app may contact public STUN services, such as stun:stun.l.google.com:19302, to discover network paths. STUN is used for connectivity and does not receive your video or audio stream.
4. Motion recordings
Motion recording files are saved on the Camera phone, not on the Viewer phone by default. If you open a recording from a Viewer phone, the selected file is sent directly between the two devices through an encrypted WebRTC DataChannel. The signaling server does not receive or store the recording file.
5. Permissions
The app asks for camera, microphone, internet, network state, notification, foreground service, and wake lock permissions so it can provide camera monitoring, talkback audio, motion recording, and long-running camera mode.
6. Advertising and Google Mobile Ads
The app uses the Google Mobile Ads SDK to display banner and interstitial ads. Where required, the app asks for advertising consent before requesting ads and serves personalized, non-personalized, or limited ads according to the user's choices and applicable law. The SDK may automatically collect and share IP addresses (which may indicate general location), app interactions, diagnostic information, and device or account identifiers such as the advertising ID and app set ID for advertising, measurement, and fraud prevention. Google states that this data is encrypted in transit using TLS. Google processes this data under its own privacy policy. Required users can reopen Ad Privacy Choices in the app. P2P HomeCam does not use Firebase or a separate analytics SDK.
7. What we do not do
- We do not require account registration.
- We do not sell personal data.
- We do not use Firebase or a separate analytics SDK.
- We do not store live video or live audio on the signaling server.
8. Retention and deletion
Pairing data and settings remain on your device until you reset registration, delete a saved camera, clear app data, or uninstall the app. Motion recordings remain on the Camera phone until you delete them or the app removes older recordings according to the retention setting.
9. Security
Pairing uses a PIN-protected secret and the signaling server stores room authentication as a hash in memory. You should only register cameras you own or are authorized to use. Keep your devices updated and protect your home Wi-Fi router.
10. Children
The app is not directed to children. Do not use it to record or monitor anyone where doing so would violate law, consent requirements, or personal privacy.
11. Contact
For privacy questions, contact the developer through the app store listing or the official support contact published with the app.