Legal

Privacy Policy

Last updated: October 25, 2026

Who we are

FrameOS (frameos.studio) is a software service that turns long-form podcasts and videos into short, publish-ready clips. FrameOS is run by Satvik Shrivas, based in India. This policy explains what information we collect when you use FrameOS, how we use it, how long we keep it, and the choices you have. It applies to the FrameOS website, dashboard, processing pipeline, and the FrameOS connector that AI assistants use at frameos.studio/mcp (see Using FrameOS from AI assistants).

Information we collect

  • Account information. We use Clerk to handle sign-in. When you create an account, we receive and store your email address and name, along with a unique account identifier.
  • Content you submit. Source videos you upload or link for processing, and the clips, transcripts, captions, and related metadata our pipeline generates from them.
  • Connected channel information. If you choose to connect a YouTube channel, Facebook Page, Instagram professional account or LinkedIn profile, we store the account's ID, name and profile picture, the OAuth tokens needed to publish on your behalf, and, where the platform shares them, the statistics of its posts that the Analytics page shows (see Social publishing and Google user data below).
  • AI assistant connections. If you connect an AI app to FrameOS, we keep a daily count of which app you used and which FrameOS tools it called (see Using FrameOS from AI assistants below).
  • Payment information. Payments are handled by third-party payment processors. We never receive or store your card numbers or full payment details; we keep only records of your plan and transaction status.
  • Technical information. Standard request and error logs needed to operate, secure, and debug the service.

How we use information

