ReelForgeHome

Privacy Policy

Last updated: 2026-05-27

This policy describes what data ReelForge collects when you use the service, how we use it, who we share it with, and the choices you have about it. By using ReelForge you agree to the practices below.

1. Information we collect

We collect data in three categories:

  • Account data — email address, name, password hash, organisation membership, and timestamps for sign-up and last sign-in.
  • Connected-platform data — when you connect an Instagram, YouTube, or other publishing account via OAuth, we store the access token and refresh token (encrypted at rest), the external account id and display name, the scopes you granted, and metadata required to publish on your behalf (e.g., Instagram Business Account ID). We do not store your social-platform password.
  • Content data — playbooks, generated scripts, generated reels / carousels / posts, rendered media files, and the performance metrics we fetch from the platforms you publish to.

2. How we use it

  • To generate content in the style of the reference accounts you add.
  • To publish that content to your connected social accounts when you approve a post.
  • To poll your published posts for metrics (views, likes, comments) so you can see performance inside the product.
  • To operate, maintain, and improve the service.
  • To send you operational emails (sign-up confirmation, password reset, security alerts).

3. Who we share it with

We share data with third parties only to the extent needed to operate the product:

  • Meta (Instagram + Facebook) — when you publish to Instagram, we send the rendered media URL, caption, and your OAuth access token to Meta's Graph API. We also pull metrics back from Meta. Subject to Meta's Privacy Policy.
  • Google (YouTube) — when you publish to YouTube, we send the rendered video, title, and description to YouTube's Data API using your OAuth access token. We also pull metrics back from YouTube's Analytics API. Subject to Google's Privacy Policy.
  • LLM providers — text and image data used to generate playbooks and scripts is sent to our LLM providers (currently OpenRouter, which routes to Anthropic / Google / OpenAI per request). Those providers do not train on or retain the data per their API terms.
  • Infrastructure providers — our hosting provider (Vultr) and object storage (self-hosted MinIO) hold the data at rest. We do not sell or rent your data to anyone.

4. Use of YouTube API services

ReelForge uses YouTube API services to upload videos on your behalf and read back engagement metrics. By connecting your YouTube account you are also agreeing to the YouTube Terms of Service. You can revoke ReelForge's access at any time via Google's security settings.

5. Where data is stored

Application data is stored in a managed PostgreSQL database and self-hosted MinIO object storage, both running on infrastructure located in the United States. Encryption keys for OAuth tokens are stored separately from the encrypted ciphertext.

6. Data retention

We keep your data while your account is active. When you delete a connection, the OAuth token is revoked and marked deleted but historical posts published through that connection are preserved. When you delete your account, see the Data Deletion Instructions for what gets removed and on what timeline.

7. Your rights

You can:

  • Access and export your data — email us.
  • Correct inaccurate data — most fields editable in app, or email us.
  • Delete your data — see the Data Deletion Instructions.
  • Revoke connected-platform access — disconnect from inside the app, or revoke from the platform directly.

8. Cookies

We use a single authentication cookie to keep you signed in between page loads. We do not use third-party tracking, analytics cookies, or advertising cookies.

9. Children

ReelForge is not directed to children under 13. If you believe a child has provided us data, email us and we will delete it.

10. Changes to this policy

When we make material changes we will update the "Last updated" date at the top and, if appropriate, notify you by email or in-app banner.

11. Contact

Questions, requests, or complaints: email [email protected].