What we collect
Workspace account details, contact form submissions, operations records, team access records, sales requests, support messages, and technical logs.
Privacy Policy
Privacy built around broadcast operations trust.
This plain-language policy explains how BroadSync should handle workspace users, contact forms, operations records, access, integrations, and operational data. Last updated: 25 June 2026.
Broadcast operations control from ingest to transmission.
Purpose
Operational use
Control
Customer-owned data
Access
Role-based path
No sale
No contact-list resale
Operating record
What we collect
Why we use it
Who sees it
Plain-language promise
Personal information should be used for clear operational purposes only.
BroadSync exists to help broadcast teams run cleaner operations. Data handling should support that purpose and stay proportionate.
Why we use it
To provide the workspace, support onboarding, improve the product, communicate with customers, secure the service, and meet legal obligations.
Who sees it
Authorized workspace users, approved service providers, and BroadSync support or operations people with a legitimate need.
What we do not do
BroadSync should not sell contact lists or use sensitive operational data outside the product purpose.
Customer rights
Broadcast organizations need practical control over workspace data.
Access and correction
Customers should be able to review and correct workspace records where the product permits.
Deletion and retention
Retention should be defined by account status, contractual needs, legal obligations, backup windows, and operational requirements.
Guest access
Guest and vendor access should be limited to the specific information needed for the workflow.
Questions
Privacy questions can be routed through the BroadSync contact page.
Policy clarity
Privacy commitments should stay clear as the product scales.
BroadSync keeps privacy language practical for operators, administrators, vendors, and reviewers who rely on the workspace.