Privacy Policy

1. Who we are

ChannelzIQ is a software-as-a-service platform for YouTube content creators, operated by ChannelzIQ LLC ("we," "our," or "us"), a limited liability company based in the suburbs of Chicago, Illinois, USA. Our website is https://channelziq.com and our customer application is https://go.channelziq.com. This Privacy Policy explains what information we collect, how we use it, and the rights you have over your data.

2. Information we collect

2.1 Account information

When you create a ChannelzIQ account, we collect your name, email address, and a hashed password (or, if you use Google Sign-In, the Google account identifier and email address Google returns to us). We collect billing details (last four digits of your payment card, billing zip code, and Stripe customer identifier) when you subscribe to a paid plan; we do NOT store your full credit card number — Stripe handles that.

2.2 Connected Google service data

ChannelzIQ uses YouTube API Services. For information about how Google handles personal information, please see the Google Privacy Policy.

ChannelzIQ requests permission to access several Google services through OAuth. You grant each permission explicitly during connection, and you can revoke them at any time in your Google Account settings at https://myaccount.google.com/permissions. The specific scopes we request and what we do with each:

• YouTube Data API (youtube.readonly, youtube.force-ssl): Read your channel profile, video metadata, titles, descriptions, tags, thumbnails, playlists, comments, and subscriber information. The "force-ssl" permission also allows us to post comment replies and update video titles/descriptions on your behalf, but only when you explicitly trigger an action in our interface — we never modify your channel automatically.
• YouTube Analytics API (yt-analytics.readonly): Read non-monetary analytics — views, watch time, audience retention, traffic sources, demographics, device types, and similar performance metrics — for your own channels only.
• Google Search Console API (webmasters.readonly): Read search query data, page performance, and click-through rates for websites you own and have verified in Google Search Console. We use this to surface keyword opportunities and search-visibility signals for content planning.
• Google Analytics API (analytics.readonly): Read pageview, audience, and acquisition data from any Google Analytics 4 properties you grant us access to. We use this to correlate YouTube performance with web traffic for creators who run a companion website or blog. For more on how Google itself handles this data when our service queries it on your behalf, see Google's How Google uses information from sites or apps that use our services.
• Sign-in scopes (openid, userinfo.email, userinfo.profile): Used to authenticate you and display your name and email in our application.

Note (updated May 2026): the Google AdSense Management API integration was removed from ChannelzIQ. We no longer request the adsense.readonly scope and we no longer store any AdSense data. Customers who previously granted that scope are unaffected — the scope remains on their old OAuth grant until they reconnect, and our code does not read it.

Limited Use of Google user data. ChannelzIQ's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer Google user data to third parties except as necessary to provide or improve user-facing features that are prominent in the requesting application's user interface, and only with explicit user consent. We do not use Google user data for serving advertisements, including retargeting, personalized, or interest-based advertising. We do not allow humans to read Google user data unless we have the affected user's explicit consent for specific messages, doing so is necessary for security purposes (such as investigating abuse), to comply with applicable law, or for ChannelzIQ's internal operations and only when the data has been aggregated and anonymized.

2.3 Connected non-Google services

If you choose to connect a WordPress blog, Facebook page, Instagram business account, or TikTok account, we collect the access tokens and account identifiers necessary to read your published content and (where you authorize it) publish on your behalf. As with Google services, you can revoke these connections at any time.

2.4 Content you create within ChannelzIQ

Drafts, scripts, video titles, blog post outlines, social media captions, research queries, and any other content you generate or edit inside ChannelzIQ are stored in our database and associated with your account. AI-generated suggestions are also stored so you can revisit and reuse them.

2.5 Usage and diagnostic data

We collect application logs (IP address, browser type, pages visited, actions taken, timestamps, error messages) to operate, secure, and improve the service. These logs are retained for 30 days unless required longer for security investigation.

2.6 Cookies and similar technologies

