Privacy Policy

This Privacy Policy explains how Pixelogy collects, uses, stores, and protects information when you use the Pixelogy website, customer portal, fleet activation service, on-prem Pixelogy Control software, render-node agents, and the Pixelogy Zoom integration.

Pixelogy deployments are commonly operated on customer-controlled networks. In those deployments, the customer controls the projects, media, operators, meetings, render nodes, and local control-plane data. Pixelogy processes hosted portal, fleet activation, update, support, and account data as described below.

Account and contact information, such as names, email addresses, organization names, support contacts, and administrator/operator account details.

Portal and control-plane information, such as login events, roles, permissions, project metadata, node assignments, update status, audit logs, and support diagnostics.

Render-node and fleet information, such as node identifiers, hardware fingerprints, license status, software versions, activation certificates, IP addresses, telemetry, service health, and update history.

Project and media metadata, such as project names, scene structures, surface configuration, asset names, and operational state. Customer media files are normally stored and processed on customer-controlled infrastructure unless a customer explicitly uploads them to a hosted Pixelogy service.

Zoom integration information, such as the connected Zoom account user ID, email address, OAuth tokens, meeting IDs, meeting links or passcodes entered by an operator, participant names or identifiers, meeting role/status, and short-lived authorization tokens needed to join approved meetings.

Website and technical data, such as browser type, device information, request logs, cookies or similar technologies used for authentication, security, analytics, and service reliability.

To provide, secure, maintain, and improve Pixelogy services, including fleet activation, customer portal access, render-node management, project deployment, diagnostics, updates, and support.

To authenticate users, enforce permissions, audit sensitive actions, prevent abuse, and protect customer deployments.

To operate the Zoom integration, including connecting an authorized Zoom account, creating Pixelogy-owned meetings when requested, minting short-lived Zoom authorization tokens, joining approved meetings as visible participants, and rendering meeting video into customer-controlled display outputs.

To communicate with customers about support, service health, security, billing, product changes, or requested account actions.

To comply with legal obligations, enforce agreements, and protect the rights, safety, and security of Pixelogy, customers, users, and third parties.

Pixelogy uses Zoom data only to provide the requested Zoom meeting integration. We do not sell Zoom user data, use it for advertising, or use it to train machine learning models.

OAuth refresh tokens are stored by the Pixelogy Control environment or hosted service that initiated the connection. Render nodes do not need long-lived Zoom OAuth refresh tokens. Nodes receive only the short-lived join information needed to connect to a meeting.

Meeting audio and video frames are processed transiently by the node-local Zoom Meeting SDK helper and Pixelogy compositor so the meeting can be displayed on customer-controlled outputs. Pixelogy does not retain Zoom meeting audio or video by default.

If a host or cohost grants local recording or a customer enables recording, resulting recordings or derived media are controlled by the meeting host, Zoom account settings, and the customer's Pixelogy deployment configuration.

We do not sell personal information.

We share information with service providers only as needed to operate Pixelogy, such as hosting, storage, deployment, logging, email, payment, support, security, and analytics providers.

We may share information with a customer administrator when the information relates to that customer's deployment, account, operators, nodes, projects, or support request.

We may disclose information if required by law, legal process, or to protect the rights, safety, and security of Pixelogy, customers, users, or third parties.

Hosted portal, fleet, activation, update, and support records are retained for as long as needed to provide the service, support customers, maintain security, comply with legal obligations, and resolve disputes.

On-prem control-plane data is retained according to the customer's local deployment settings and operational practices.

OAuth tokens are retained until the connected account is disconnected, the token expires or is revoked, the customer removes the integration, or deletion is requested where applicable.

Diagnostic logs and telemetry may be retained for a limited period for reliability, security, support, and audit purposes.

Pixelogy uses technical and organizational safeguards designed to protect information, including authentication, role-based access controls, encryption in transit, signed update packages, secret-file handling, audit logs, and restricted operational access.

No system is perfectly secure. Customers are responsible for securing their own networks, operator accounts, Zoom accounts, render nodes, and on-prem infrastructure.

You can disconnect a Zoom account from Pixelogy Control, revoke Pixelogy access from the Zoom App Marketplace, or ask your Zoom administrator to remove the app from your account.

Customers can request access, correction, export, or deletion of personal information by contacting Pixelogy. Some information may be retained when required for security, legal compliance, audit records, or legitimate business operations.

Operators should contact their organization's Pixelogy administrator for requests involving customer-controlled on-prem deployments.

Pixelogy is intended for business, live production, and professional display operations. It is not directed to children and should not be used by children.

Pixelogy and its service providers may process information in the United States, Canada, and other locations where we or our providers operate. Customers are responsible for configuring deployments in accordance with their own regional and regulatory requirements.

We may update this Privacy Policy from time to time. The updated version will be posted on this page with a revised effective date.

Questions or privacy requests can be sent to support@pixelogy.tech.