ReuseCam · Legal

Privacy Policy

Effective July 19, 2026 Version 1.1 Developer: WAISHAN Privacy contact: atujasonlin@gmail.com

1. Overview

ReuseCam turns a phone or tablet into a live camera that can be viewed from another compatible device or modern web browser on the same local Wi-Fi network.

This policy applies to the Android version of ReuseCam distributed through Google Play. It must not be reused for a separately distributed platform build unless that build's data practices have been verified against this policy.

ReuseCam is designed to work without an account or a developer-operated cloud service. WAISHAN ("we," "us," or "our") does not receive or store your live camera video, microphone audio, camera name, local connection details, or session links on our servers. The app does not include advertising, third-party analytics, or cloud recording in the version covered by this policy.

This policy explains what the app accesses and processes, how local device-to-device communication works, what remains on your device, and the choices available to you.

Privacy policy website hosting

This privacy policy page is hosted on a RackNerd server in the United States. The hosting infrastructure necessarily processes an IP address and basic request metadata transiently to deliver the page and protect the server. Ordinary HTTP access logging is disabled. The page does not use advertising, analytics, tracking scripts, or cookies. Operational security or error records, if generated, are used only to maintain and protect the website and are not used for profiling or advertising.

2. Information ReuseCam Accesses and Processes

2.1 Camera video

When you enter Camera mode and grant camera permission, ReuseCam accesses the selected camera to show a local preview. When you explicitly start broadcasting, the app sends the live video to a viewer that connects through your local network.

Camera video is processed in real time. ReuseCam does not record the video, save it to the app's storage, upload it to a developer-operated server, or use it for advertising or analytics.

2.2 Microphone audio

Microphone audio is optional. If you grant microphone permission and leave the microphone enabled when starting a broadcast, ReuseCam sends live audio to the connected viewer with the live video.

ReuseCam does not record the audio, save it to the app's storage, upload it to a developer-operated server, or use it for advertising or analytics. You can disable the microphone or deny its permission and continue using video without audio.

2.3 Local network and connection information

ReuseCam uses local network information, including the device's local IP address, a local port, and local network availability, to make the camera discoverable and establish a direct connection on the same Wi-Fi network. The app does not request precise or approximate location permission for this purpose.

When Camera mode is broadcasting, ReuseCam may announce the following information to devices on the same local network:

  • The camera name, which defaults to a device model name and can be changed by the user.
  • The device model used to describe the nearby camera.
  • A random broadcast-session identifier used to distinguish nearby cameras. A new identifier is generated each time you start a broadcast, it is not stored, and it becomes meaningless when the broadcast stops.
  • A local session address and a random session token used to connect to the current broadcast.

This information is used only for local discovery and connection. It is not sent to or stored by us. Because other devices on the same local network may be able to see discovery announcements, use a trusted Wi-Fi network and do not put personal information in the camera name.

2.4 Local preferences

ReuseCam stores the following information locally on the device:

  • Your selected video quality.
  • Your camera name.

These values are not associated with a ReuseCam account because the app has no account system. They remain in the app's private local storage until you clear the app's data or uninstall the app.

2.5 Session links and tokens

Each time you start broadcasting, ReuseCam creates a random session token and includes it in the local watch link and QR code. The token is used to limit access to that broadcast. It expires when you stop broadcasting, and a new token is created for the next session.

The session token is also included in the local discovery announcement so compatible Viewer devices can connect automatically. Devices on the same local network that actively inspect discovery announcements may therefore be able to obtain the current token and attempt to connect. Treat the network, link, QR code, and discovery session as trusted only while broadcasting, and stop the broadcast when it is no longer needed.

3. How Device-to-Device Transmission Works

Live video and optional audio are transmitted through WebRTC between the camera device and the viewer. WebRTC media is encrypted while in transit. ReuseCam does not operate a relay, media, analytics, or recording server for this connection.

Local discovery, the watch page, and connection signaling may use local HTTP, WebSocket, and mDNS traffic that is not protected by HTTPS/TLS. These communications stay within the network path selected by your device, but other parties controlling or connected to an untrusted network may be able to observe local connection details. Use ReuseCam only on a network you trust, protect the session link, and stop the session immediately if you believe the link or network is not secure.

Guest Wi-Fi, client/AP isolation, VPN routing, firewalls, or enterprise network policies may block discovery or connections. ReuseCam does not bypass these controls.

4. Permissions

Depending on your device and Android version, ReuseCam may request or use these permissions:

  • Camera: Required to show a preview and broadcast live video in Camera mode.
  • Microphone: Optional; used only to include live audio in a broadcast.
  • Notifications: Used to show an ongoing notification while broadcasting and provide a visible way to return to or stop the session.
  • Network and Wi-Fi access: Used to detect local connectivity, host the local watch page, establish the direct stream, and discover nearby ReuseCam cameras.
  • Foreground service permissions: Used to keep a user-started camera and optional microphone session active while the broadcast is running.

You can manage runtime permissions in Android Settings. If you revoke camera permission, Camera mode cannot provide video. If you revoke microphone permission, you can continue with video only. Notification restrictions may affect how the ongoing broadcast notification appears.

5. Information WAISHAN Does Not Receive

