ReelForge

Support

Fix safely, share minimally

Start with the exact error, app version and failed stage. Never email secrets.

Current listed version Not published · support operator Not configured

Release status: Requires legal review and a configured support address before launch.

Contact

Support email not yet live

Include order number only when the issue concerns purchase/license. Never include API keys, license keys, passwords, OAuth tokens or full project media.

Useful first checks

  1. Confirm system requirements: Windows 10/11 x64, 16 GB RAM minimum, adequate disk and current drivers.
  2. Open the in-app readiness/diagnostics view and record the named failing check.
  3. Retry only the failed stage; ReelForge retains partial projects for recovery.
  4. For provider failures, verify quota/status in that provider's console.

Diagnostic bundle

Create a diagnostic bundle only with explicit consent. First preview the exact JSON inventory, then confirm export. Review diagnostic.json again before sharing. It excludes raw logs, project names/media, prompts, scripts, paths, emails, API/license keys and OAuth tokens.

YouTube and OAuth

Uploads are Private/manual by default. For authorization problems, revoke ReelForge in your Google Account → Security → Third-party access. ReelForge stores its YouTube sign-in token locally, encrypted with Windows DPAPI; after you revoke access, publishing again re-prompts Google authorization and requests only the minimum scopes it needs.

License/device move

In Settings → License, select Deactivate on the old device, then activate the receipt's license key on the new one. If the old device is unavailable, use the hosted customer portal or contact support with the order number.

Scope

Support covers ReelForge installation, activation and reproducible product defects. It cannot guarantee YouTube monetization, views, revenue, third-party API uptime or legal/factual review of generated content. Jurisdiction: Not configured.