Privacy Policy

1. Introduction

This Privacy Policy explains how the independent ContentFactory software project processes information when a user runs the desktop/local tooling, connects a third-party platform, reviews analytics, or authorizes a controlled publishing operation. It also describes this public website, which contains no account system, contact form, advertising cookies, or embedded marketing analytics.

2. Information processed

Depending on the features the user chooses, ContentFactory may process:

• account identifiers, display names and basic profile information made available through an authorized OAuth scope;
• video identifiers, titles, descriptions, captions, tags, publication status and other video metadata;
• performance information such as views, likes, comments, shares, subscriber changes and available viewing metrics;
• video, audio, image, script, research, thumbnail and metadata files created or supplied by the user;
• local technical state needed to run jobs, quality checks, approvals, audits, retries and analytics mappings; and
• OAuth access and refresh tokens needed to call an authorized platform API.

The exact information available depends on the platform, the scopes approved for the application, and the permissions granted by the user.

3. OAuth and connected accounts

A user chooses whether to connect a platform account. Where supported, ContentFactory uses the platform's official OAuth flow and requests defined scopes for specific features. Read-only analytics permissions are distinct from upload or publishing permissions. A user may revoke ContentFactory's access through the connected platform's account or security settings when that platform provides such controls.

4. Tokens and credentials

OAuth tokens and configured credentials are used to authenticate API requests the user has authorized. ContentFactory is designed to store runtime token files outside the source repository in a user-local application directory. Tokens and client secrets are not intentionally displayed in status output, reports, this website, or version-controlled files. Users remain responsible for protecting their own device and developer credentials.

5. Local and external processing

Video rendering, local AI assistance, local text-to-speech, quality checks and SQLite workflow state can run on the user's device. ContentFactory is local-first, not exclusively local. When a user connects a service or requests an API operation, the information required for that operation is transmitted to the relevant external platform. For example, analytics requests send account or video identifiers, and an explicitly authorized upload sends the selected media and metadata.

6. How information is used

Information is processed to provide the feature requested by the user: identify an authorized account, discover authorized videos, display and store available analytics, validate media, maintain review and audit state, perform a specifically approved platform operation, map a platform video back to a local record, and compare generation strategies using performance evidence.

7. Sharing and service providers

ContentFactory does not include a feature that sells personal information. Information may be transmitted to a connected service only as needed to use its API or complete an operation the user requests. A static hosting provider may process ordinary network information, such as IP addresses and request logs, when serving this website under that provider's own practices.

8. Third-party platforms

Connected services may include TikTok and Google / YouTube. Their handling of information is governed by their own terms, privacy policies, account settings and developer-platform rules. ContentFactory cannot control the availability, policy decisions or independent processing of those services.

9. Retention

Generated files, local database records, analytics snapshots, approval records and token files may remain on the user's device until the user removes them, revokes access, resets the relevant local data, or the software replaces them as part of its normal operation. The project does not claim a universal fixed retention period where the software does not define one. External platforms retain information according to their own policies.

10. Security

ContentFactory applies practical safeguards such as keeping configured secrets outside the repository, limiting scopes by feature, avoiding token output, validating files before controlled publishing, and requiring explicit approval before a real write. No software or transmission method can guarantee absolute security.

11. User controls

Users can choose not to connect an account, decline a requested OAuth scope, revoke an authorization from the platform, and remove applicable local token, database, analytics or generated-content files they control. Before deleting local data, users should keep any backup they need. Questions or privacy requests may be sent to the contact below.

12. Children and eligibility

ContentFactory does not establish a universal minimum age for every connected service. Users must meet the age, capacity, parental-consent and account-eligibility requirements imposed by the platform they connect and by applicable law. Content intended for children remains subject to additional review and platform-specific obligations.

13. Changes to this policy

This policy may be updated as ContentFactory changes. The effective date will be revised when a new version is published. Material changes should be reviewed before continuing to use connected features.

14. Contact

For privacy questions or requests, contact: fesquedylan6@gmail.com