Privacy Policy for SecureCam

Effective date: 2026-10-29 (previous version: 2026-10-26)

App: SecureCam: Phone Security Cam (package dev.mjandroid.securitycamera)

Developer: MJ Android Dev (Manoj Singh Rawal, https://mjandroid.dev) ("we", "us")

Contact: mjandroiddev@gmail.com

Policy URL: https://mjandroid.dev/securecam/privacy

SecureCam turns a spare Android phone into a motion-triggered security camera, and another phone into the viewer that watches it. This policy explains what happens to the photos, video and audio the app records, and to any other information it handles.

The short version: we never receive your recordings. Cameras and viewers talk directly to each other, encrypted, over your home Wi-Fi or your own private Tailscale network. Recordings stay on the camera phone, or go to the cloud storage account you connect yourself. The only server we run is a small relay that delivers push alerts; it sees only a device token and two ID numbers, never images, video or sound.

1. What the app records

When you use a phone in Camera mode and it is armed, SecureCam uses the camera and, if you turn it on, the microphone to record photos, video and audio when it detects motion, or when you tap Record now. You choose what is recorded, when (schedules), and where in the picture (detection zones) in the app's settings.

2. How your devices talk to each other

A phone in Viewer mode connects directly to your camera phones to show live video, events and recordings, and to change settings. Each viewer must first be paired using a code shown on the camera. SecureCam does not use public links or port forwarding, and no SecureCam server sits between your phones. There are two ways the phones reach each other:

Tailscale is a separate service with its own terms and privacy policy (tailscale.com/privacy-policy).

3. Optional cloud upload (your own account)

If you turn on cloud upload, the camera phone uploads its recordings to your own Google Drive, Dropbox or Box account. You sign in with that provider in your browser and grant access; the app stores the access tokens only on your phones. Uploads go straight from your camera phone to the provider over HTTPS. We never see the files or the tokens. The provider's own privacy policy applies to files stored there. You can sign out in the app's settings at any time, and revoke access from your provider account.

4. Push alerts (relay and Firebase Cloud Messaging)

To tell a viewer phone about motion even when the app is closed, SecureCam uses push alerts by default where Google Play services is available. You can switch to Polling in the viewer's settings, in which case the viewer checks your cameras directly and none of the following is used.

5. What we do not do

6. Permissions the app uses

PermissionWhy
CameraCamera mode: live view and motion-triggered photos and video.
MicrophoneCamera mode: audio recordings, only if you enable audio.
Foreground service (camera, microphone)Keeps the camera watching with the screen off, with a visible notification while it runs.
Foreground service (special use)Viewer mode: periodically checks your own cameras for motion alerts when you choose Polling instead of push alerts.
NotificationsMotion alerts and camera status.
Internet and network stateTalking to your devices over your Wi-Fi or Tailscale, sending push wake-ups through the relay and, if enabled, uploading to your cloud account.
Ignore battery optimization, wake lock, run at startupLets the camera keep running overnight and remind you to resume it after a restart.

7. Recording other people

SecureCam is meant for watching your own home and property. You are responsible for using it lawfully: many places require you to tell people when they are being recorded, and some restrict recording audio or recording areas you do not control.

8. Children

SecureCam is not directed at children and is intended for adults aged 18 and over.

9. Security

Connections between your phones are encrypted (TLS pinned to your camera's certificate on Wi-Fi, WireGuard over Tailscale) and require a per-camera pairing code. Uploads to cloud providers and push requests use HTTPS. Recordings and settings are kept in the app's private storage on your phones. No method is perfectly secure, so keep your phones and your Tailscale account protected.

10. Your choices and deletion

Because we do not keep your data (the push relay stores nothing), there is nothing for us to access or delete on our side. If you have a question, contact us at the address below.

11. Changes to this policy

If we change this policy, we will update this page and the "Effective date" above. Significant changes will also be noted in the app's release notes.

12. Contact

MJ Android Dev (Manoj Singh Rawal) · mjandroiddev@gmail.com · https://mjandroid.dev