We use your information to provide the service: authenticate you, process the videos you submit, generate and store your clips and transcripts, publish clips to channels you have connected when you explicitly choose to publish (in the dashboard, or by asking an AI app you've connected to FrameOS), bill for paid plans, respond to support requests, and keep the service secure and reliable. We do not sell your personal information, and we do not use your videos to train models or for any purpose other than delivering the service to you.

Analytics and cookies

We use analytics to understand how visitors find and use FrameOS so we can improve it — for example, which pages people view and where they drop off before signing up. These tools may set cookies and record aggregated interaction data such as clicks, scrolls, and the pages you visit.

  • Google Analytics 4. Aggregated traffic and usage metrics. GA is gated behind your cookie choice using Google Consent Mode v2 — it sets no analytics cookies until you accept the consent banner.
  • Microsoft Clarity and Contentsquare. Heatmaps and session replay that show how visitors move through the site so we can find and fix friction. They capture interaction events (clicks, scrolls, page paths) and, by default, mask the text you type into form fields.
  • Vercel Analytics and Speed Insights. Cookieless, aggregated traffic and performance (Core Web Vitals) measurement.
  • Ahrefs Web Analytics. Aggregated traffic measurement, such as which pages are visited and which sites send visitors to FrameOS.

You can decline analytics cookies using the banner shown on your first visit, and you can block or clear cookies through your browser settings at any time. To opt out of Google Analytics specifically, install Google's opt-out browser add-on.

Your videos and generated clips

Source videos you upload are stored only for processing and are automatically deleted within 7 days. Generated clips, transcripts, and thumbnails are stored in Google Cloud Storage so you can review, download, and publish them from your dashboard, and they remain available until you delete them or your account is closed.

We automatically check frames from every video you submit for sexually explicit content. If a video is flagged, we keep a private copy of it and the flagged frames while our team reviews it; you can keep using the video in the meantime. If they find nothing wrong, the copy and frames are deleted straight away and are gone for good within 7 days. If the video breaks our rules, we keep them for 30 days as a record of that decision, then delete them, unless the law requires us to keep them longer.

Social publishing and Google user data

FrameOS lets you connect your own YouTube channel, Facebook Page, Instagram professional account or LinkedIn profile so you can publish clips directly from FrameOS and see how your posts perform. Each platform is covered below, starting with YouTube.

The YouTube connection uses Google's official OAuth consent flow — you grant access on a Google-hosted screen, and we never see your Google password. FrameOS asks for two permissions: to upload videos to your channel, and to view your YouTube account.

  • What we store. The OAuth tokens Google issues (encrypted at rest with AES-256-GCM); your channel's ID, name, profile picture and subscriber count; and, for each video on your channel, its title, link, thumbnail, length, publish date and its view, like and comment counts. We do not read or store any other data from your Google account.
  • What we use it for. The upload permission is used only to upload a clip when you choose to post it now or schedule it — from the dashboard, or by asking an AI app you've connected to FrameOS to post it — with the title, description and visibility you set. We never publish anything without your direct action. The view permission is used to show which channel is connected, and to show your videos' statistics to your workspace on the Analytics page, refreshed about once an hour. This data is never sold, never used for advertising, and never shared with anyone outside your workspace, except that an AI app you connect to FrameOS yourself can see your channel's name, ID and profile picture (see Using FrameOS from AI assistants below).
  • How to disconnect. You can disconnect your channel at any time from the dashboard, which immediately discards the stored tokens and stops all further reads. Statistics already collected stay in your workspace until you close your account or ask us to delete them at support@frameos.studio. You can also revoke FrameOS's access from your Google security settings at myaccount.google.com/permissions.

FrameOS's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

FrameOS uses YouTube API Services to publish clips to your connected channel and to show your videos' statistics. By connecting a YouTube channel you also agree to the YouTube Terms of Service, and you can review the Google Privacy Policy to understand how Google handles data accessed through these APIs.

Facebook, Instagram and LinkedIn connect the same way: you grant access on Facebook's or LinkedIn's own screen, and we never see your password for them. Instagram connects through Facebook, using the Facebook Page your Instagram professional account is linked to.

  • What we ask for. On Facebook, permission to list the Pages you manage, read their posts' engagement, and post to them. On Instagram, permission to read your professional account's profile and posts, and to publish to it. On LinkedIn, your basic profile (name and profile picture) and permission to post on your behalf.
  • What we store. The access tokens each platform issues (encrypted at rest with AES-256-GCM); each connected account's ID, name or username, and profile picture; and, for Facebook Pages and Instagram accounts, the follower count and each recent post's caption, link, thumbnail, publish date, and like and comment counts that the Analytics page shows. LinkedIn doesn't share post statistics with apps, so we store none from it.
  • What we use it for. Posting a clip only when you choose to post it now or schedule it — from the dashboard, or by asking an AI app you've connected to FrameOS — with the caption you set, and showing your posts' statistics to your workspace on the Analytics page. This data is never sold, never used for advertising, and never shared with anyone outside your workspace, except that an AI app you connect to FrameOS yourself can see each account's name, ID and profile picture.
  • How to disconnect. Disconnect an account at any time from the dashboard, which immediately discards its stored tokens. You can also remove FrameOS in your Facebook settings (Business Integrations, or Apps and Websites) or your LinkedIn settings (Permitted Services). To have statistics we already collected deleted, email support@frameos.studio.

Using FrameOS from AI assistants

You can use FrameOS from AI apps such as Claude, ChatGPT, Codex, Cursor, VS Code with GitHub Copilot, Gemini CLI, Perplexity and Grok, through the FrameOS connector. To connect one, you sign in to FrameOS from the AI app and approve access. The AI app never sees your FrameOS or Google password.

  • What the AI app can see. Once connected, the AI app can read your workspace name, plan, credit balance and recent credit use; your project and clip titles and the links you submitted; transcripts; clip details such as start and end times, hooks and caption style; your brand settings, collections and thumbnails; temporary links to preview or download your clips, which expire after about an hour; and the names, IDs and profile pictures of your connected social accounts. It never receives the sign-in tokens for those social accounts.
  • What FrameOS receives from the AI app. Only what the app sends when it uses a FrameOS tool — for example, a video link or file to clip, what to focus on, or the title and caption for a post. We handle it the same way as anything you submit in the dashboard. FrameOS can't see your chats, the AI app's memory, or files you haven't sent to FrameOS.
  • The AI app's own policy. Anything FrameOS returns becomes part of your conversation with that app. From there, the AI app's own privacy policy and settings decide how it is stored and used, including whether your chats are used to train its models. Check the settings of the AI app you use.
  • What we don't do. We don't sell anything that comes through the connector, and we don't use it to train AI models. To run and protect the connector, we keep a daily count of which AI app you used and which FrameOS tools it called.
  • Sign-in tokens. When you connect, the AI app gets an access token that lasts about 24 hours, and usually a refresh token so it can renew access without asking you to sign in again. These tokens only let the app use FrameOS tools for your workspace; they give no access to your Google account.
  • How to disconnect. Remove or disconnect FrameOS in the AI app's settings (usually under connectors, MCP servers or plugins). To cut off every AI app at once, or to delete your account and data, email support@frameos.studio.

Service providers (subprocessors)

We rely on a small set of providers to run FrameOS. Each processes data only as needed to deliver their service to us:

  • Google Cloud — storage of generated clips and transcripts, and compute for video processing.
  • Clerk — authentication and account management, including sign-in for AI apps you connect to FrameOS.
  • Vercel — website and application hosting.
  • Supabase — managed database hosting.
  • Upstash — job queues and short-lived processing data.
  • Groq, Google Gemini and Anthropic — AI transcription and analysis of the media and transcripts you submit, such as finding the best moments for clips and drafting post captions.
  • Dodo Payments — checkout, subscriptions and billing for paid plans.
  • Brevo — account and product emails.
  • Zendesk — support chat and help requests.
  • Canny — the feedback and feature-request board.
  • Google Analytics, Microsoft Clarity, Contentsquare, Vercel Analytics, and Ahrefs Web Analytics — website usage analytics, heatmaps, and session replay (see Analytics and cookies above).

Retention

Uploaded source videos are deleted automatically within 7 days. The private copy of a video flagged by our content check is deleted once our team finds nothing wrong with it, and may be kept as a record if the video breaks our rules (see above). Generated clips and transcripts are kept until you delete them or close your account. Account records are kept for as long as your account is active. OAuth tokens for connected channels are kept only while the connection is active and are discarded immediately when you disconnect. Statistics collected from a connected channel for the Analytics page are kept until you close your account or ask us to delete them. Daily counts of the AI apps and FrameOS tools you used are kept for as long as your account is active. Operational logs are retained for a limited period for security and debugging.

Security

We protect your data with industry-standard measures, including encryption in transit, encrypted storage, AES-256-GCM encryption for OAuth tokens at rest, and access controls that limit data access to what is needed to operate the service.

Your rights

You can request a copy of the personal information we hold about you, or ask us to delete your account and associated data, at any time by emailing support@frameos.studio. We respond to verified requests promptly.

Changes to this policy

If we make material changes to this policy, we will update the date at the top of this page and, where appropriate, notify you by email or in the dashboard before the changes take effect.

Contact

Questions about privacy or this policy: support@frameos.studio.

See also our Terms of Service, or return to the FrameOS homepage.