Thanks — you're asking whether agent or room metadata sent via Dispatch is secure. Good question. • Job/dispatch metadata is treated as customer content and can include personal data (IDs, names, phone numbers) and is available to the agent via the JobContext. • Metadata is protected by LiveKit’s security controls: TLS in transit, encryption at rest, access controls, and organizational safeguards (pseudonymization, audits, employee training). • Secrets (API keys, credentials) are stored in a separate secure secrets store and are not exposed in logs or the UI. • End-to-end encryption (E2EE) is supported for media and data channels, but job/dispatch metadata is not explicitly described as E2EE-protected — it is protected by the platform’s infrastructure and DPA-level safeguards instead. If you need stricter protection for specific fields, would you like guidance on: • encrypting sensitive metadata client-side before dispatching it, or • minimizing metadata sent in the job and storing sensitive values in the secure secrets store? Sources: Agent dispatch | LiveKit Documentation | Job lifecycle | LiveKit Documentation | Agent Builder | LiveKit Documentation | Data Processing Addendum | LiveKit | Introducing data tracks: realtime streaming beyond audio and video | LiveKi..., with interactive elements