YouTube source data
V1 is scoped to public YouTube comments obtained through supported API-based workflows. The app should display YouTube as the data source and keep links back to original comments when available.
Trust and compliance
AudienceCue is designed around official data access, export transparency, and user-controlled analysis. This page summarizes the operating rules that should be visible before a user pays or uploads work.
Plain-language baseline
We process public YouTube comment data for the user who starts the job, keep source metadata attached to exported rows, and route payments through Creem. This page summarizes the customer-facing operating rules for paid AudienceCue use.
V1 is scoped to public YouTube comments obtained through supported API-based workflows. The app should display YouTube as the data source and keep links back to original comments when available.
CSV and JSON exports are generated from stored job rows so users can inspect the same evidence behind each report. AudienceCue keeps account-associated jobs, exports, and reports available according to the retention and deletion rules in the Privacy Policy.
Reports summarize patterns, risks, questions, and representative comments. AI output should remain reviewable and should not auto-post replies or take channel actions without user confirmation.
Checkout and subscription records are handled by Creem. Users should have a visible contact path for billing, account, privacy, and data deletion requests.
Legal note: this page summarizes AudienceCue operating rules for customers. The Privacy Policy, Terms of Service, Refund Policy, and contact page provide the controlling customer-facing references.