Privacy and data controls
Policy version: 2026-10-16.1. Last updated: 16 October 2026. Project developer: Steven Patrick Buglione, acting as an individual.
Public source, private installations
Creator Intelligence is distributed as MIT-licensed source code. This GitHub Pages site is documentation, not a hosted analytics service or public MCP endpoint. The maintainer’s own installation remains private. Other operators run independent installations and are responsible for their own policies, credentials, authorizations and data handling. Installing the code does not send your workspace to the maintainer.
Your choices before use
The local application requires an affirmative agreement to the current privacy policy and terms before research, drafting or scheduled collection. MCP sharing is a separate, optional choice, off by default. The owner can change that choice in Settings. Agreement version and time are recorded locally. Agents cannot accept these choices on your behalf.
Data and purpose
The application uses YouTube API Services for public channel/video metadata and statistics, and owner-authorized Analytics and Reporting data. It stores original ideas, scripts, reference links, production blueprints and local exports for research and planning. It does not collect Google passwords, sell API data or provide another creator’s private analytics.
Local storage and retention
Workspace data is stored in the operator’s local PostgreSQL database. OAuth tokens are encrypted at rest; credentials are kept outside source control. Public API metadata and statistics expire after 30 days in this release. Extended public-statistical history and custom-score features remain disabled. Owner reports require continuing authorization and expire within 30 days of retrieval unless refreshed. Expired records are excluded from responses; a scheduled cleanup removes them from storage. Original drafts persist until deletion; managed encrypted draft backups normally expire after seven days and exclude provider caches, analytics and Google tokens.
Sharing with connected tools
After the owner explicitly enables MCP sharing, connecting Claude or another MCP client allows requested records to reach that client and potentially its provider. Local storage does not mean all processing stays on the device. Operators must review the connected provider’s retention and training settings before sharing private reports. The application itself has no model-training workflow. An optional local model performs inference. Blueprint JSON export downloads a local file or returns the requested record to the connected MCP client. There is no external production integration. Google credentials are not included in tool results or blueprints.
Deletion and authorization
Settings provides local export, disconnect and deletion. Disconnect removes this app’s stored connection and owner reports. Delete My Data removes local drafts, cached records and managed draft backups; it does not delete videos from YouTube. Separately downloaded exports and manual backups remain the operator’s responsibility.
Local disconnect does not invoke Google’s project-wide token revocation. Access can be withdrawn using the separately confirmed revocation control or Google Account permissions. Revocation can affect other clients sharing that Google project. Each operator should use a project dedicated to this API client.
Website hosting and cookies
This static website has no analytics scripts, external fonts or application cookies. GitHub Pages hosts it; GitHub logs and stores visitor IP addresses for security purposes. See GitHub Pages data collection and the GitHub Privacy Statement. The local application uses a session cookie for authentication. API requests and thumbnail references reach Google.
Google data and contact
Use of Google user data must comply with the Google API Services User Data Policy, including Limited Use requirements. This application uses YouTube API Services; see the YouTube Terms of Service and Google Privacy Policy.
For project questions or to request a private contact channel, contact the developer on GitHub. Issues are public: do not include private channel data, addresses, credentials or other sensitive details. For a self-hosted installation’s data request, contact that installation’s operator. Report security problems through GitHub private vulnerability reporting.