How we handle personal data submitted through this website — what we collect, why, who we share it with, and the rights you can exercise.
This draft must be reviewed by qualified counsel before it goes live. Every item marked «LIKE THIS» requires a factual answer only GoGo CTV can supply. It is a drafting aid, not legal advice.
It also assumes the analytics configuration described in section 4 remains true. If a CRM, tag manager, advertising pixel, or any additional cookie-setting tool is added, this policy must be updated before that tool goes live.
This policy covers personal data that GoGo CTV collects through this website, gogoctv.com — principally the information you choose to send us when you request a demo or get in touch.
It does not cover the GoGo CTV advertising platform. When a streaming publisher or platform uses our ad server to serve advertising to its viewers, that publisher is the controller of viewer data and GoGo CTV acts as its processor. Those activities are governed by the customer's written agreement with us and its accompanying data processing addendum, not by this website policy. If you are a viewer of a streaming service and want to understand how advertising data is handled, contact that streaming service directly.
A separate platform privacy notice and a customer-facing data processing addendum are needed. This page cannot serve that purpose, and the distinction above is only defensible if those documents actually exist.
For personal data collected through this website, the controller is GoGo CTV Inc., a Wyoming corporation trading as GoGo CTV, with its registered office at «REGISTERED ADDRESS».
You can reach us about anything in this policy at contact@gogoctv.com.
If GoGo CTV offers services to people in the EU or UK, an Article 27 representative may be required, and its name and address must be published here. Counsel should confirm whether that applies. Likewise, whether a Data Protection Officer must be appointed and named.
When you complete the demo request form on our contact page, we collect:
All of these are business contact details. Please do not send us sensitive personal data, and do not include personal data about other people in the free-text field.
If you email us directly, we receive your email address, your message, and anything you attach.
Our hosting provider records standard server access logs when a page or file is requested. These include:
We use these logs to deliver the site, diagnose faults, and protect against abuse and attack. We do not use them to build a profile of you.
This website uses Google Analytics 4 to understand how people find and use the site. It is the only measurement tool here: no tag manager, no advertising pixel, no session recording, no cross-site advertising tracking.
Google Analytics sets first-party cookies (_ga and _ga_<stream>) that give your browser a random identifier, so repeat visits count as one visitor rather than several. They hold no name, email address or other directly identifying detail.
If you are in the EEA, the UK, Gibraltar, the Channel Islands, the Isle of Man, Switzerland or California, no analytics cookie is set. We run Google Consent Mode with analytics storage denied by default in those regions, so Google Analytics falls back to cookieless measurement — we receive aggregate counts and nothing is stored on your device. Because nothing is stored on your device, we do not show a cookie banner.
We would rather state the limits of that than let it read as a stronger guarantee than it is. Two things remain true even where storage is denied. First, the Google tag still loads and still sends a cookieless request to Google — which carries your IP address, browser user-agent and the page URL, and Google processes it in the United States. Second, the regional denial depends on Google resolving your location correctly; a VPN, a corporate network that exits in another country, or a territory we have not listed can be read as somewhere else, in which case the default outside those regions applies and a cookie is set. There is currently no banner or control on this site for you to refuse either, and we will not pretend otherwise: we hold no identifier that would let us suppress a future visit on request, so an email asking us to exclude you is not something we could reliably act on. The controls that do work are in your own browser, and they are listed under “Turning it off” below.
The alternative is a consent management platform that withholds the tag entirely until a visitor opts in, which removes the cookieless-ping and geo-misresolution exposure described above at the cost of measurement coverage. That is a business decision, not a technical one, and it has not been taken. Until it is, this section must keep describing the residual exposure rather than implying there is none.
Everywhere else, analytics storage is enabled. Advertising storage, advertising personalisation and Google Signals are disabled in every region on every visit, without exception.
We also record one event when a demo request is submitted, so we can tell which pages produce enquiries. That event carries the role and volume range you selected — never your name, email address or message.
You can block analytics with Google's browser opt-out add-on, or by blocking cookies for this site in your browser. Nothing on this site depends on analytics working.
Because analytics storage is already denied by default for visitors we resolve to California, a Global Privacy Control signal makes no additional difference to what is stored on your device — which in that case is nothing. Two caveats, for consistency with the section above: this site does not currently read the Global Privacy Control signal itself, so the protection comes from the regional default rather than from your signal being honoured; and if your location is resolved incorrectly, the default outside those regions applies instead. Blocking cookies for this site is the control that does not depend on either.
This section describes the analytics configuration as it is actually deployed. If advertising features, Google Signals, a tag manager, or any additional measurement tool is ever enabled, this section and the California section below must be updated before that change goes live.
Where the UK or EU GDPR applies, we rely on the following legal bases:
We do not use your information for automated decision-making that produces legal effects for you, and we do not use it to profile you for advertising.
We will not add you to a marketing list on the strength of a demo request alone. «CONFIRM: if any marketing email is sent, describe it here and state the consent or opt-out basis relied on»
We do not sell your personal data. We share it only with service providers who process it on our instructions, and only as far as they need to:
| Provider | What it does | Where |
|---|---|---|
| Amazon Web Services | Website hosting and content delivery, server access logs, and the function that receives and forwards demo requests | United States |
| Amazon Web Services | Email delivery of demo request notifications to our team | United States |
| «SMS PROVIDER, if enabled» | Optional text notification to our team when a demo request arrives | «REGION» |
| «CRM / EMAIL TOOL, if used» | Storing and managing business contacts and correspondence | «REGION» |
| Google Analytics | Website analytics. Advertising features and Google Signals are disabled; analytics storage is denied by default in the EEA, UK, Switzerland and California. Google acts as our processor under the Google Ads Data Processing Terms, accepted 18 September 2025. | United States / Global |
We may also disclose personal data where we are legally required to, or to establish, exercise, or defend legal claims. If our business is sold or reorganised, information may transfer to the acquiring entity, subject to this policy.
The list above must be complete and accurate at publication. An incomplete processor list is one of the most common findings in a data protection audit. Confirm whether the optional SMS notification is enabled, and whether any CRM or email tool now receives form submissions.
We are based in the United States and our infrastructure runs in the United States. If you contact us from outside the United States, your information will be transferred there.
Where personal data is transferred out of the UK or EEA, we rely on the European Commission's Standard Contractual Clauses and the UK International Data Transfer Addendum, together with supplementary measures where appropriate. You can request a copy of the relevant transfer mechanism at contact@gogoctv.com.
This is only accurate if the clauses have actually been executed with the relevant providers, and if a transfer impact assessment exists. Counsel should verify before this paragraph is published. Also confirm whether reliance on the EU–US Data Privacy Framework is preferable for any provider that participates in it.
Where we are required to keep information for longer by law, we keep it for that period and no longer.
Retention periods must be real and enforced by an actual process, not aspirational. Publishing a period nobody deletes against is worse than publishing none. Confirm the current log retention setting at the CDN and storage layer before filling these in.
All traffic to this website is encrypted in transit using TLS. Demo request submissions are sent over an encrypted connection to a serverless endpoint hosted on Amazon Web Services, which forwards them by email to a monitored company mailbox. Submissions are not stored on the website itself, and access to systems holding enquiry data is limited to personnel who need it.
Our security page describes our practices in more detail. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
Depending on where you live, you may have the right to:
To exercise any of these, email contact@gogoctv.com. We will respond within one month, and will tell you if we need longer. We may ask you to verify your identity before we act, and we will not charge you or treat you differently for making a request.
If you are a California resident, the CCPA as amended by the CPRA gives you the right to know what personal information we collect and why, to access and delete it, to correct inaccuracies, and not to be discriminated against for exercising those rights.
In the twelve months before the effective date of this policy, we collected the categories of personal information described in section 3 — identifiers, professional or employment-related information, and the contents of messages you send us — directly from you or automatically from your device, for the purposes in section 5, and disclosed them to the service providers in section 6.
We do not sell personal information, and we do not share it for cross-context behavioural advertising. Our analytics is configured with advertising storage, advertising personalisation and Google Signals disabled, and with analytics storage denied by default for California residents — so no personal information is disclosed for advertising purposes. We have not sold or shared personal information in the preceding twelve months, and we do not knowingly collect or sell the personal information of anyone under 16. Because we do not sell or share, we do not offer a "Do Not Sell or Share My Personal Information" link.
You may use an authorised agent to make a request on your behalf; we will ask for proof of their authority.
The statement that no personal information is sold or shared must remain true, and it depends on the analytics configuration staying as described. Enabling Google Signals or advertising personalisation would likely constitute "sharing" under the CPRA even with no money changing hands, and would require an opt-out link. Counsel should also confirm whether any other US state privacy law now applies and requires additional disclosures.
This website is aimed at businesses and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has sent us personal data, contact us and we will delete it.
We may update this policy as our practices or the law change. The effective date at the top of this page shows when the current version took effect. Where a change materially affects your rights, we will take reasonable steps to tell you.
See also our Terms of Service and Security page.