Privacy Policy

1. What this policy covers

This policy applies to qube.so, the Qube dashboard, protected meeting rooms, Qube Computer, participant and second-device experiences, authorized recordings and review tools, APIs, and embedded players (together, the “Service”). It applies to organizations, account holders, hosts, participants, guests, reviewers, and people who contact Qube.

2. Who controls meeting data

The organization that creates a room chooses its participants, access policy, enabled controls, recording setting, reviewers, and retention period. For data Qube handles on that organization’s instructions, the organization is responsible for the meeting and Qube acts as its service provider or processor. Qube separately controls account, billing, security, abuse-prevention, and support data needed to operate the Service.

3. Information Qube collects

Account and organization information

Names, work email addresses, organization membership, roles, authentication metadata, account settings, billing status, and administrative activity.

Room and participant information

Room names, invitations, admission decisions, participant names and identifiers, join and leave times, permissions, device-qualification results, and room settings.

Workspace and meeting content

Files, links, application state, browser sessions, shared-computer activity, meeting media, screen content, chat, and other material participants choose to place inside a Qube room. Temporary workspace content is handled for the life of the room unless the organization enables a feature that saves or exports it.

Security and evidence data

Admission events, focus and fullscreen changes, protected-playback status, security level, session-specific forensic identifiers, acoustic events, paired-device status, and other security-relevant activity. When a host enables recording, Qube may also retain authorized video, audio, transcript, workspace activity, and supporting evidence on the same session timeline.

Support and service data

Messages sent to Qube, diagnostic information, service logs, performance data, and information needed to prevent fraud, investigate abuse, and keep the Service available.

4. What remains outside Qube

Qube does not use the ordinary meeting experience to inspect unrelated files, applications, messages, or processes on a participant’s personal computer. A higher-assurance room may require a paired second device to show the surrounding workstation or may enforce focus and fullscreen. The room must identify those controls before protected content is shown.

5. How Qube uses information

• Provide, secure, support, and improve protected rooms and Qube Computer.
• Authenticate users, enforce room policy, and respond to security events.
• Create an authorized recording or review record when the host enables it.
• Process billing, respond to support, and communicate service changes.
• Detect fraud, abuse, attacks, and violations of the Terms of Service.
• Meet legal obligations and protect the rights and safety of users and Qube.

Qube does not sell personal data. Qube does not use private meeting content or the authorized session record to train a general-purpose AI model.

6. Sharing and subprocessors

Qube shares information with the organization that controls the room, the participants and reviewers that organization authorizes, and service providers needed to run the platform. Those providers may include identity, database, object-storage, cloud compute, meeting-media, content-delivery, monitoring, billing, and email services. Qube may also disclose information when legally required, to protect the Service, or as part of a corporate transaction subject to appropriate safeguards. A current subprocessor list is available on request.

7. Disposal and retention

Disposable workspace state and retained meeting records have separate lifecycles. A disposable Qube destroys its temporary cloud computer and workspace when the meeting ends. That does not automatically delete an authorized recording, transcript, security event, exported artifact, account record, or information the organization is required to retain.

Organizations choose the retention period for authorized room records. When an organization deletes a retained record or its configured retention expires, Qube removes it from primary storage within 30 days and from backups within 90 days, unless a longer period is legally required. Account, billing, security, and support records are retained for as long as needed for the purposes described in this policy.

8. Participant notices and choices

Organizations are responsible for telling participants what the room will collect, whether recording is enabled, which higher-assurance controls are required, who can review the record, and how long it will be kept. Participants may decline to enter a room and should contact the host when they need an accommodation or an alternative process.

9. Access, correction, export, and deletion

A participant may ask the organization that controlled a room to access, correct, export, restrict, or delete session data. Qube will support the organization in responding as required by applicable law. Account holders can also request access or deletion of Qube-controlled account data by emailing privacy@qube.so. Qube may need to verify the requester’s identity before completing a request.

10. Security

Qube uses access controls, encryption in transit and at rest, isolated cloud execution, protected media, logging, and operational safeguards to protect the Service. Protected-playback capabilities vary by browser, operating system, hardware, and room policy. No technical system can eliminate every physical, human, or software risk. Qube will notify affected organizations as required when it becomes aware of a security incident that materially affects their data.

11. Children

The Service is built for organizations and professional meetings and is not directed to children under 16. Qube does not knowingly collect personal data from children under 16. Contact Qube if you believe a child’s information was submitted to the Service without appropriate authorization.

12. Changes to this policy

Qube may update this policy as the Service, law, or data practices change. Material changes will be announced by email, through the dashboard, or with another clear notice before they take effect. The effective date at the top identifies the version currently published.

13. Contact

Privacy questions and data requests can be sent to privacy@qube.so.