Who we are
FrameOS (frameos.studio) is a software service that turns long-form podcasts and videos into short, publish-ready clips. 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, and processing pipeline.
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, we store the channel's ID and name and the OAuth tokens needed to publish on your behalf (see Social publishing and Google user data 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, 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.
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.
Social publishing and Google user data
FrameOS lets you connect your own YouTube channel so you can publish clips directly from the dashboard. This connection uses Google's official OAuth consent flow — you grant access on a Google-hosted screen, and we never see your Google password.
- What we store. Only the OAuth tokens Google issues (encrypted at rest with AES-256-GCM) and your channel's ID and name. We do not read or store any other data from your Google account.
- What we use it for. The tokens are used solely to upload clips that you explicitly choose to publish to your own channel. We never publish anything without your direct action, and we never read private account data beyond your channel's identity.
- How to disconnect. You can disconnect your channel at any time from the dashboard, which immediately discards the stored tokens. 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.
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.
- Vercel — website and application hosting.
- Groq and Google Gemini — AI transcription and analysis of the media you submit for processing.
- Aiven — managed database hosting.
Retention
Uploaded source videos are deleted automatically within 7 days. 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. 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.