Privacy Policy
ChannelReign runs on your computer. Your scripts, your footage and your finished videos stay there. Our server checks your licence and counts your usage, and — only when you ask for it — writes scripts and AI pictures for you (section 4). This page lists exactly what we hold and where your words go, in the same words the software actually uses.
1. Who we are
ChannelReign ("we", "us") is desktop software for producing video. This policy covers the software you install and the licence server it talks to. Questions about this policy: [email protected].
Phone / WhatsApp: +1 (505) 481-4452
2. What we store on our server
Our licence server keeps one record per licence. That record contains the following and nothing else:
| Group | What is stored | Why |
|---|---|---|
| Purchase | Licence key, plan, the email address used at purchase, purchase reference, subscription reference, status, expiry date, created date | To know that your licence exists, which plan it is on, and to contact you about it |
| Refunds | If your licence is switched off: the date it was switched off and a short reason
code for it (for example refund, dispute, or
subscription_ended:failed_payment) |
So that a refund or chargeback switches your licence off at the right time, so a dispute we win can switch it back on, and so we can answer questions about it later |
| Devices | A one-way fingerprint of each computer you activate on, the computer name Windows reports, the list of registered devices, when a device was last removed, and when the licence was last seen online | To enforce the device limit of your plan, to allow only one free trial per computer, and to show you your own machines in the app |
| Usage counts | Minutes used this month, minutes used today, videos rendered, premium scripts generated, the start of the current billing month and day, per-render settlement records, and our own estimated cost of serving you | To apply your plan's limits and to show you your usage |
These are counts and identifiers. None of them is the content of your work.
The app contacts our server when you activate a licence, about once a day to re-check it, before and after each video it makes, and about once an hour to check for updates and policy changes. Each licence request carries your licence key, the device fingerprint and the computer name. The update and policy checks send only the app's version number.
3. What we do not store
- The text of your topics, scripts, or style instructions. They are never written to our database and never written to our server logs.
- Your videos, images, audio, or project files. These never leave your computer unless you upload them somewhere yourself.
- Your own API keys. They are stored on your computer only (see section 7) and are never sent to us.
- Tracking data. The software and the licence server set no cookies and use no analytics, advertising, or session-tracking services of any kind.
4. Where your text does go
When you press Write the script for me (premium script generation), the topic you type — with the film length and the niche you picked, and, if you set them, a short style instruction and the display name of the niche — is sent through our server to AI service providers that write scripts and make pictures for us (they process the text you send, under contract, and do not train on it). To give the writer facts, our server also looks the topic up on Wikipedia. We pass it through and return the result. We do not keep a copy.
Before we pass it on, an automatic check runs on that text. It is not a person and not a model: it looks only at the shape of what you sent — its length, and a fixed list of patterns that try to redirect the writer with instructions. It runs in memory, keeps no copy of your text, and records nothing about it except a count of how many requests were refused and which rule refused them. A refused request is not sent to the writer: for a documentary film ChannelReign asks you to paste your own script (or try again later), and the one-click video tools use ChannelReign's simpler writer on your own computer.
If you do not want your topic to go to our server or to our AI service providers, paste your own script instead.
When your plan includes AI background illustrations, the sentence of your script for a scene that has no photo — with the names of people removed — is sent through our server to the AI service provider that makes pictures for us (it processes the text you send, under contract, and does not train on it). The same automatic check runs on that sentence first. We pass it through and return the picture; we do not keep a copy of the sentence. If a picture cannot be made, the scene keeps its designed background. The finished picture comes back as a link to that provider's image server, and your computer downloads it from there.
5. Public sources the software searches from your computer
To find facts, pictures, footage and music, the software asks these public sites directly from your computer — no account and no key. Each request carries only the words needed for that search: never your licence key, your computer name or your Windows user name. Like any website, each site sees your computer's internet address, and the software tells them it is ChannelReign. Each site has its own privacy policy.
- Wikipedia and Wikidata — your topic, and names and terms from your script: for script research, Check topic and the pictures of a film.
- Wikimedia Commons, Openverse and the Internet Archive — search words taken from your topic and script, to find archival pictures, footage and music. The files chosen for your film are downloaded to your computer.
- YouTube and Google search suggestions — Check topic searches them for your topic. When a YouTube key is set up in your copy, the same search goes to YouTube's official Data API (googleapis.com) instead. The channel kit checks whether the suggested @handles already exist on youtube.com.
- An online text-to-speech service — only the older One-Click video and dubbing tools, when no other voice is available, send the narration text there. Documentary films use the voice built into ChannelReign, on your computer.
- First-run downloads — the built-in voice model (GitHub) and free music for films (scottbuckley.com.au). Nothing about you is sent.
6. Services you connect with your own keys or accounts
The software can talk to the services below directly from your computer, using keys or accounts you provide. That traffic does not pass through our server, and we never see those keys or that content. Each service has its own privacy policy, which applies to what you send it.
- Pexels, Pixabay — stock footage and images
- Freesound — sound effects
- YouTube / Google — channel research (with your own YouTube key), analytics and uploading through the Google account you connect. Uploads go from your computer straight to Google, and the sign-in stays on your computer.
Google user data (YouTube)
Connecting YouTube is optional. When you press Connect YouTube, you sign in with Google and allow ChannelReign two permissions:
- Manage your YouTube videos and channel (
youtube.force-ssl) — used only when you press Upload or schedule an upload, to upload the film you finished, add its subtitles, set its thumbnail and add it to a playlist; and, when you approve your channel kit, to apply its banner, watermark and playlists to your own channel. It also reads the public comments on a few videos of a channel you chose to study, so the app can show which topics viewers ask for. - View YouTube Analytics reports for your channel
(
yt-analytics.readonly) — used to show you how your own videos perform (views, watch time, average percentage viewed, subscribers gained and audience retention).
ChannelReign never deletes your videos, captions or comments, and never posts comments. All of this data goes directly between your computer and Google. It is never sent to our server, never written to our database, never sold, never used for advertising and never used to train AI models. The Google sign-in token is saved only in the app's settings file on your computer, encrypted with your Windows account (DPAPI). Comments read for topic ideas are kept in a local cache on your computer for up to 7 days and then refreshed or removed.
ChannelReign's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Removing access: press Disconnect in the app's YouTube settings. The app deletes the sign-in from your computer and asks Google to cancel the permission. You can also remove ChannelReign at any time at myaccount.google.com/permissions. To delete everything the app stored from Google, disconnect and then delete the app's data folder on your computer.
7. What stays on your computer
| File | Contents |
|---|---|
config.json |
Your settings and any API keys you entered. Every secret in this file is encrypted with Windows DPAPI and can only be read by your own Windows user account on that machine. |
license.json |
A signed copy of your licence, so the app keeps working during a brief internet outage. |
data/ |
Your projects, channels, brand kits, transcripts and research. |
output/ |
The videos you produce. |
Nothing in this list is uploaded on its own. If you create a backup or a support bundle, the file is written to your own disk and it is your choice whether to send it anywhere. Support bundles deliberately exclude API keys and licence keys, and replace your Windows user name and home folder path with placeholders.
8. How long we keep it
The licence record is kept for as long as your licence exists, and afterwards only as long as we need it for accounting and fraud prevention. Monthly usage counters reset at the start of each billing month.
9. Your rights
You can ask us for a copy of the record we hold for your licence, ask us to correct it, or ask us to delete it. Deleting it ends the licence, because the record is the licence. Write to [email protected] from the email address you used at purchase.
10. Changes to this policy
If we change what we store, we will change this page and update the date at the top.
11. Companies that process data for us
These companies handle data for us, only to run the parts named here. None of them may use it for anything else.
| Company | What it does for us | What it receives |
|---|---|---|
| Anthropic | Writes premium scripts (section 4) | Your topic, film length, niche and style instruction |
| fal.ai | Makes AI background illustrations, when your plan includes them (section 4) | One script sentence per scene, with the names of people removed |
| Gumroad | Takes payment and issues your licence key | Your name, email and payment details (we never see your card) |
| Render | Runs our licence server | The licence record in section 2, and the text in section 4 while it passes through |
| Supabase | Stores the licence record (database) | The licence record in section 2 |
| Cloudflare | Hosts this website and the installer download, and forwards email to our support address | Standard web request data (IP address, browser) and emails you send us |