Privacy Policy
Last updated: 5 August 2026
Who this covers
This policy covers members who subscribe to WebinarCaster, and registrants who sign up for a webinar run by a member. For registrant data, the member is the controller and WebinarCaster is the processor.
What we collect
Member data: name, email, password hash, subscription and payment status, workspace settings, and any integration credentials you save. Registrant data: name, email, optional phone, chosen session, attendance and watch time, chat and questions submitted in the live room. Technical data: IP address, browser type and basic usage events needed to run and secure the service.
Why we process it
To provide the service, authenticate you, enforce plan limits, deliver webinars and reminders, sync attendance to the CRM you connect, take payment, prevent abuse, and support you.
AI processing
Webinar transcripts and chat context are sent to an AI provider to generate simulated chat, FAQ answers and Q&A responses. On the Pro plan you may supply your own provider key, in which case that processing happens under your own provider account. Provider keys are encrypted at rest and are never sent to a browser.
Who we share it with
Infrastructure and database hosting, payment processing, email delivery, AI providers, and any CRM or webhook destination you configure. We do not sell personal data.
Retention
Member data is kept while the account is active and for a reasonable period afterwards. Registrant data is kept until the member deletes it or closes the account. You can request deletion at any time.
Your rights
Depending on where you live, you may request access, correction, export or deletion of your data, and object to certain processing. Contact us from the email on your account and we will respond within the period the law requires.
Cookies
We use cookies and local storage strictly to keep you signed in and to remember registration state in the live room. No advertising cookies are set by the app itself.
Security
Data is encrypted in transit, access is scoped per member at the database level, and provider keys are encrypted with a server-only key.