Effective date: 2026-10-22
Updated 2026-10-22: banners now appear on every screen.
This policy covers the Camlane Android app (the ad-supported ads build from GitHub Releases or Google Play, and the ad-free foss build you can compile yourself), the Camlane desktop app and camlane-cli. It is also published at https://aryan0078.github.io/camlane/privacy/.
ads build includes Google AdMob, which may collect data as described below. The foss build contains no third-party advertising, analytics or tracking SDKs.| Data | Where it goes | Who receives it |
|---|---|---|
| Camera video and microphone audio | over your local network, directly to the desktop you paired with | you only |
| Pairing PIN and token, paired-device list, settings, imported LUTs | stored on your phone and your computer | nobody |
| Discovery information: the desktop’s display name, OS and Camlane version; the phone’s model name and a random per-install ID | your local network only | devices on your local network and the desktop you connect to |
| Logs | stored locally; shared only if you paste them into a bug report yourself | nobody unless you choose |
ads build only: advertising ID, IP address, device and app information, ad interactions |
Google AdMob, when the phone is online (including while you stream) | Google, under Google’s policies (see below) |
Desktop GUI only: one HTTPS request for sponsors/desktop.json, at most once a day |
raw.githubusercontent.com (GitHub) |
GitHub receives the standard information of any web request (IP address, user agent) under the GitHub Privacy Statement. Camlane adds no cookies, identifiers or query parameters. |
ads build it is also used to load ads.ads build only): declared by the Google Mobile Ads SDK.ads build only)The ads build from GitHub Releases or Google Play shows banner ads from Google AdMob: one banner on each screen (the device list, the camera screen, settings, about and the QR scanner), and none in dialogs or sheets. Banners never cover the camera picture or any control. There are no full-screen, video, pop-up or app-open ads. The camera screen banner stays visible during a streaming session. It doesn’t request new ads until the stream ends. Ads do not load when the phone is offline.
Google may collect and use your device’s advertising ID, IP address, device information and ad interactions to deliver, measure and personalise ads. Read How Google uses information from sites or apps that use its services and the Google Privacy Policy.
foss flavor, which contains no ad SDK. See MONETIZATION.md.Camlane never passes camera, microphone or stream data to the ad SDK.
Camlane is not directed at children under 13 and does not knowingly collect personal information from children. Camlane itself collects no personal information from anyone.
The Camlane developers hold no data about you, so there is nothing for us to give you, correct or delete. To remove everything Camlane stores locally, clear the app’s data or uninstall it on Android, and delete the desktop config directory (~/.config/camlane, %APPDATA%\camlane or ~/Library/Application Support/camlane). For data collected by Google through ads, use Google’s controls linked above.
Version 1 of the streaming protocol is not encrypted. It is meant for networks you trust. Pairing uses a PIN that is never transmitted. See the security policy for the full threat model.
When this policy changes, the effective date above is updated. The full history is visible in the repository’s git log, and material changes are noted in the changelog and release notes.
Maintainer: Aryan Singh.