We use first-party cookies for authentication (the cookie cz_user_token keeps you signed in for 24 hours, HttpOnly and Secure flags set). We use Google Analytics 4 on our public marketing pages to understand which pages people read. That is a third-party analytics cookie (_ga), and our cookie notice has always named it as such — this section previously said "minimal first-party analytics", which was wrong, and the two documents contradicted each other. Analytics storage is denied until you accept it in the banner: no _ga cookie is written before then, and if you press Decline we remove any that is already there. We do NOT use advertising cookies, retargeting pixels, or social-media tracking pixels anywhere.

2.7 People who interact with your channels

When you connect a platform we import the public comments and direct messages sent to your accounts — the names, handles, avatars and text of people who wrote them, who have no ChannelzIQ account. We hold this so you can read and reply from one inbox and so AI features you trigger can summarise it. We never contact them; it is deleted with your account.

2.8 Waitlist and contact submissions, and how you found us

We keep your name, email, message and the page you sent it from, so we can reply and, if you asked, send product updates.

When you join the waitlist or create an account, we also keep a note of how you found us, sent by your browser with that form: the campaign tags and page of your first visit to channelziq.com, the last tagged link you came through, the outside site that referred you, when you first visited, how many times you had visited, which of our public pages you had looked at (page addresses only) and how many messages you had sent to the assistant on channelziq.com. We use it to understand which marketing brings people who sign up and which pages help them decide; it is shown to our staff with your account, is never sold or shared, and is deleted with your account. If you accepted Google Analytics on our banner, we also keep the random visitor number from its cookie with your account and report your signup to Google Analytics as a sign_up event (no name or email is sent), so that the same marketing figures line up in both places. If your last answer on the banner was Decline, we do neither. Our cookie notice names the notes your browser keeps.

2.9 Chatbot transcripts

The assistant on channelziq.com records each message you send, the reply, your IP address, the page you sent it from, and — from the note your browser keeps (Section 2.8) — which visit to our site it was and how many of our pages you had looked at, so we can see what people ask after reading what. Cue, the assistant inside ChannelzIQ, records each message you send and the reply, linked to your account, but not your IP address; we also count how often you use it (free help questions and analyses) so you and we can see usage. Transcripts are deleted after 30 days.

2.10 Email open tracking

Marketing emails contain a one-pixel image; when it loads we record the time, your IP address and browser type against that email. Transactional emails (sign-in codes, receipts) carry no pixel. Open records are deleted after 365 days.

2.11 AI assistants you connect (Claude, ChatGPT and other MCP clients)

You can connect your own AI assistant — for example Claude or ChatGPT — to ChannelzIQ through our hosted Model Context Protocol (MCP) server at https://mcp.channelziq.com/mcp. Nothing is connected unless you set it up in that assistant and press Allow access on our approval screen. To make the connection work we keep: a hashed copy of the access key the assistant uses (never the key itself) and its first characters so you can recognise it, a hashed refresh token that lasts up to 90 days, when the key was last used, and a record of each step of connecting (registered, signed in, approved or denied) together with which kind of assistant it was and your account ID. That record holds no email address, IP address or browser details. Requests the assistant makes after you connect it appear in our security records like any other request, with the key or connection that made them and the address they came from, which is usually the assistant company's server and not yours. We also count, for each connection and each hour, which ChannelzIQ tools the assistant used and how many times (for example “get_video, 4 times”), so our support staff can see how a connection is being used. That count holds the tool's name only, never what you asked the assistant or what it was sent back, and is kept for 365 days. All of this is deleted with your account. Separately, the assistant registers itself with us (its app name and callback address); that registration contains nothing about you.

Once connected, the assistant can read the ChannelzIQ data your plan allows and act on your instructions (for example save a draft, schedule or publish a post, or reply to a comment). Whatever the assistant reads from ChannelzIQ is sent to the company that runs that assistant, under your own account and agreement with them, not ours — see Section 4. You can disconnect at any time in ChannelzIQ under Settings → Connected Accounts → Claude (MCP), which lists every connected assistant, and by removing ChannelzIQ from the assistant itself.

