Docs / Security, privacy and policies
Privacy at a glance
What ChannelForge collects, why, where it is kept, who processes it, and your rights — in short, with links to the full policy.
This is a plain summary of how ChannelForge handles personal information. The binding texts are the Privacy Policy, the Data Processing Addendum for business customers and the sub-processors page; where this page and they differ, they win. ChannelForge is provided by StoresWiki LLC, the controller of the information described here.
In short#
- We collect what we need to run your account and your channels, and what the features you switch on need.
- Secrets — platform tokens, two-factor secrets — are sealed; passwords and keys are stored only as hashes.
- We do not sell personal information, and we do not share it for advertising.
- The service is hosted in the European Union.
- You can see, correct, export and delete your information, and ask us to.
What we collect#
| What | Why |
|---|---|
| Account data — your name, email address, a hash of your password, your two-factor settings, your workspaces and roles, your preferences | to sign you in and run your account |
| Workspace content — briefs, research, channels, brand suites, scripts, episodes, captions, thumbnails, schedules, settings | it is what you make with ChannelForge |
| Connected-platform tokens and data — the tokens of the accounts you connect (sealed), the accounts' names and identifiers, the posts we publish and their performance | to publish what you approve to the accounts you choose, and to report how it did |
| Your accounts' posts and comments, where you use Insights and Studio | to show them to you in one place; a commenter is kept as a keyed hash, never their platform identifier |
| What a feature you switch on needs — the outlier radar's watched accounts, comment themes, the weekly coach, footage you upload, a brand voice, a product's page, profit, a media kit, agency mode | as each feature's own section of the Privacy Policy describes |
| Usage and billing records — your plan, credits and what each job used, invoices, payment status | to bill you; card and PayPal details stay with Stripe and PayPal |
| Logs — addresses, browsers, times, requests, security events, the audit log | to keep the service and your account secure |
| Messages you send us | to answer you |
| Link page clicks — a keyed hash of a visitor's address, kept two days | to count clicks once a day; the page sets no cookies |
Cookies are strictly necessary ones only: see the Cookie Policy.
How it is used, including by models#
Your content is used to provide the service: to research, write, plan, render, check and publish your episodes. Briefs, prompts and workspace content are sent to Anthropic's Claude models, through AWS Bedrock, to research, write, plan and review — and, where you use those features, to group your posts' comments into themes, write the coach's recommendations, find the best moments in your footage's transcripts and read product pages you give us. Narration is spoken by Google Cloud Text-to-Speech, which receives the script's words. Google Cloud Speech-to-Text transcribes footage you upload and checks a brand voice's consent recording; where a channel has clipping's visual check on, Google's Gemini on Vertex AI looks at a few frames of the footage. Scenes are rendered on GPU machines that hold no credentials and keep nothing after the job.
What one workspace's channels learn — lessons from their past episodes, what their own posts' numbers show — improves that workspace's future episodes. It is never given to another workspace, and data from different platform account owners is never combined.
Who we share it with#
- Sub-processors that run parts of the service for us, under contracts that require them to protect it: Amazon Web Services (hosting, database, storage, email, model access), Google Cloud (GPU compute, speech, Gemini), Cloudflare (network), Stripe and PayPal (payments) and Anthropic (Claude, through AWS Bedrock). Locations and details are on the sub-processors page.
- The platforms you connect, when you or your schedule publish to them.
- Members of your workspace, according to their roles — and your agency, if your workspace is one of its clients.
- Whoever has a link you shared, such as a media kit's: what it shows, as you chose it.
- Authorities, where the law requires it, and a successor in a merger or sale, under the same protections.
Where it is kept#
The service is hosted in the EU, in AWS in Frankfurt. Some sub-processors — GPU compute, Google's speech services and Gemini, payment providers, Cloudflare's network — may process information in other countries, including the United States; where the law requires it, safeguards such as the European Commission's Standard Contractual Clauses apply. How it is stored and protected is in Data, storage and retention.
How long it is kept#
| What | Kept |
|---|---|
| Account data | as long as your account exists |
| Workspace content | until you delete it; for a deleted workspace see Deleting a workspace |
| Connected-platform tokens | until you disconnect the platform; within 7 days of a workspace's deletion |
| What we read from the platforms | as each feature says (for example a commenter's displayed name 30 days, the outlier radar's readings 30 days, comment themes 12 weeks, coach briefs 5 weeks); within 7 days of a workspace's deletion, and what was read from YouTube for a channel within 7 days of its disconnection or of Google refusing its access |
| Uploaded footage files | 30 days after the upload |
| Brand-voice recordings | until you withdraw your consent, or the workspace is deleted |
| The free niche finder | your address 2 days, the run 30 days |
| Logs and security events | up to 12 months |
| Messages to us | up to 24 months after our last exchange |
| Billing records | as long as tax and accounting law requires |
Your rights#
Depending on where you live, you can access, correct, delete or export your personal information, restrict or object to how it is used, and withdraw consent; in the EEA and the UK these are your rights under the GDPR, and you may complain to your data protection authority. California residents can know, delete and correct their information and opt out of its sale or sharing — we do neither.
Much of it you can do yourself, in Account & security:
- Download my data — a JSON file with your account, memberships, sessions, notifications, audit trail and the workspaces you own (no secrets, no media);
- correct your name and email address;
- untick Email me occasional product news — account, security and billing emails always arrive;
- Delete account — see what deleting your account does.
In a workspace you can disconnect platform accounts (Settings → Connections), withdraw a brand voice, and an owner can delete the workspace. For anything else, write to support@storeswiki.com, ideally from your account's address. We answer within one month (GDPR) or 45 days (CCPA), and say if we need longer where the law allows it.
Platforms' own rules#
Each platform you connect has its own terms. By connecting YouTube you agree to the YouTube Terms of Service, and ChannelForge's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. To remove ChannelForge's access at a platform itself — not only ChannelForge's copy of the tokens — use the platform's settings; the Privacy Policy lists where for each one. What we do and do not do with each platform's data is in Platform policies we follow.
Children#
ChannelForge is not directed at children under 16, and we do not knowingly collect their information. If you believe a child has given us personal information, contact us and we will delete it.
For businesses and agencies#
Business customers can rely on the Data Processing Addendum. When an agency runs a client's workspace, the agency, for its client, decides what that workspace holds and why, and ChannelForge processes it on the agency's instructions, as its processor or sub-processor; see Agency mode.
Changes and contact#
Changes to the Privacy Policy are posted with a new effective date, and workspace owners are told by email or in the app before material changes take effect. Privacy questions and requests: support@storeswiki.com.
Related#
- Security — how the information is protected.
- Data, storage and retention — what is kept where, and deletion in detail.
- Your account and sign-in — the account settings mentioned above.
Something missing or unclear? Tell us and we will improve this page.