Privacy

This page describes privacy-relevant behavior based on the current Bisha Remote architecture. It is not a substitute for a lawyer-reviewed policy.

Remote session content

Screen, input, clipboard, and file-transfer content for a session is peer traffic between the devices you connect. It is not intended to be stored by Bisha marketing websites.

Relay

When a relay is used, it is designed to forward encrypted peer traffic. Relay operators should not need session media in cleartext to forward packets.

Signaling

Signaling services see operational connection metadata required to introduce peers (for example device presence and session setup signals). That is not the same as receiving your desktop pixels.

Updates

Update checks fetch a signed manifest over HTTPS. They do not require a persistent website analytics identity. Production clients pin trust to the release-signing model described in product documentation.

Logging

Operational service logs may contain limited network and service metadata needed to run signaling/relay reliably. Clipboard, file, and screen content should not be logged by those services as part of normal design.

This website

The marketing site at bisharemote.com does not add fingerprinting or invasive analytics by default. Essential hosting logs from Vercel or Cloudflare may exist as part of normal web delivery.

Contact

Intended privacy contact: privacy@bisharemote.com — mailbox not confirmed operational yet.