Privacy Policy for SecureCam
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.
- Recordings are saved in the app's private storage on the camera phone.
- Motion detection and the optional smart alerts (detecting people, vehicles and animals) run entirely on the camera phone using an on-device model. Images are not sent anywhere for analysis.
- Recordings are deleted automatically according to the retention settings you choose (number of days and maximum storage), or when you uninstall the app.
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:
- On the same Wi-Fi (home): the camera accepts connections on your local network over TLS (HTTPS). The camera creates its own encryption key on the phone, and the viewer only trusts the certificate it was shown in the pairing QR code. To find the camera again when its address changes, the camera announces itself on your local network with a service name and a random camera ID (no name, picture or location). You can turn this off in the camera's settings ("Allow viewers on this Wi-Fi").
- From anywhere (Tailscale): phones connect over Tailscale, a private network you sign in to and control yourself, either with the separate Tailscale app or with Tailscale built into SecureCam (Settings → "Away from home: Tailscale"). When you sign in with the built-in option, you log in on Tailscale's own web page; SecureCam never sees your password. Your phone then registers as a device in your Tailscale network, which means Tailscale receives information needed to connect your devices: a device name (for example "securecam-front-door" or "securecam-viewer-" plus the phone model), the operating system, network addresses and encryption public keys. SecureCam turns off Tailscale's optional diagnostic log uploads. Traffic between your devices is end-to-end encrypted with WireGuard; when a direct path isn't possible it may pass through Tailscale's relay servers, which cannot read it. You can sign out in the app at any time and remove the device in your Tailscale admin console.
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.
- Your viewer phone gets a push token from Google's Firebase Cloud Messaging (FCM) and gives it to your cameras directly (over Wi-Fi or Tailscale).
- When motion is detected, the camera sends a small wake-up request to our push relay, hosted on Cloudflare Workers. The request contains only the viewer's FCM token, a camera ID and an event number. It never contains images, video, audio, camera names or locations.
- The relay passes the wake-up to FCM and does not store the token or the IDs. It keeps only anonymous counts of successes and errors, and applies rate limits that use the token and the sender's IP address for up to a minute. Cloudflare processes these requests as our hosting provider (cloudflare.com/privacypolicy).
- FCM then delivers the wake-up to your phone as Google's service, under the Firebase terms (firebase.google.com/support/privacy). The viewer fetches the alert's details directly from your camera.
5. What we do not do
- No SecureCam account. Our only server is the push relay described above, and it never receives your recordings.
- No advertising, no advertising ID, no analytics, and no crash-reporting SDKs.
- We do not sell or rent your information, and we do not share it except as described above to deliver push alerts.
- No location, contacts or other personal data is collected.
6. Permissions the app uses
| Permission | Why |
|---|---|
| Camera | Camera mode: live view and motion-triggered photos and video. |
| Microphone | Camera 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. |
| Notifications | Motion alerts and camera status. |
| Internet and network state | Talking 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 startup | Lets 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
- Delete recordings by lowering the retention settings, or by clearing the app's storage or uninstalling it on the camera phone.
- Remove a camera from a viewer, or generate a new pairing code on the camera to unpair all viewers.
- Turn off cloud upload or sign out of your cloud account in settings; files already uploaded stay in your account until you delete them there.
- Switch alerts from push to polling at any time.
- Sign out of the built-in Tailscale in settings, and remove the device from your Tailscale admin console.
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