LocalCam Mirror — Privacy Policy

Effective date: October 1, 2026
Applies to: LocalCam Mirror for Android
Contact: aimotioncoach@gmail.com

What LocalCam Mirror does

LocalCam Mirror lets two phones connect directly to each other over local Wi-Fi or Bluetooth to mirror a camera feed, capture photos, send remote commands, and record video. Mirroring, photo capture, motion detection, and recording work entirely between your two phones over a direct local connection. No internet connection is used for any of this, and no servers are involved.

Data we collect

We do not collect, store, receive, or share your personal data, usage data, analytics, or diagnostics. Nothing is transmitted to us at all — the only transmissions the app makes are the ones you switch on, to destinations you own. We operate no servers and we have no account system. Nothing about you or your device is ever sent to us.

One optional exception, which you turn on yourself: Telegram alert forwarding. It is off by default. If you enable it, motion alert photos are sent from your phone directly to your own Telegram bot and your own Telegram channel — never to us. See "Telegram alert forwarding" below.

Subscriptions (Motion Detection Pro)

LocalCam Mirror offers an optional auto-renewing subscription, Motion Detection Pro, which unlocks the app's motion-detection features (person/vehicle/animal alerts, automatic recording, and the activity timeline). The subscription is sold and processed entirely through Google Play's billing system. Only the phone used as the camera needs a subscription.

Payment is charged to your Google account. All payment and financial information is handled directly by Google — this app does not collect, receive, or store your payment details, card information, or purchase history on any server. We operate no backend; your subscription status is stored only locally on your device and is verified through Google Play.

Subscriptions renew automatically at the end of each billing period unless canceled at least 24 hours before the period ends. If you started a free trial, it converts to a paid subscription automatically when the trial ends unless canceled beforehand. You can view, manage, or cancel your subscription at any time in Google Play (Menu > Subscriptions), or at https://play.google.com/store/account/subscriptions. Prices are shown in the app before purchase, may vary by country, and are subject to applicable taxes.

For details on how Google processes payment data, see the Google Play Terms of Service and the Google Privacy Policy.

Data that stays on your device

The app creates photos when you use Photo mode and video recordings when you choose to record. Captured photos are saved locally to the camera phone's gallery under Pictures/LocalCamMirror. During a connected session, a captured photo is also sent directly to the controller phone and saved there under Pictures/LocalCamMirror/Received. Video recordings are stored locally under Movies/LocalCamMirror. These files are fully under your control, and you can delete them at any time using your phone's gallery or file manager.

Settings you configure in the app (preview quality, audio preference, and photo settings) are stored locally in your device's app storage and are deleted when you uninstall the app.

How data moves between phones

When two phones are connected, the following is sent directly between them over Nearby Connections:

• Live camera preview frames
• Remote control commands (including preview, recording, camera, and photo controls)
• Captured photo files when you use Photo mode
• Recorded video files (optional, only when the save-to-gallery toggle is on)
• Session heartbeat signals

All traffic between devices is encrypted in transit using TLS, which is provided automatically by Google's Nearby Connections SDK. No data passes through any server or third-party service. No data leaves the local network.

Background operation

When you start a session as the camera host and accept a connection from the controller device, LocalCam Mirror runs an Android foreground service so the camera can continue capturing and streaming to the controller even when you leave the LocalCam Mirror screen, switch to another app, or lock the device. While this service is active:

• The camera, and (only while you are recording) the microphone, remain in use on the host device.
• The local Bluetooth / Wi-Fi connection to the paired controller device remains active and continues to carry encoded preview frames and control messages.
• A persistent notification is shown on the host device for the entire duration of the session, so it is always visible to you that the camera is in use. The notification includes a Stop sharing action that ends the session immediately.
• No camera, microphone, or connection data is captured or transmitted while the foreground service is not running. The foreground service stops automatically when the paired controller disconnects, when you tap Stop sharing in the notification, or when you stop advertising from the Camera Host screen.

Telegram alert forwarding (optional, off by default)

LocalCam Mirror can send motion alerts to a Telegram channel you own. This feature is off by default and only becomes active if you complete the setup wizard yourself.

What you set up. You create your own bot with Telegram's BotFather and choose your own channel or chat. The app never creates accounts on your behalf.

What is sent, and to whom. When forwarding is on and your camera detects motion, the app sends directly from your phone to Telegram's servers (api.telegram.org) over an encrypted HTTPS connection:

