Last updated
June 21, 2026
Who provides Audience Desk
Audience Desk is provided by Hashcode Fibration as a SaaS platform for radio and TV stations managing live audience messages.
Data we process
We process account details, workspace membership, billing records, provider connection metadata, and audience messages that a station chooses to ingest from connected channels such as Facebook, WhatsApp, and YouTube.
Google and YouTube data accessed
When a station administrator connects YouTube, Audience Desk uses Google OAuth and requests the YouTube read-only scope https://www.googleapis.com/auth/youtube.readonly. We use this access only so the station can connect YouTube channels or live broadcasts it owns or manages and route live audience messages into Audience Desk.
The Google user data we may access includes Google OAuth token metadata, the authorized Google or YouTube account identifier needed to maintain the connection, YouTube channel and live broadcast metadata available to the authorized account, live chat identifiers, live chat messages, commenter display names or channel identifiers when provided by YouTube, timestamps, message IDs, and related live chat metadata required to de-duplicate, route, moderate, cluster, and display live comments.
How Google and YouTube data is used
Provider data is used only to deliver the Audience Desk service: displaying, organizing, moderating, clustering, shortlisting, reporting on, and routing audience messages for live production workflows. Producers use this data to curate live audience comments for presenters and on-air teams.
Audience Desk does not use Google or YouTube data to upload videos, edit videos, delete content, post comments, send live chat messages, train generalized artificial intelligence models, serve advertising, retarget users, determine creditworthiness, or sell data. We do not request YouTube write scopes for the live-comment ingestion workflow.
Sharing Google and YouTube data
We share Google and YouTube data only as needed to provide Audience Desk to the station workspace that connected the account. Authorized station users such as tenant administrators, producers, and presenters may see connected channel metadata or curated live comments according to their role.
We may use subprocessors that host or operate the service, such as cloud infrastructure, databases, storage, email delivery, monitoring, and security providers. These subprocessors process data only for Audience Desk service delivery, reliability, and security. We do not sell Google user data or share it with advertising platforms, data brokers, or unrelated third parties.
Google API Services User Data Policy
Audience Desk's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Client control
Station administrators control which provider accounts and channels are connected. A station can disconnect a channel, request deletion, or close its workspace subject to operational, billing, legal, and security retention requirements.
Storage and protection
Audience Desk stores production secrets outside source code, encrypts provider tokens, protects data in transit, restricts access by workspace and role, and keeps operational logs and support access limited to what is needed to run and secure the service. Human access to workspace content is limited to authorized station users and time-bound support access when needed to resolve a customer support, security, or reliability issue.
Retention, revocation, and deletion
Default provider-message retention is six months unless a contract, law, security incident, or deletion request requires a different period. Station administrators can disconnect a Google or YouTube data source in Audience Desk. Disconnecting stops new YouTube access and removes the active connection for future ingestion. Users may also revoke Audience Desk access from their Google Account permissions page.
To request deletion of stored Google or YouTube-derived data, contact us through the contact page and include the workspace name and connected channel details. We will delete or anonymize eligible provider data unless retention is required for security, legal, billing, abuse-prevention, or contractual reasons.
Contact
Questions about this policy can be sent through the contact page.