Browser-first document reading
PDF, Word, PowerPoint, text and Markdown sources are read on the device when the editor can parse them. The editor reports unsupported, protected or unreadable files instead of silently guessing.
A transparent beta needs clear boundaries. This page describes the current product flow and the security work being completed before public release.
Buzzuro’s current document flow reads supported source material in the browser and prepares text for the quiz-generation workflow. The product does not need the original file uploaded merely to extract text. Accounts and saved quizzes use the application’s hosted data services, while live rooms use the realtime room flow. Do not place confidential or regulated material into a beta product until your organization has reviewed the current privacy and processor details.
Start with a topic or supported material, then review the questions before the group sees them.
Open a live lobby and show the QR code or room code on the host screen.
Players answer in their browsers while the host keeps the pace and moves the round forward.
PDF, Word, PowerPoint, text and Markdown sources are read on the device when the editor can parse them. The editor reports unsupported, protected or unreadable files instead of silently guessing.
Saved host data and live room state are separate product concerns. Room codes are for joining a session, not a replacement for access control or a promise of long-term storage.
Security headers, rate limits, privacy documentation, account deletion cleanup and production monitoring are part of the pre-release hardening checklist. Public release should wait until those controls are verified.
Not during the invite-only beta unless your organization has reviewed and approved the current data flow. Use non-sensitive sample material while evaluating Buzzuro.
The maker page explains the beta status, while this security page records the current source-material and live-room boundaries. Both should be updated when the implementation changes.