1. Who is responsible for the portal
BringLive Digital (Pty) Ltd operates BringLive Meet. This notice describes the data handling designed into the supplied portal. It does not claim regulatory approval and must be reviewed against the final production hosting, payment and media providers before launch.
2. Information the portal may process
- Account information: name, email address, password-derived verifier, plan and account timestamps.
- Security and session information: server session identifier, CSRF token, login failures, hashed IP evidence and audit-event metadata.
- Meeting information: room code, title, selected experience, scheduled time, host relationship and invitation token.
- Live meeting information: participant names, chat and room state are processed for the live session. Live-chat retention depends on the enabled service configuration and the applicable customer terms.
- Media: camera, microphone and screen-share streams are processed when you permit them. Recording is initiated by an authorised user action and is subject to the applicable recording notice and enabled service configuration.
- Billing: where hosted billing is enabled, the billing provider receives the account or subscription information needed to provide that service. Full payment-card details should be entered on the billing provider’s hosted payment pages rather than the BringLive Meet marketing website.
3. Smart Mic and face-presence assistance
Smart Mic voice-activity analysis runs in the browser. Optional face-presence detection, where the browser supports it and the user enables it, is intended only to detect whether a face is present; this build does not perform identity recognition or emotion analysis and does not upload face images for that feature.
4. Why information is used
Information is used to create and secure accounts, provide meeting rooms, enforce host/plan permissions, deliver requested media functions, prevent abuse, support billing, diagnose faults and meet legal or security obligations.
5. Legal basis and transparency
The appropriate lawful basis depends on the final production relationship and purpose. Account/service processing will generally be necessary to provide the requested service; some optional functions rely on user choice or consent. BringLive Digital must complete a production POPIA assessment before commercial launch.
6. Service providers and international processing
Production may use providers such as managed hosting, Stripe for billing and LiveKit/TURN infrastructure for media. Their exact identities, regions and contractual safeguards must be confirmed in the production notice before customers are onboarded. Some providers may process information outside South Africa.
7. Retention and deletion
The supplied local pilot keeps account, meeting and audit data in its local database until the database is deleted or the account environment is reset. A production retention schedule must be configured and published before commercial launch. Privacy/deletion requests can be sent to info@bringlivedigital.com.
8. Security
BringLive Meet uses layered account, session, request-integrity, rate-limiting, invitation and audit controls appropriate to the service stage. No internet system is risk-free; secure hosting, access management, backup, monitoring and incident handling remain part of operating the service responsibly.
9. Your choices and rights
Depending on applicable law and context, data subjects may ask about personal information, request correction or deletion, object to certain processing, withdraw consent where processing relies on consent, and complain to the Information Regulator. Identity verification may be required before acting on a request.
10. Security compromises
BringLive Digital's production incident process must evaluate and notify security compromises in accordance with applicable POPIA requirements. The Information Regulator currently provides an eServices route for section 22 security-compromise reporting.
11. Changes
Material changes to this notice should be versioned. New users must accept the current Terms and acknowledge the current Privacy Notice during registration.