The picture stays local.
The native local-network sharing flow sends the screen from host to viewer. Bavua’s account APIs do not receive or store that screen stream.
CLEAR INFORMATION. MORE INFORMED CHOICES.Your space.
Your space.
Clear boundaries.
What stays on your network, what our services handle, and the choices that help keep your workspace yours.
01 / TWO DIFFERENT PATHS
A screen stream. An account service.
They do different jobs, and it helps to know the difference.
Bavua servicesSign-in · device records · subscriptionsHTTPS
Account API traffic
Your MacNative host
Direct screen streamYour viewing deviceNative viewer
The account stays connected.
Sign-in, registered devices, hosting announcements, session records, and subscriptions use our backend services.
02 / KNOW THE CONNECTION
Use a network you trust.
The local screen stream is not encrypted in transit.
The current native local-network stream uses TCP without transport encryption. Keep your devices on a trusted network. Do not expose the streaming port to the public internet.
Account traffic between the apps and production Bavua APIs uses HTTPS (TLS). HTTPS protection for that API traffic does not make the separate local screen stream end-to-end encrypted.
Choose the screen or window you intend to share, review the receiving device, and stop sharing when you are done. macOS Screen Recording and Local Network permissions are controlled in System Settings.
03 / A LITTLE CONTROL GOES A LONG WAY
Your account. Your devices.
Signed account access.
Authenticated API requests use signed access tokens. The browser session refreshes through the backend and keeps its tokens in tab-scoped session storage.
Device-aware sharing.
Use the same account on your own devices. Review requests to view a screen, and remove devices you no longer use from your account.
Sign out on shared computers and keep your sign-in provider’s account secure. Account deletion and app-store subscription cancellation are separate actions.
04 / THE INFORMATION BEHIND THE EXPERIENCE
A clearer view of your data.
Account information
Sign-in provider details such as your name, email, account identifier, and profile photo URL.
Device and session records
Registered device details, network information, session times, connection metrics, and error reports used by the service.
Subscription records
The purchase identifiers and status needed to associate a store subscription with your Bavua account.
Service infrastructure
The project uses AWS for APIs, MongoDB Atlas for records, and Cloudflare for the website and delivery. The API deployment is configured for AWS eu-west-1.
05 / SOMETHING WE SHOULD LOOK AT?
Make a private connection.
RESPONSIBLE DISCLOSURE
Email the security team Found a suspected security issue?
Email a description, steps to reproduce, affected versions, and the potential impact. Share only what is needed to understand the issue; leave out passwords and private account data.