• the motion snapshot image for that event
• a two-line caption: what was detected (for example "Person detected"), the confidence percentage, your phone's model name (for example "SM-G991U"), and the time of the event
• if — and only if — you also switch on "Also send a video clip", a short copy of that event's recording: at most 60 seconds, re-encoded smaller and at lower quality, typically around 6 MB. It is a separate copy made for sending — your full-quality recording stays on the phone and is never sent. This option needs auto-record to be on, and a second setting can hold clips until the phone is on Wi-Fi.

No location is ever sent. No account, email, phone number, or contact information is ever sent, because the app never has any. Video is sent only if you switch on the video clip option described above; with that switch off — which is how it ships — no video leaves your phone.

We never receive it. We run no server and are not in the path. The data goes from your phone to Telegram and into your channel.

Answering commands (optional). When you enable Telegram commands, this app reads messages sent to your own Telegram bot so it can answer them. Messages are processed on your device and are not sent anywhere else. Only the account you set up may command the camera; messages from anyone else are ignored and not stored. Replies — a photo, a short clip of the most recent event, or a short status of battery, free storage and detection state — go to the same Telegram chat you chose. Turning the switch off stops the app reading messages at all.

Telegram is a third party. Once your alerts arrive in Telegram, they are handled under Telegram's own privacy policy and terms, not ours. Telegram can access messages sent through the Bot API. Please review Telegram's privacy policy before enabling this feature.

Your bot token. Your token is stored encrypted on your device and is never sent to us and never sent to your other phone. Disconnecting Telegram in the app erases it.

Delivery log. The app keeps a local log of send attempts on your phone, so you can see whether alerts are getting through. It holds up to 200 records for up to 7 days, contains only outcomes and timestamps — never images, video, message text, or your token — and never leaves your device.

Turning it off and deleting your data. You can disable forwarding or disconnect Telegram at any time in the app, which stops all sending and erases your stored settings and token. Alerts already delivered live in your own Telegram channel: delete them there, or delete the bot in BotFather to revoke its access entirely.

Third-party SDKs

LocalCam Mirror uses the following third-party SDKs:

• Google Nearby Connections — local, encrypted device pairing and data transfer between your two phones.
• Google Play Billing — processes the optional Motion Pro subscription.
• Google Play In-App Updates & In-App Review — standard Google Play update/review prompts.
• On-device motion model (LiteRT) — person/vehicle/animal recognition runs locally on your device; no data leaves the device.
• Telegram Bot API — used only if you enable Telegram alert forwarding. Receives your motion alert photos and captions, sent from your device to your own bot and channel.

We do not use any analytics or tracking SDKs of our own.

Permissions

The app requests the following permissions:

• Camera — To capture the live preview and photos and to record video on the host device. Used by the foreground service so the camera can continue capturing while the app is in the background during an active session. See Background operation.
• Microphone — To include audio in video recordings. Only used while you are actively recording. Can be turned off in the app's Settings screen.
• Bluetooth and Nearby Wi-Fi Devices — Required by Google Nearby Connections to discover and connect to the other device over local wireless. No data is sent over the internet.
• Notifications — To show the persistent “LocalCamMirror is streaming” notification while the camera host's foreground service is active. You can revoke this in your system settings; the foreground service will still run, but you will not see the in-progress notification.
• Storage and Media — To save captured photos and recorded video files to your phone's gallery in the Pictures/LocalCamMirror and Movies/LocalCamMirror folders.
• Internet — Used for subscription handling, app updates, and, only if you enable it, Telegram alert forwarding.

Children's privacy

LocalCam Mirror does not knowingly collect any information from anyone, including children under 13. Since no data is collected at all, the app is compatible with COPPA requirements.

Changes to this policy

If the app is updated in a way that changes how data is handled, this policy will be updated and the effective date revised. The current version will always be available at the URL registered with Google Play.

Contact

If you have questions about this privacy policy, contact us at:

aimotioncoach@gmail.com

Your camera feed, photos, recordings, and the connection between your two phones never leave the local link between them and never touch our servers — we do not run any.

No video, audio, photos, or personal data ever reaches us, or any server we operate — we operate none. The only data that can leave your two-device local session for a third-party service is the Telegram alerts you switch on yourself, described above, and they go to a Telegram channel you own.