Files & privacy
This page describes what Beam actually does today — no promises we cannot verify.
Local mode (recommended)
- The file never leaves your computer; the browser opens and renders the PDF locally with PDF.js.
- Only the current page (as an image) is sent to the shared screen over WebSocket.
- The server relays and caches the latest frame in memory only — nothing is written to disk.
- Frames disappear when the server restarts or the meeting ends; reopen the PDF to restore them.
- Server logs never record frame content.
Upload mode
- Uploads from a phone, and PPTX conversion, send the file to the server that hosts this deployment.
- PDF: the source file and the rendered page images are stored on the server disk.
- PPTX: only the converted PDF and page images are kept; the original PPTX is deleted right after conversion.
- Page images and source files are deleted automatically when the meeting ends, when you leave, or when the host removes you. A cleanup job catches leftovers after server failures, within 7 days at most.
- Tapping Remove file on the phone deletes that presenter’s document immediately.
Who can see it
- Anyone with the 6-digit code can join the room; the host decides who goes on screen.
- Viewer questions go only to the host and never appear on screen.
- Page images are served under an unguessable random deck ID. There is no public listing, but anyone with the link can open it.
- Please don’t share the room code or deck links with people who shouldn’t have them.
Logs
Access logs record request path, status code, IP and latency for debugging and abuse prevention. They never record file or frame content.
Deletion & contact
To delete a file or a room early, contact whoever runs this deployment and include the room code and time. Rooms expire after 24 hours of inactivity; files are cleaned up right after the meeting ends.
Last updated: 2026-10-30