Last updated: 7 October 2026. This policy covers the LayerLink Android app (package com.layerbit.layerlink) specifically — what it captures, what it sends anywhere, and what it doesn't. It is separate from the general Layerbit website privacy policy, which covers this website's own advertising, analytics and cookies; none of that applies to the app, since the app contains no advertising SDK, no analytics SDK, and sets no cookies.
What LayerLink does
LayerLink lets you broadcast your Android device's screen to a viewer's web browser in real time, over a direct peer-to-peer connection. You start a broadcast, LayerLink generates a session link, and whoever opens that link in a browser sees your screen live. There is no account, no sign-up, and no login anywhere in the app.
Screen capture
LayerLink uses Android's MediaProjection API to capture your device's screen, running inside a foreground service (permission FOREGROUND_SERVICE_MEDIA_PROJECTION) with a persistent notification for as long as a broadcast is live — this is what keeps the capture running and visible to you even while you're using another app. Android shows its own system permission dialog every time before capture can start, naming exactly what you're about to share, and requires this to be a foreground service specifically so the capture cannot continue silently once you leave the app.
The captured video frames are never uploaded to or stored on a Layerbit server. We do not record your broadcasts. We have no ability to view, retain, or replay a session after it ends, because we never receive the video in the first place — it is encrypted in transit using WebRTC's mandatory DTLS-SRTP the entire way, regardless of which path below it takes.
Signaling, and the two paths your video can take
Two devices that have never met can't establish a connection without some third party introducing them. LayerLink uses Google Firebase Realtime Database for exactly that introduction, and nothing else:
- When you start a broadcast, LayerLink writes a short-lived record under a random session ID: the WebRTC offer, and as your viewer connects, the answer and ICE candidates (network address information needed to negotiate a connection).
- This record contains no video, no audio, and no identifying information about you — no name, no email, no device ID, no account, because the app has none of these to send.
- The record is actively deleted from Firebase the moment you stop the broadcast — LayerLink issues an explicit delete against that session's data as part of ending the session, rather than leaving it to expire on its own.
- A session ID is only useful while its record exists. Anyone holding a live session's link could attempt to join it while it's active, so treat a LayerLink link like a temporary password and only share it with someone you intend to let view your screen.
Firebase only ever carries that connection-negotiation data, never the video itself. The video takes one of two paths, decided automatically by the two devices' networks, not by anything LayerLink chooses:
- Direct, peer-to-peer (the common case). Most of the time both devices can reach each other directly once they know each other's network address, and the video travels straight from broadcaster to viewer with nothing in between.
- Relayed through a TURN server (when a direct path isn't possible). Some network combinations — most often two devices on different mobile carriers in different countries, each behind their own carrier-grade NAT — can't reach each other directly no matter what. WebRTC's standard fallback for exactly this case is a TURN relay: LayerLink uses ExpressTURN, a third-party relay service. If you enter your own relay under Relay server in the app, that one is used instead. In this case your still-encrypted video does pass through the relay server to get from one device to the other. It is not decrypted there, not logged by LayerLink, and we have no visibility into what that relay does or doesn't retain beyond its own stated purpose of relaying the connection — so if this matters to you, the relay operator's own policies, not ours, govern that relay.
What the app does not do
- No advertising SDK of any kind, and no ads shown anywhere in the app.
- No analytics or crash-reporting SDK. We don't know how often you open the app, how long a session runs, or what device you're using, because nothing in the app reports that anywhere.
- No account system, no login, no password, and nothing to reset if forgotten — there's simply nothing stored server-side tied to you.
- No access to your contacts, photos, files, location, microphone, or camera. LayerLink requests exactly two things beyond normal app permissions: the screen-capture permission described above, and "display over other apps," used only to show the floating Stop control while a broadcast is live so you can end a session without reopening the app.
- No data sold, rented, or shared with any third party for advertising or any other purpose. Firebase and, when a direct connection isn't possible, the TURN relay — both described above — are the only infrastructure the app talks to, and neither receives anything beyond what's described there.
Your rights over your data
Because LayerLink stores nothing tied to you beyond a signaling record that's deleted when your broadcast ends, there is, in practice, very little for a data request to act on. If you have a question about what a specific session might have left behind, or believe something was retained that shouldn't have been, email us at ceo@layerbit.co.in and we'll look into it and respond directly.
Children's privacy
LayerLink is a general-purpose screen-sharing utility, not directed at children, and we do not knowingly collect personal information from anyone under 13 (or the equivalent minimum age in your jurisdiction) — in any case, the app has nothing resembling a profile or account to collect that information into.
Changes to this policy
When this policy changes we update the date at the top. A change that adds a new capability which touches data — audio transmission, remote control, or any server-side storage, for example — would be reflected here before that capability ships, not afterwards.
Contact
Questions about this policy, or about LayerLink specifically: ceo@layerbit.co.in.