1. Scope and operator
MeetBridge is a RaketaLabs product. References to MeetBridge, RaketaLabs, we, us, or our mean the team that operates MeetBridge unless a signed customer agreement identifies a different contracting entity.
This policy applies to the MeetBridge website, web application, mobile application, booking pages, meeting rooms, organization workspaces, support interactions, and related services.
2. Our role and customer roles
For account administration, service security, billing, product operations, website activity, and direct support, RaketaLabs may act as an independent controller.
When a business customer uses MeetBridge for its meetings, invitees, employees, candidates, clients, or booking requesters, that customer generally determines why and how the meeting content is processed. In that context, the customer is generally the controller and MeetBridge generally acts as its processor under the applicable agreement.
If you participate in a customer-controlled workspace, privacy requests about meeting content may need to be directed to that customer. We will assist the customer as required by applicable law and contract.
3. Data we collect
We collect information you provide, information generated through use of the service, and limited technical information needed to operate and protect MeetBridge.
- Account and profile data: name, email, authentication identifiers, avatar, profile color, language, voice preference, security status, and account timestamps.
- Organization data: workspace identity, membership, roles, invitations, permissions, ownership, and administrative actions.
- Booking data: requester details, company, selected time, timezone, language, custom answers, request status, host assignment, and related communications.
- Meeting data: title, schedule, meeting code, participant identity and role, join requests, device preferences, chat, transcript, translation, summaries, decisions, actions, reactions, and timeline events.
- Speech and voice data: live audio segments needed to provide enabled speech features, selected generated-voice settings, and an optional voice reference and derived voice profile when a user chooses that feature.
- Uploaded content: profile images, organization logos, background images, files, and other content submitted through enabled product features.
- Technical and security data: IP-related security signals, device and browser information, application version, session information, logs, diagnostics, abuse-prevention identifiers, and cookie or local-storage preferences.
- Billing and support data: plan, entitlement, transaction status, customer messages, troubleshooting details, and records needed to manage a commercial relationship.
4. Sources of data
We receive data directly from users, from organizations that invite or manage users, from meeting hosts and participants, from booking requesters, from authorized account and payment services, and automatically from devices interacting with MeetBridge.
A host or organization may provide your name, email, meeting details, role, or booking context before you create an account or join a meeting.
5. Purposes and legal bases
We process data only when we have an applicable legal basis. The basis depends on the data, relationship, location, and feature.
- Contract and requested service: authenticate users, create accounts, manage workspaces, schedule meetings, provide live multilingual features, preserve authorized meeting history, and deliver support.
- Legitimate interests: secure the service, prevent fraud and abuse, diagnose failures, maintain reliability, understand product performance, and protect users, customers, RaketaLabs, and the public where those interests are not overridden by individual rights.
- Legal obligations: retain or disclose information when required for tax, accounting, sanctions, lawful requests, dispute handling, or other legal duties.
- Consent: used where required for optional processing, non-essential cookies, or a feature that applicable law requires to be consent-based. Consent can be withdrawn for future processing.
- Customer instructions: process organization-controlled meeting content on behalf of a customer under the customer agreement and Data Processing Agreement.
6. Meeting audio, transcripts, and generated features
When enabled, MeetBridge processes speech to provide live captions, translations, generated speech, summaries, decisions, action items, and searchable meeting history. Participants may receive translated text or generated audio based on another participant's speech.
Audio used for live processing is not treated as a permanent recording unless the product clearly indicates that recording is enabled. Final transcripts, translations, chat, summaries, actions, participant details, and meeting events may be stored for authorized meeting history.
Generated outputs may be inaccurate or incomplete. MeetBridge does not use those outputs to make solely automated decisions that produce legal or similarly significant effects about individuals.
7. Optional voice references
A personal voice reference is optional. If selected, a user provides a voice sample so MeetBridge can create a derived profile used to generate speech in that user's voice.
Users must provide only their own voice or a voice they are expressly authorized to use. Voice references must not be used for impersonation, fraud, harassment, identity abuse, or deceptive content.
A user can remove an optional voice reference from available account controls. Removal stops future use of that reference after operational deletion completes, but does not automatically remove authorized meeting records or generated audio already delivered during prior meetings.
8. When data is disclosed
We disclose data only as needed for the service, customer instructions, security, corporate operations, or law.
- Authorized workspace members, hosts, and participants according to meeting and organization permissions.
- Service providers that support hosting, storage, communications, authentication, payments, customer support, security, speech processing, translation, generated speech, and service analytics.
- Professional advisers, auditors, insurers, and transaction counterparties subject to appropriate confidentiality obligations.
- Authorities or other parties when disclosure is legally required or reasonably necessary to protect rights, safety, security, or the integrity of the service.
- A successor or relevant counterparty in a merger, financing, acquisition, restructuring, or sale, subject to applicable safeguards.
9. International processing
MeetBridge and its service providers may process data in countries other than the country where a user or customer is located.
Where required, international transfers rely on recognized safeguards such as adequacy decisions, contractual protections, supplementary measures, or another valid legal mechanism.
10. Retention
We retain personal data only as long as needed for the stated purpose, customer instructions, account administration, security, backup cycles, dispute resolution, and legal obligations.
- Account and organization records are generally kept while the account or commercial relationship remains active and for a limited period afterward.
- Meeting history, transcripts, translations, chat, summaries, and actions follow workspace settings, customer instructions, plan capabilities, deletion requests, and applicable legal requirements.
- Live audio segments used only for real-time processing are kept no longer than operationally necessary unless an explicit recording feature is enabled.
- Optional voice references and derived profiles are retained until removed, the feature is disabled, the account is deleted, or a shorter contractual period applies.
- Security, audit, transaction, and support records may be retained longer where necessary to prevent abuse, establish legal claims, or comply with law.
- Deleted data may remain in restricted backups until the applicable backup cycle expires.
11. Security
We use administrative, technical, and organizational safeguards designed to protect personal data, including access controls, authentication, scoped permissions, transport protection, logging, monitoring, and incident-response procedures.
No system is completely secure. Users must protect credentials, devices, meeting links, exported content, and workspace permissions and must promptly report suspected misuse.
12. Privacy rights
Depending on applicable law, individuals may have rights to know or access personal data, correct inaccurate data, request deletion, restrict processing, receive a portable copy, object to certain processing, withdraw consent, and complain to a supervisory authority.
California residents may also have applicable rights to know, delete, correct, limit certain uses of sensitive personal information, opt out of sale or sharing, and receive equal service. MeetBridge does not sell personal data for money. If a practice legally treated as sale or sharing is introduced, the required controls and notices will be provided.
We may need to verify identity and authority before completing a request. Rights can be limited by law, the rights of others, security needs, or the controller role of a customer workspace.
13. Children
MeetBridge is intended for business and professional use and is not directed to children under 16. Organizations must not invite minors or submit a minor's data unless they have a valid legal basis and all required permissions.
14. Changes and contact
We may update this policy to reflect legal, operational, or product changes. Material changes will be communicated through the service or another appropriate channel, and the effective date will be updated.
For privacy requests, security questions, Data Processing Agreement inquiries, or subprocessor information, contact RaketaLabs through the MeetBridge contact page. Include enough detail to identify the relevant account, workspace, booking, or meeting without sending unnecessary sensitive content.