In the version covered by this policy, WAISHAN does not collect or receive through a developer-operated server or service:

  • Account credentials, because ReuseCam has no account system.
  • Names, email addresses, phone numbers, postal addresses, contacts, or precise location.
  • Camera video or microphone audio on our servers.
  • Photos, videos, or other files from your device storage.
  • Advertising identifiers.
  • Purchase or payment information.
  • App usage analytics, advertising profiles, or cross-app tracking data.
  • Cloud crash reports or diagnostics sent to us.

Google Play and your device or operating-system provider may independently process store, installation, security, or diagnostic information under their own terms and privacy policies. That processing is not controlled by ReuseCam and is not described as our collection in this policy.

ReuseCam does process and transmit certain information directly between devices as described in Sections 2 and 3. Google Play's Data safety terminology may classify an off-device transfer as "collected" even when WAISHAN does not receive the data.

6. Sharing and Sale of Information

We do not sell personal information. We do not share your camera video, microphone audio, local preferences, identifiers, or session links with advertisers, data brokers, analytics providers, or other third parties.

When you start a broadcast, ReuseCam announces local connection information to compatible devices on the same local network. A device that obtains the current session token may attempt to connect; ReuseCam permits at most one active Viewer. After a Viewer connects, the app transmits live media directly to that Viewer. This is a user-initiated device-to-device transfer, but local discovery is visible more broadly than a privately delivered QR code. Choose the network, camera placement, and connected Viewer carefully.

7. Data Retention and Deletion

We do not maintain a ReuseCam user database or retain your live media on our servers.

  • Live video and audio are processed in real time and are not recorded by ReuseCam.
  • A session token and the broadcast-session identifier are valid only for the current broadcast and become invalid when the broadcast stops. Neither is stored.
  • Camera name and video quality remain in the app's private local storage until you clear app data or uninstall ReuseCam.

To delete all ReuseCam data stored by the app on your device, use Android Settings to clear the app's storage or uninstall the app. Because there is no ReuseCam account or developer-hosted user record, there is no server-side account to delete. You may contact us at atujasonlin@gmail.com if you have a privacy question or believe you sent information to us through a separate support interaction.

Information that you voluntarily send by email or another support channel is outside the app's local camera connection. We will use it to respond to your request, retain it only as reasonably necessary for support, security, legal, or recordkeeping purposes, and delete it when it is no longer needed, subject to applicable law. Do not send camera footage, active session links, or session tokens in support messages.

8. Security

We use a privacy-minimizing architecture intended to keep live media on the user's local network and outside developer-operated servers. ReuseCam uses encrypted WebRTC media, random session tokens, a visible broadcasting state, an ongoing foreground notification, and a user-controlled Stop action.

Live video and audio are carried over encrypted WebRTC channels. Discovery announcements and connection signaling (the local web page, session link, and connection setup messages) travel over the local network without TLS. A publicly trusted certificate is generally not available as a zero-configuration solution for an arbitrary private LAN address, while self-signed or private-CA certificates are not trusted by browsers by default. This is why ReuseCam should be used on a trusted Wi-Fi network.

No method of transmission or software security is perfect. A session token is a limited local access control, not a complete security boundary against someone who controls the network or obtains the session link. ReuseCam is not designed for hostile or public networks and is not a certified security, medical, or child-safety system.

9. Children's Privacy

ReuseCam is intended for adults and is not directed to children under 13 or the minimum age required by local law. The app may be used by an adult to view a room in which a child is present, but it does not create a child profile or intentionally collect personal information from children on our servers.

ReuseCam does not replace direct adult supervision or a certified child-safety or medical device. If you believe a child has sent personal information directly to us through a support channel, contact atujasonlin@gmail.com so we can review and delete it where appropriate.

10. International Use

ReuseCam does not transfer live media or local app data to a developer-operated server in another country. The direct local connection is controlled by the devices and network selected by the user.

If you contact us for support, your message may be processed in the country where WAISHAN operates or where the selected email service provider stores data. We will handle support information as described in this policy and as required by applicable law.

11. Your Choices and Rights

You can:

  • Choose whether to grant microphone and notification permissions.
  • Revoke permissions through Android Settings.
  • Turn the microphone off while using Camera mode.
  • Choose a non-personal camera name.
  • Choose the trusted local network on which discovery announcements and the session token are visible.
  • Stop a broadcast at any time, which disconnects the viewer and invalidates the session token.
  • Clear local app data or uninstall ReuseCam to delete locally stored preferences.
  • Contact atujasonlin@gmail.com with privacy questions or requests relating to information you submitted directly to us.

Depending on where you live, privacy law may provide additional rights concerning personal information held by a business. Since we do not receive the app's live media or local connection data, we generally cannot identify or retrieve it from our systems. We will respond to requests concerning support information that we actually hold, subject to verification and applicable law.

12. Changes to This Policy

We may update this policy when ReuseCam's features, data practices, legal requirements, or distribution channels change. We will update the effective date at the top of this page and, when required, provide additional notice in the app or on the store listing.

If a future version adds accounts, cloud relay, recording, analytics, crash reporting, advertising, payments, remote access, or other data processing, we will update this policy and the Google Play Data safety disclosure before releasing that version.

13. Contact

Developer: WAISHAN

Email: atujasonlin@gmail.com