Registration and approval
Who may register, and who is approved to attend.
Security and privacy, governed by clear controls.
Understand how attendee access, audience evidence, recordings, transcripts, AI-assisted content and external connections are governed. Read the detailed policies in the Trust Center; we do not present unearned certifications.
Product screenshot, access rules and role assignment on a session
Architecture, not assurances
What we will and will not claim.
We do not claim a security certification here. Product controls and published policies answer different questions; review both before making a procurement decision.
Access decided before entry, not at the door
Registration, approval and admission are separate decisions. Entry depends on the selected admission mode and an eligible attendee identity.
- Organisers choose the admission mode for a webinar
- Personal-link and signed-in modes restrict forwarded-link access
- Replay requires a separate, current access decision and ready media
Access rules on a session
Roles that match the work being done
Privileged production access is separate from attendee admission. Roles determine which controls a person may use.
- Host, speaker and attendee permissions are distinct
- Backstage separated from the stage
- Moderation held by the people responsible for it
Role assignment
Tenancy kept apart
Workspace and webinar records are scoped to the organisation that owns them. Recording, transcript and derivative access depend on verified ready media and an authorized viewer or operator.
- Workspaces scoped to the organisation that owns them
- Media access must respect the same organisation boundary
- Attendee records not shared across tenants
Workspace scoping
Data handled for the purpose it was given for
Attendee information supports registration, delivery and appropriate follow-up. Transcript, AI-assisted and integration workflows also need purpose, access and retention boundaries. The linked policies govern processing and requests.
- Retention set out in the Data Retention policy
- Processing described in the Data Processing Agreement
- Subject requests handled through the Trust Center
Retention settings
What the product does
Where the controls live.
These controls have different scopes and eligibility rules; this summary is not a security certification.
Roles and moderation
Distinct surfaces for host, speaker, producer and attendee.
Tenancy
Workspaces scoped to the organisation that owns them.
Recording access
Playback needs ready media and a current content-access decision.
Retention
Held to the periods set out in the retention policy.
Requests
Subject and government requests handled through the Trust Center.
Keep reading
Where to go next.
Questions
Questions about security and privacy.
Does this page claim a security certification?
No. We do not claim a security certification here. Product controls and published policies answer different questions; review both before making a procurement decision.
Can a forwarded link get someone into a webinar?
Personal-link and signed-in admission modes restrict forwarded-link access. Entry depends on the selected admission mode and an eligible attendee identity.
How are roles separated?
Host, speaker and attendee permissions are distinct, backstage is separated from the stage, and privileged production access is separate from attendee admission.
Are organisations' records kept apart?
Workspace and webinar records are scoped to the organisation that owns them, and attendee records are not shared across tenants.
Where are retention, processing and requests covered?
Retention is set out in the Data Retention policy, processing in the Data Processing Agreement, and subject requests are handled through the Trust Center.