Effective & Last Updated: November 16, 2026

Privacy Policy

Rich Clips Studio (“Rich Clips”, “we”, “our”) is built on a strict local-first privacy architecture. This Privacy Policy explains what data is accessed when you use Rich Clips Studio and the companion HTTPS OAuth callback relay at https://rich-clips-auth.vercel.app, how credentials are encrypted on your own device, and how you can revoke access or delete all stored data at any time.

Core Privacy Guarantee: Zero OAuth tokens, client secrets, user profiles, or video files are stored on rich-clips-auth.vercel.app, and Rich Clips never sells, rents, licenses, or shares user data with third-party data brokers, advertisers, or analytics networks.

1. Platform APIs & Scopes We Access

Rich Clips interacts with external platform APIs strictly as configured and initiated by you inside your local Studio instance:

  • TikTok API (Login Kit & Content Posting API): When you connect a TikTok account, Rich Clips requests OAuth 2.0 PKCE authorization for user.info.basic (to display your connected TikTok handle/open_id and query creator video duration/privacy limits), video.upload (to upload creator-initiated Share-to-Inbox draft clips), and video.publish (to publish creator-initiated Direct Post videos). Rich Clips never reads private messages or uploads videos without your explicit action.
  • Instagram / Meta Graph API: When you connect an Instagram Professional account via Meta Unified Login, Rich Clips uses instagram_business_basic and instagram_business_content_publish solely to identify your linked Instagram handle and publish rendered 9:16 Reels when you click publish.
  • YouTube Data API v3: Used to search public video metadata (titles, channel names, durations, and view counts) for viral topic discovery. Rich Clips’ use of YouTube API Services adheres to the Google Privacy Policy.
  • Twitch Helix API: Used with app-level credentials to search public game categories, clips, and VOD metadata for viral topic discovery.
  • AI Transcription & Highlight Providers (Gemini & Groq): When you generate clips with burned captions or AI story-arc scoring, audio excerpts and transcript metadata are sent using your own configured API keys solely to produce word-level timestamps and clip copy.

2. Stateless Zero-Secret OAuth Callback Relay

Because TikTok and Meta require public HTTPS redirect URIs, https://rich-clips-auth.vercel.app/api/auth/tiktok/callback and https://rich-clips-auth.vercel.app/api/auth/instagram/callback act purely as stateless HTTP 302 relays:

  • The relay validates that the encoded return origin points exclusively to http://localhost:<port>, http://127.0.0.1:<port>, or a private RFC1918 LAN IPv4 address, blocking all external open redirects.
  • The relay holds zero OAuth client secrets, performs zero token exchanges, sets zero tracking cookies, and retains zero persistent logs or databases.

3. Local AES-256-GCM Encrypted Token Storage

All OAuth token exchanges (including PKCE code_verifier validation) happen directly between your local Rich Clips Studio server and the official TikTok or Meta token endpoints over HTTPS:

  • Access tokens, refresh tokens, and temporary single-use OAuth PKCE state nonces are encrypted at rest using authenticated AES-256-GCM encryption keyed by your local TOKEN_ENCRYPTION_KEY inside your local SQLite database (rich_clips.db).
  • Browser API endpoints (such as /api/settings/health) return boolean-only configuration flags and never transmit raw API keys, client secrets, or encrypted token payloads to the browser.
  • Downloaded video slices, rendered 9:16 MP4 clips, and exported caption bundles remain strictly inside your local MEDIA_WORKDIR folder.

4. Zero Third-Party Data Resale or Profiling

Rich Clips does not collect telemetry, behavioral analytics, or advertising identifiers, and never sells, brokers, or transfers user or creator data to any third party. Data leaves your machine only when calling the official YouTube, Twitch, TikTok, Instagram, Gemini, or Groq APIs at your direction.

5. User Revocation & Data Deletion Instructions

You have complete, immediate control to revoke OAuth permissions and permanently delete all data stored by Rich Clips:

  • Disconnect & Delete Inside Rich Clips Studio: Open Accounts & System in your local Rich Clips Studio UI and click Disconnect next to any TikTok or Instagram account (calls DELETE /api/accounts/:id), which immediately deletes the encrypted token row from SQLite. Deleting any clip or project inside Studio permanently removes its database record and local rendered media files, or you may delete rich_clips.db and MEDIA_WORKDIR directly on disk.
  • Revoke TikTok Access: In the TikTok app, go to Profile → Menu → Settings and privacy → Security and permissions → Apps and services permissions, select Rich Clips, and tap Remove access.
  • Revoke Instagram / Meta Access: Open Instagram or Facebook Settings → Apps and Websites (or Business Integrations) and remove Rich Clips. Automated Meta deauthorization and deletion webhooks are also supported at /auth/instagram/deauthorize and /auth/instagram/delete.
  • Revoke Google / YouTube & Twitch Access: Manage or revoke Google permissions at myaccount.google.com/permissions and Twitch connections at Twitch Settings → Connections.