2.12 Voice features (dictation and the teleprompter's Follow my voice)

Some features in ChannelzIQ can use your microphone, and only after you press their microphone button and allow it in your browser: dictating into a text box, and the teleprompter's Follow my voice, which keeps the line you are reading at the top of the screen. Both use your web browser's own speech recognition. Your browser sends what you say to its maker's speech service to turn it into text — Google's in Chrome, Microsoft's in Edge, Apple's in Safari — under your agreement with that company, not ours. ChannelzIQ never receives, records or keeps your voice. Dictated text becomes part of the box you dictated into and is handled like anything else you type there. The words the teleprompter hears stay in your browser and are discarded when you close the teleprompter; ChannelzIQ records only that the feature was turned on or used, never what was said. The microphone stops when you pause, close the teleprompter or stop dictating.

2.13 The ChannelzIQ Chrome extension

If you install the ChannelzIQ extension for Google Chrome and connect it to your ChannelzIQ account, it shows your ChannelzIQ information, and actions on your content, in Chrome’s side panel beside the page you are viewing. Before you press Connect, the panel and the ChannelzIQ page you confirm on both say what is described here. Until you connect, the extension reads and sends nothing about the pages you visit.

What it reads. The address and title of the active tab in the window the panel is open in, and when that tab changes. It does not read the text, forms, images or media of any page, does not run scripts on pages, and does not use Chrome’s browsing-history or cookies features.

What it sends to ChannelzIQ. When the tab shows a YouTube, Facebook, Instagram or TikTok video, post, channel or account — including another creator’s — the extension sends the platform and the identifier from the address (for example a video ID or an @handle) to ChannelzIQ, which looks it up among your connected accounts; for a YouTube item ChannelzIQ has not stored, ChannelzIQ may ask YouTube’s public data who published it. When the tab shows a page on a WordPress site you have connected, it sends that page’s address, cleaned first in your browser: no tracking tags or other query, nothing after a #, only WordPress’s own ?p= post number when the address uses one, and never an address that carries a user name or password. The address of any other website is compared with your connected sites inside your browser and is not sent. Anything else is sent only when you press something in the panel: an idea and the notes you write (and, if you keep it, the cleaned link to the video), adding a channel as a peer, linking an item to a project, a sync or refresh, a comparison with another creator’s public YouTube figures, an image you choose and confirm as a new Facebook or YouTube thumbnail, or an AI action, which shows its Cue-token estimate before you press Run. Nothing in the panel spends Cue tokens or changes anything on a platform by itself.

What Chrome keeps on your computer. In the extension’s own storage in Chrome: the panel’s sign-in credential (a random key, stored as Chrome stores extension data; ChannelzIQ adds no encryption of its own to it), the workspace you chose, small preferences (such as the last tab you used and the “Compare automatically” switch), which disclosure you accepted, and up to five recently viewed items per workspace — each with its cleaned address, its title, the platform and when you viewed it. This is kept separately for each ChannelzIQ account. Signing out of the panel removes that account’s data from Chrome; uninstalling the extension removes all of it. When ChannelzIQ ends the panel’s sign-in (it expired, was revoked, or you signed out of ChannelzIQ), the panel removes its stored sign-in but keeps that account’s workspace, preferences and recently viewed list in Chrome until you connect that account again and sign out of the panel, or uninstall the extension.

Its sign-in. The panel has its own sign-in, separate from your ChannelzIQ browser session. It lasts up to 30 days. We store only a hash of its credential, with when it was connected and last used; these records are kept with your account and deleted with it. Signing out of the panel asks ChannelzIQ to revoke the credential and clears the panel’s data in Chrome; if ChannelzIQ cannot be reached at that moment, the panel says so, its data in Chrome is still cleared, and the credential stays valid until it expires or you sign out of ChannelzIQ. Signing out of ChannelzIQ, or an administrator ending your sessions, also ends the panel’s access.

Who receives it. The extension talks to one server, ChannelzIQ’s API at go.channelziq.com. To show YouTube thumbnails, your browser loads public images from Google’s i.ytimg.com; those requests carry no referrer, but Google receives the video’s ID and your IP address. When you press an action, ChannelzIQ may use the service providers in Section 4 that the action needs — for example YouTube or Search Console data from Google, Meta for a Facebook or Instagram refresh or thumbnail, TikTok for a TikTok refresh, and Anthropic for an AI action — not every provider for every action. Like every request to ChannelzIQ, extension requests appear in our ordinary security and application logs, kept as Section 5 says. The extension adds no advertising or analytics service.

What you save stays ordinary ChannelzIQ data. Ideas, notes, drafts, project links, peers and thumbnails you save or apply through the panel are handled, kept and deleted like the same things saved in the ChannelzIQ studio (Sections 3–5 and 7). A public YouTube comparison is remembered for up to a day.

Limited use. We use the information the extension handles only to provide the panel’s features: showing your ChannelzIQ information for the page you are on and carrying out the actions you request; and, as Section 2.14 describes, to protect your account and our service from attacks and abuse. We do not sell it; we do not use or transfer it for advertising, including personalised or interest-based advertising, or to determine creditworthiness or for lending; and we do not transfer it to anyone except as needed to provide those features, to comply with the law, to protect against security threats or abuse, or as part of a merger, acquisition or sale of assets. People at ChannelzIQ do not read it except with your agreement for a specific request (such as a support question), when needed for security (such as investigating abuse), to comply with the law, or in aggregated, anonymised form for internal operations. Our use of information received through the extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. This is separate from, and does not replace, our commitments for data from Google’s APIs in Section 2.2.

2.14 Security monitoring, risk scores and account links

From October 31, 2026, we use security records to look for signs that an account is being attacked or misused. These records include sign-in attempts, the address and approximate location a request came from, how you signed in, which key or connection made a request, and requests we refused. Only records from that date onward are used for what this section describes.

Risk score. Our system gives each account a score from 0 to 100. The score tells us which accounts to look at first. It is a review priority. It is not a judgment about you and not a finding that you did anything wrong. An account without enough information is marked "not scored". The score comes from behavior such as repeated failed sign-ins, attempts to reach another customer's data, probing for pages that are off limits, repeated use of an invalid key, unusual sign-in addresses, unusual patterns of use through our API, and AI use that keeps going after a limit has refused it. A score alone does not restrict an account. We do not use it for marketing, pricing or deciding which features you get.

What does not raise your score on its own. Your country, using a free email provider, using a VPN, having low activity, or not subscribing. Errors on our side do not count, nor does trying a feature your plan does not include, nor does content other people post that we import from your connected platforms.

Automatic protective actions. Specific rules can act before a person has looked:

• Cooldown. One key, one session or one feature on your account (for example AI features) stops working for a short time, usually 30 minutes, and then starts again by itself. A person can end it early or extend it. Repeated cooldowns go to a person to review.
• Pause. Nobody in your organization can sign in until a person has reviewed it. Connected assistants and the Chrome extension stop too. A person applying a pause by hand may limit it to one team member. Your data is not deleted by a pause.
• Address restriction. Requests from one internet address are refused. By hand, we can also restrict a range of addresses or a whole country. An address rule can affect anyone using that address, including people without an account, and it lasts until we remove it or until the end date we set.

Securing your account. If we have reason to think someone else has your sign-in, for example because Google tells us your Google account was compromised or a replaced sign-in token is used again, we end your sessions, ask you to sign in again and email you. We do not pause your account for this.

A person reviews every pause. Only the owner of ChannelzIQ can lift one, and there is no fixed time for that, so a pause lasts until the review is finished. We do not email you when a pause starts. When you try to sign in you will see that your account is paused and a form for messaging support. We do not show the score or the evidence during a review, because that could help someone attacking the account. If you think a pause is a mistake, tell us through that form or at support@channelziq.com, and a person will read it.

Account links. To spot one person or group misusing several accounts, we compare the addresses used to sign in and sign up, and show our administrators the accounts that share one. We may also check a new account against the one-way fingerprint we keep for evaluations (Section 5), which can confirm a match but cannot list accounts. Homes, offices and mobile networks often share an address, so a link is a reason to look. A link alone never raises a score or restricts an account. We do not tell one customer about another.

Who can see this. Addresses, approximate locations, scores, links and incident records appear in our administrator console. Only administrators with the highest level of access can see them.

3. How we use your information

We use the information described above to:

• Provide the core ChannelzIQ service — display your YouTube analytics, generate AI-assisted content recommendations, surface keyword and competitive research, and let you publish or schedule content across your connected platforms.
• Process subscription payments through Stripe.
• Communicate with you about your account, send service updates, and provide customer support.
• Detect and prevent fraud, abuse, and security incidents, including the risk scores, automatic protective actions and account links described in Section 2.14.
• Comply with legal obligations.
• Improve the product — for example, identifying which features creators use most so we can prioritize roadmap work. This analysis uses aggregated, de-identified data wherever possible.

We do not sell your data to third parties. We do not share data from your connected services with advertisers, data brokers, or any external party other than the limited operational vendors listed below.

4. Who we share data with

We share information only with the limited set of vendors that operate ChannelzIQ on our behalf:

• Anthropic, PBC (AI sub-processor) — When you click a "Generate", "Refresh", "Analyze", or similar AI button inside ChannelzIQ, the relevant content from your account is sent to Anthropic's Claude API for processing and the response is returned to you. Examples of data sent in context with each AI feature: video titles and descriptions, video thumbnail images, audience comments and your past replies to them, transcripts you have stored, blog article text, brand-voice samples you have configured, Google Analytics page paths and session counts, YouTube traffic-source labels, keyword lists, and the prompt instructions that frame the request. Anthropic's Commercial Terms contractually prohibit them from training their models on content sent through the API. ChannelzIQ does not pool content across customers to train, fine-tune, or otherwise improve any AI model — every AI request is scoped to the requesting customer's own account. See Anthropic's privacy policy at anthropic.com/legal/privacy.
• Stripe, Inc. — Payment processing. Stripe receives the data necessary to charge your card and manage your subscription. See Stripe's privacy policy at https://stripe.com/privacy.
• Hostinger / our hosting infrastructure provider — Server hosting in a US data center. Our hosting provider has access to encrypted data at rest but does not access application content.
• Google LLC — Our service uses Google APIs (the ones described in Section 2.2). Data flows between ChannelzIQ and Google's APIs are governed by Google's own privacy and security practices. If you use Google to sign in or connect, Google can also send us a security alert about that Google account, for example that it was compromised or its sessions were revoked. We use the alert to end your ChannelzIQ sessions and ask you to reconnect, and we keep it for 365 days.
• Cloudflare, Inc. — Bot protection on our public forms (waitlist sign-up, creating an account with an email code, contact, feedback, roadmap votes, status-page subscribe and developer access). When you submit one of those forms, Cloudflare’s Turnstile check runs in your browser at challenges.cloudflare.com and our server sends the resulting one-time token, plus your IP address, to Cloudflare to confirm you are not an automated script. Turnstile is designed not to profile you or track you across sites, and it receives none of the information you typed into the form. See Cloudflare’s privacy policy.
• Twilio Inc. — SMS delivery for one-time sign-in codes, where you have chosen SMS. Twilio receives your phone number and the message body. See Twilio's privacy notice.
• Meta Platforms, Inc. (Instagram Business Discovery) — Instagram peers in Peer Insights. When you add or refresh an Instagram peer, we ask Meta's Instagram API for that account's public profile and recent posts (followers, number of posts, and each post's likes and comments). Only public Business and Creator accounts can be read. The request is made through the Instagram professional account you connected, so Meta receives the username you entered and can see that your account looked it up. YouTube peers are read from YouTube's public API (Google, above). See Meta's privacy policy.
• Apify Technologies s.r.o. — An integration for collecting comments on TikTok videos exists but is switched off and has no credentials, so nothing is sent to Apify today. Peer data no longer goes through Apify. It is listed here because the code is one administrative change away from live. See Apify's privacy policy.
• MaxMind, Inc. — Approximate geolocation of IP addresses we record: on each sign-in, so an unfamiliar-location alert can say "a sign-in from Berlin" rather than an IP number; on each sign-up and waitlist join, so our internal alert can name the city and country; and in the security records described in Section 2.14. The lookup runs against a database we download and hold ourselves; your IP is not sent to MaxMind. See MaxMind's privacy policy.
• LinkedIn (Microsoft Corporation) — Only if you connect a LinkedIn account. Receives the OAuth token you granted, plus the content you publish and the comments we fetch back. See LinkedIn's privacy policy.
• Bluesky Social, PBC — Only if you connect a Bluesky account. Receives your app password or OAuth grant, the posts you publish and the replies we read back. Resolving a Bluesky handle also queries plc.directory, the AT Protocol's public identity directory, which receives the handle being resolved. See Bluesky's privacy policy.
• Threads (Meta Platforms, Inc.) — Only if you connect a Threads account. Receives the OAuth token and the content you publish. Covered by Meta's privacy policy, linked above.
• Reddit, Inc. — A Reddit publishing adapter exists in the product but the platform is currently switched off and cannot be connected: Reddit's terms require a signed commercial agreement before a paid product may use their API, and we do not have one. It is listed here because the code is one administrative toggle away from live, and we would rather disclose it early than quietly. If it is ever enabled it will receive the OAuth token you grant and the content you publish.
• Have I Been Pwned (Superlative Enterprises Pty Ltd, api.pwnedpasswords.com) — When you set or reset a password, we check whether that exact password already appears in public breach data. We do this with k-anonymity: your password is hashed on our server and only the first five characters of that hash are sent. The service returns every hash sharing those five characters and the comparison happens here. Your password, the full hash, your email and your IP address never reach them, and no account identifier is included. If the service is unreachable we let the password through rather than block you. See their privacy policy.
• Brave Software, Inc. (Brave Search API) — Powers the news and topical-research lookups. Brave receives the search query, which is derived from your topic or keyword. It receives no account identifier. See Brave's privacy policy.
• Slack Technologies, LLC (hooks.slack.com) and Discord Inc. (discord.com / discordapp.com webhooks) — Only if you save a Slack or Discord webhook address. The alerts or weekly summary you chose are posted to that channel, and can include video titles and your own totals. We keep the address and a 90-day record of each delivery attempt. See Slack's privacy policy and Discord's privacy policy.
• Our email delivery provider (SMTP / SendGrid) — Sends sign-in codes, alerts and transactional email. Receives your email address and the message content. Nothing else about your account is included.
• Google Fonts and the Tailwind CSS CDN — Our pages load fonts and, on some pages, a stylesheet from these third parties. Because a browser must request them, your IP address reaches Google and the CDN when a page loads, before you have interacted with anything. This happens on the public site whether or not you have an account. We list it here because it is a real disclosure, not because we like it.

AI assistants you choose to connect (Section 2.11) are not our vendors. When you connect Claude (Anthropic, PBC), ChatGPT (OpenAI, L.L.C. / OpenAI OpCo, LLC) or another MCP-capable assistant, the ChannelzIQ data that assistant reads at your request — for example video titles, analytics, comments, scripts and calendar entries — goes to that company under your own account with them, and how they keep and use it (including whether it may be used to train their models) is set by their terms, their privacy policy and your settings there, not by ChannelzIQ. See Anthropic’s privacy policy and OpenAI’s privacy policy. This is separate from the ChannelzIQ AI features described above, which run on Anthropic’s API under our commercial terms.

We may also disclose information if required by a valid legal request (subpoena, court order, law enforcement request) but we will resist requests we believe are overbroad and notify the affected user where legally permitted. We may also share incident records (Section 5), limited to what is needed, with our payment processor to answer a chargeback or payment dispute, with our legal advisers, and with law enforcement when we believe a deliberate attack took place.

4.1 Third-party data sources used for enrichment

The following third-party services are used to translate and enrich data we already have on file. We do NOT pass your account identity or personal information to any of them — only generic terms (such as place names) are submitted.

Geocoding & Location Data (Nominatim / OpenStreetMap)

ChannelzIQ uses the Nominatim geocoding service to translate audience location data (city / region / country) returned by your connected platforms (YouTube Analytics, Meta Insights) into a standardized format for display and analytics. Map data and geocoding results are provided by OpenStreetMap contributors under the Open Database License (ODbL). We cache geocoding results locally for up to 90 days to reduce Nominatim API load and honor their usage policy. We do not share your audience location data with Nominatim — only generic place names are submitted for translation.

5. Data retention

We retain account information and content you create for as long as your account is active. If you delete your account, your access ends immediately and your data is held for a 30-day grace period, during which you can ask support to stop the deletion; at the end of it your account data is permanently erased. These survive that erasure: billing and referral-payment records we are required to keep for accounting and tax purposes (typically 7 years); one audit entry recording that the account was erased and when (kept 7 years, with no content); encrypted backups until they age out; security records, as described below; and records that keep a past choice or limit working, namely your address on our do-not-email list, the one-way fingerprint that stops the same person starting a second evaluation, and the history of changes to the account's access (with no content). Messages you sent through our contact form, roadmap votes and status-page subscriptions are not tied to your account. Ask us and we will delete them. Backups on our server are kept for 7 days and the off-site copy for 30 days, so a copy of your data can exist for up to about 60 days after you ask us to delete it. If we ever have to restore a backup, we erase again every account whose deletion had already been requested.

Incident records. When our rules or our team open a security incident, we keep a record of it and the evidence behind it: the times and actions involved, whether they were allowed, the addresses and approximate locations, the account, organization and key concerned, the score when the incident opened, the rule that fired, what we did, and the review. It never includes passwords, sign-in codes, tokens, what you write in ChannelzIQ, or data imported from your connected platforms.

We keep incident records indefinitely, including after the incident closes and after the account is deleted. When an incident closes as a false alarm or a fault on our side, we delete its evidence and keep only a note that it happened and how it closed. We do this so that deleting an account cannot erase the trail of an attack, so that we can recognise a repeat attack, and so that we can answer disputes and legal claims. When an account is erased we remove its name and email address from these records. What is left, such as an address, a time and an internal account number, can still relate to a person, so we do not call it anonymous. We will not delete incident records on request unless the law requires it.

Cached data from connected services (e.g., YouTube video metadata, keyword research results) is refreshed regularly and replaced. Analytics we import from your connected services — including history back to when a channel started, where the platform provides it — are kept for as long as your account is active, so trends and comparisons can cover your whole history.

YouTube data (specific commitment). Under Google's YouTube API Services Developer Policies, a daily job deletes any YouTube comment or video details we have not been able to refresh from YouTube in the last 30 days, and closes a YouTube connection that has not synced in 30 days. This still applies while an account is paused, so after a pause of more than 30 days you may need to reconnect YouTube. While your connection stays authorized, our regular sync re-reads your channel and re-pulls recent analytics days; analytics history from earlier days is kept with your account, as described above.

If you disconnect a Google account from ChannelzIQ, we revoke the OAuth token at Google immediately, and the comments and video details we stored through it are deleted once 30 days pass without a refresh. Analytics history imported through it stays with your account until you delete the account or ask us to remove it. If you ask us to delete a specific piece of YouTube-derived data, we will do so within 7 days of your request (see Section 7).

Server log files are deleted after 30 days. Database records follow fixed windows, purged daily: chatbot transcripts and error reports 30 days; sign-in attempts 90 days; sign-in codes 7 days; email opens 365 days; feature-usage events 400 days; internal operational logs (sync, pull, backfill and delivery records) 90 days; email delivery records, security events and counts of the tools a connected AI assistant used 365 days, and security events stay for the rest of that window after an account is deleted; risk scores, the current score and 90 days of history, deleted with your account; address restrictions until we remove them or until their end date; incident records indefinitely, as described above; administrative audit entries 90 days, except the record that an account was anonymised, kept for 7 years, and entries about a security incident, kept with the incident.

6. How we protect your data

• All data in transit is encrypted using TLS 1.2 or higher.
• Sensitive credentials (OAuth refresh tokens, API keys, payment processor tokens) are encrypted at rest in our database.
• Access to production systems is limited to the ChannelzIQ founding team and requires SSH key authentication. There are no offshore contractors or third-party developers with access to production data.
• We log all access to production systems and review the logs regularly.
• Nightly backups are encrypted with a key held outside the server and copied to a separate location.

No security measure is perfect. If we detect a security incident affecting your data, we will notify you and the appropriate authorities as required by applicable law.

7. Your rights

Regardless of where you live, you have the following rights with respect to your ChannelzIQ data:

• Access and portability — export your content and account records yourself, from Settings → Data & Privacy → Export All My Data. It downloads as a ZIP of spreadsheets, one per kind of record. You do not need to ask us. The export does not include risk scores, security events, account links or incident records. To ask what security information we hold about you, email support@channelziq.com. We may hold back details during a review, or where they would reveal how we detect attacks or concern another person. If your account is paused and you cannot sign in, ask support and we will send you your export, once we are satisfied the request comes from the account holder.
• Correction — edit it directly: Settings → Profile for your name and email, Settings → Organization for your organization’s details, and Settings → Connected Accounts to reconnect or replace a linked service.
• Deletion — Settings → Data & Privacy → Delete my account. After a 30-day grace period during which you can change your mind, your content is destroyed across every table that holds it, and the records that must survive for billing and tax are stripped of anything identifying you. Section 5 lists what survives, including security records. If you cannot sign in, email support@channelziq.com and we will do this for you once we have confirmed the request comes from you. If your account is paused, deletion starts when the review ends, or 30 days after your request, whichever comes first.
• A person's review of a pause — a person reviews every automatic pause (Section 2.14). You can tell us why you think it is wrong through the form on the sign-in page or at support@channelziq.com.
• Do not sell or share — we do not sell personal information and do not share it for cross-context behavioural advertising. Settings → Data & Privacy has a switch that records your opt-out; it takes effect immediately and you can turn it off at any time. If your browser sends the Global Privacy Control signal we switch it on for you. More about this right.
• Withdraw consent — disconnect any connected Google or third-party service at any time from within ChannelzIQ Settings, or revoke our access directly from your Google Account at https://myaccount.google.com/permissions.

To exercise any of these rights, email support@channelziq.com. We will respond within 30 days.

8. Children's privacy

ChannelzIQ is not directed at children under 13 and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, please contact support@channelziq.com and we will delete it.

9. International users

ChannelzIQ is operated from the United States and our servers are located in the United States. If you access ChannelzIQ from outside the US, you understand that your data will be transferred to and stored in the US, which may have different data-protection laws than your jurisdiction.

ChannelzIQ is not currently optimized for compliance with the European General Data Protection Regulation (GDPR) or the UK Data Protection Act. We are keeping that sentence because it is true, and we would rather say so than imply otherwise. What it does not mean is that the underlying rights are unavailable: access, portability, correction, deletion and opt-out are all self-serve controls in the product, described above, and deletion erases your content across every table that holds it rather than merely flagging the account closed. What we have not done is the formal apparatus a GDPR-ready processor is expected to have — a documented lawful-basis register, data-processing agreements with every sub-processor listed in section 4, and a named data protection officer. (We do keep a written incident and breach-response procedure.) We are focused on serving creators based in the United States and Canada at this stage. If you reside in the EU, UK, or another jurisdiction with comprehensive data-protection law, please note that not all features described in this policy may be enforceable in your local courts, and our processes may not fully meet local requirements.

10. Changes to this policy

We may update this Privacy Policy from time to time as we add new features or change our practices. When we do, we will update the "Last updated" date at the top of this page. If we make a material change — a change to what personal information we collect, how we use it, or who we share it with — we will notify you by email or through a notice in ChannelzIQ a reasonable time before it takes effect. We will not apply a material change to personal information we collected before the change without your consent. Continued use of ChannelzIQ after a change takes effect constitutes acceptance of the updated policy.

11. Contact us

Questions, requests, or concerns about this Privacy Policy or how we handle your data? Reach out:

Email: support@channelziq.com

If you need to send physical mail, request our mailing address by emailing support@channelziq.com with the subject line "Mailing address request" and we will respond within 5 business days.