Event links and codes
Every event gets an unlisted listen link and a short code:
- Rotate at will - Changing the event code immediately invalidates previously shared links - useful between sessions or days.
- Separate surfaces - The interpreter console is protected by its own per-event access code; the broadcast console requires an organiser account. Attendees never see either.
- QR distribution - The QR code and link are distributed through your own channels - screens, badges, registration emails.
Paid and closed events
The standard pattern for ticketed events: the event link and QR code are delivered through your existing registration or ticketing emails, so only registered participants receive them. Rotating the code keeps forwarded links from living too long.
Interactive hybrid rooms are stricter: invited-only admission with per-email invitations, a waiting room for guests, a room lock and host moderation - suited to paid workshops and closed sessions.
If your format requires individually personalised, single-use links tied to your registration platform, we scope that integration together during event setup.
Security and privacy
- EU infrastructure - Production runs on Microsoft Azure within the European Union; processing is GDPR-compliant.
- Encrypted in transit - TLS for pages and signalling, encrypted WebRTC for media.
- No retention by default - Live audio is processed in real time and not retained unless you enable recording; recordings and transcripts belong to you.
- Cookie-light - The attendee listen page works without any non-essential cookies.
- Payments - Card payments are processed entirely by Revolut under PCI DSS; card data never touches Interpretwise servers.