> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/legal/privacy-policy.md). # Privacy Policy **Effective date: April 17, 2026** TheContentForge ("we," "us," or "our") is a social content operations platform. This Privacy Policy explains what information we collect, how we use it, and your rights with respect to that information. *** ## Information we collect **Account information** When you register or are invited, we collect your email address and the role assigned to your account within your organisation. **Billing information** For paid subscriptions, we collect billing contact details. Payment card processing is handled by our payment processor; we do not store full card numbers on our systems. **Analytics data you upload** Editors and admins may upload CSV exports from X Analytics, Instagram Insights, and Facebook Page Insights. This data is stored per organisation and used to power the Dashboard, Patterns, and Competitor Analysis features. **Generated content** Content generated via Content Forge, ForgeSays, or the Telegram Bot is stored in your organisation's generation history. Retention periods are determined by your plan tier. **Telegram bot interactions** When you use the Telegram Bot, we log the command type, timestamp, and the input provided. We do not store the full message text of messages that do not trigger a command. **OAuth tokens** When you connect a social account via OAuth, we store the resulting access token on your behalf. Tokens are org-scoped and encrypted at rest. Connecting and publishing is currently available for X; Instagram and Facebook are coming soon. **Investor Intel data** If you use Investor Intel, we store the items you choose to track - watchlists, tracked wallets, saved theses and research - and, for the read-only Portfolio Tracker, the public wallet address(es) you sync. We read public on-chain and market data for those addresses; we never request or store private keys and never move funds. Your portfolio data is private to your account and is used only to ground your own AI analysis. **Wallet address and on-chain data** If you link a Solana wallet (for example, to verify FORGE holder access), we store your wallet's public address and timestamps of ownership verification. To determine holder eligibility we read your wallet's FORGE token balance from public Solana RPC/indexer providers and store the observed balance, the Solana slot, and the result. A wallet address is public on-chain data; linking it to your account associates that public address with your identity in our systems. We do not request or store private keys or seed phrases, and we never initiate transactions or move funds. **Bot access and security events** We log Telegram bot access events - allowlist enforcement (blocked chats and users) and successful command execution - to a Security Log. No message content is stored - only the event type, timestamp, and the Telegram chat and user identifiers involved. *** ## How we use your information * **Providing the service** - All data collected is used to operate and improve TheContentForge for you and your organisation. * **Content generation** - Uploaded analytics, brand voice settings, and post history are passed to AI generation providers (xAI/Grok, OpenAI, and Google Gemini) to produce contextual content, image, and video drafts. Inputs are not used to train third-party models. * **Billing and subscription management** - Billing information is used to process payments, send invoices, and manage subscription renewals and changes. * **Security** - Security event logs are used to detect and investigate unauthorised access and misuse. * **Communication** - We may contact you at your registered email address for account-related notices and billing alerts. We do not send marketing email without your consent. *** ## Third-party services | Service | Purpose | | ------------------------------- | ----------------------------------------------------------------------------------------- | | Supabase | Database, authentication, storage, and edge functions | | xAI (Grok) | AI content generation | | OpenAI | AI content, image, and transcript generation | | Google (Gemini) | AI content and image generation | | X, Instagram, Facebook | OAuth for social account connections (publishing is X-only today) | | FluidPay | Card payment processing for subscriptions | | Helio | Crypto (USDC on Solana) payment processing | | MoonPay | Crypto payment processing (legacy, where used) | | Netlify | Frontend hosting | | Helius / QuickNode (Solana RPC) | Reading public on-chain balances for wallet features and FORGE holder-access verification | | Birdeye | Token metadata/price reference (display only) | *** ## Data retention Retention periods for organisation data depend on your subscription plan: | Data type | Starter | Pro | Enterprise | | ----------------------- | --------------------- | --------- | ---------- | | Analytics uploads | 6 months | 12 months | 36 months | | RSS / algorithm sources | 6 months | 12 months | 36 months | | Competitor posts | 90 days | 180 days | 365 days | | Security logs | 12 months (all plans) | - | - | Account and billing data is retained while your account is active. After cancellation or deletion, account data is removed from production systems within 30 days. Billing records may be retained longer as required by applicable law. *** ## Students (draft - pending legal review) > This section covers the Students lane and is a **draft pending review by counsel**. It will be finalised before general release. If you sign up through the Students lane, we collect your name, email, and any self-attested school or campus you provide, along with the version of the Student/NIL terms you accept and your affirmation that you are 18 or older and a current student. **We do not verify school enrolment, and we do not collect or store educational records, academic transcripts, or athletic-eligibility data.** Self-attested school information is not verified. Student drafts, brand voice, and projects stay scoped to your workspace. You can request deletion of your account or removal from the waitlist at any time (see **Your rights**). The tools are intended for people 18 and over; if we learn an account belongs to someone under 18, we will remove it. *** ## Data security All data is stored in Supabase with row-level security enforced per organisation. OAuth tokens and API keys are encrypted at rest. Access to production data is restricted to authorised administrators. *** ## Your rights You may request access to, correction of, or deletion of your personal data at any time. Contact your organisation admin or email ****. We will respond within 30 days. *** ## Changes to this policy We may update this policy from time to time. The effective date at the top will reflect the latest version. Continued use of the platform after changes are posted constitutes acceptance. *** ## Contact **** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://thecontentforge.gitbook.io/thecontentforge-docs/legal/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.