Room access
Hosts can control room visibility, share invite links, and block listener emails for their own room without changing the blocked user's broader account access.
Trust and access
Veravox separates public product information from authenticated live-session, account, billing, and artifact access.
Unauthenticated visitors must sign in before hosting or joining live sessions.
Publisher consoles, listener rooms, gateway admission, WebSocket tokens, session artifacts, and profile data remain protected.
Private-room passwords are stored as hashes; raw private-room passwords are not shown after refresh or sign-in.
Public pages do not reveal whether a private room alias exists.
Hosts can control room visibility, share invite links, and block listener emails for their own room without changing the blocked user's broader account access.
Production readiness includes authenticated-flow validation, billing guardrails, public-route checks, and deployment verification before public launch.