Privacy Policy — MediaBeam Extension

Last Updated: January 2026

MediaBeam is a privacy-first tool for peer-to-peer file and text sharing using WebRTC. It does not collect, store, track, or transmit personal or sensitive data. MediaBeam does not require an account or login to use.

Data Collection

MediaBeam does not collect or store:

• Personal information
• Identifiers
• Browsing history
• Usage analytics
• Device or network information
• File contents
• File metadata

We do not use:

• Cookies
• Analytics trackers
• Fingerprinting techniques
• Advertising technology

MediaBeam does not collect, transmit, or sell personal or sensitive user data.

Local Data

MediaBeam stores the following locally on the user's device:

• Theme preference (light/dark) stored via localStorage
• Temporary network banner state stored via sessionStorage

No data is transmitted to any server from these values.

Transfer Behavior

Files and text are sent directly between devices over encrypted WebRTC data channels. No backend server ever receives file contents. MediaBeam does not log or store user data, file names, or metadata on any server.

TURN servers may relay encrypted WebRTC traffic only as a fallback for restricted networks. Relay operators cannot decrypt data.

Third-Party Services

MediaBeam uses the following infrastructure services:

• Ably Realtime (signaling) — exchanges WebRTC offer/answer messages
• Twilio TURN (fallback relay) — relays encrypted bytes when direct connection is blocked

These services do not have access to file contents or user identifiers.

Data Retention

MediaBeam retains no data. All transfers are ephemeral and exist only in-memory during the WebRTC session.

Permissions Justification

MediaBeam requests minimal permissions necessary to perform user-initiated actions such as copying room codes and received text.

MediaBeam does not request:

• Broad host permissions
• Tab access
• History access
• Storage access

Contact

Questions can be directed to: hello@wileydigital.tech