Stays on your Mac.

What the app can see

macOS asks before each of these, and you can turn them off in System Settings. The app uses a permission only for the feature that needs it.

• Camera. The floating camera window.
• Microphone. Live captions and recorded audio.
• Screen Recording. Previewing and recording a crop of the display.
• Speech Recognition. Turning speech into caption overlays and brief transcripts, on your Mac.
• Input Monitoring and Accessibility. Showing keys you press in other apps on an overlay. Those keys are drawn on your screen. They are not sent anywhere. Don’t type passwords while that overlay is visible.

Video briefs

A brief is built on this Mac from the video you choose. Speech, on-screen text, and sampled images stay in a local working folder while the brief is made, then you export a file you control. Sharing that file with an AI tool, or anyone else, is a separate choice you make outside FrameCast. See video briefs for AI and screen record without uploading.

What is stored

Looks, overlays, and settings are saved on your Mac. Photos you place in overlays are copied into FrameCast’s local folder. Recordings and exports go where you save them.

Voice-over

Generating a voice-over sends the selected script and delivery settings to FrameCastat getframecast.com and to our speech provider to create the audio. Transcription runs on your Mac. The generated audio is returned to the app for your assets and timeline. Older app versions can send a recording for voice conversion; system audio is included when it was mixed into that recording. FrameCast does not retain a copy of uploaded recordings. Account credit transactions and voice-conversion usage are recorded. For each generated voice-over, FrameCast records the voice, model, length, and cost, not the script. Our speech provider processes submitted text and recordings under its own terms. Ordinary exports do not upload recordings or scripts.

AI music and generated visuals

Music you compose is kept by FrameCast, tagged with its mood, genres, instruments, and tempo, and may be offered to other FrameCast users who want the same kind of music. To tag it and to find matching tracks, your music description and your video’s script are sent to our AI provider; neither is stored. Music whose description names a brand, company, or person stays private to you and your team. Stills and clips generated for Suggest visuals are stored once and reused for anyone who asks for exactly the same prompt.

Files and photo sync

FrameCast Files holds what you add to it: uploads from the website or apps, photos and videos taken with the FrameCast camera, recording backups, and, if you turn on photo sync, the photos and videos on your iPhone. Files are stored with Cloudflare R2 in the United States and open through links that expire within an hour. FrameCast records each file’s name, folder, type, size, who added it, from which device, and when it was added, changed, and last opened, but doesn’t look inside it. The iPhone app makes the small previews you browse, on the iPhone.

Photo sync. It’s off until you turn it on, and it needs full access to your photo library, which iOS asks for. While it’s on, iOS uploads photos and videos in the background, mostly while the iPhone charges on Wi-Fi, and they stay in your photo library. With each one, FrameCast keeps its capture date and an identifier from your photo library so the same photo is never uploaded twice. You choose whether to include videos and screenshots, and you can turn it off at any time; what was already uploaded stays in Files until you delete it.

Who can see them. My Files are private to you. They sit on your personal plan, they are not counted against any team, and team admins cannot open them. Each team is a separate drive. See teams and roles. Owners and admins can see that team’s files, including restricted folders. Members see unrestricted folders. A contributor sees only what they uploaded and folders granted to them. A viewer can read and download. A restricted folder stays hidden from people who were not granted view or edit.

Photo sync into a team asks you to confirm first, because that team’s admins will see those photos. Personal photo sync stays in My Files. Team admins see devices that sync into their team: name, model, app version, and sync status, and how much of that team’s storage each member uses. They do not see devices that only sync to your personal library or to another team.

Finder and the Files app. If you turn on a drive in FrameCast on your Mac, or use the Files app on your iPhone, the system lists its folders and downloads files to your device when you open them. Files you add or change there are uploaded to FrameCast.

Deleting and keeping files. Deleted items stay in Trash for 30 days, then are removed from storage. Emptying Trash removes them right away. FrameCast never deletes files to make room: when storage is full, uploads stop until you make space or add storage. If your personal paid plan ends, its files are kept, read-only, for 90 days. After that, the newest files that fit in the free plan stay and the rest are deleted. If a team’s subscription ends, only that team goes read-only for 90 days. During that time you can move your own uploads from that team into My Files if your personal plan has room. After 90 days, that team’s files are deleted. Your other teams and your personal files are not part of that deletion. Your account page shows what will be removed and when.

Share links

When you choose Share link, or turn on “Copy a share link when I stop,” the video is uploaded to Cloudflare R2 along with a poster image, captions, a transcript, chapters, and a title and summary written on your Mac when it can. A link to a recording you haven’t edited also carries its cursor log: where the pointer moved and clicked, and when keys were pressed (never which keys), so the web editor can follow your cursor. People watching the link never receive it; only you, and your team for a team video, can open it in the editor. Anyone with the link can watch unless you set a password, an expiry date, or limit it to your team or an email domain. Public links can appear in search engines; the others ask search engines not to index them. Deleting a link removes the video, its views, and its comments.

What we record about viewers. Each time someone watches, the player reports how many seconds they watched, how far they got, which parts they saw, whether they finished, whether they clicked the call-to-action button, the site that linked them there, and an approximate country from the connection. Viewers who aren’t signed in are counted with a random-looking code made from their connection, browser, and the date; the IP address isn’t stored, and the code changes every day. If a viewer is signed in to FrameCast, the creator of the video can see their name and email address and how much they watched. Your own plays of your videos aren’t counted.

Comments and reactions. Comments are shown to everyone who can watch the video, under your account name or the name you type. The creator can delete any comment on their video, and you can delete your own. Reactions are counted without names.

Email. Creators get an email for the first view of each link, for new comments, and a daily summary, sent through Resend. Each email has a link to turn it off, and every kind can be switched off on your account page.

Recording in the browser. The recorder at /record uploads the video to your share link while you record. If you leave Captions and transcript on, your browser’s built-in speech recognition turns your microphone into text as you talk, which can send your voice to the browser maker’s speech service. The finished text is saved with the video as its captions and transcript.

AI on your videos. After you share a video with speech, its transcript, title, and chapters are sent through Vercel’s AI Gateway to a language model provider to write the summary shown under it, unless one was already written on your device and covers the whole video. You can turn this off in your account under AI, and a team can turn it off for its videos. The same is sent when you ask for a summary, a document, a bug report, how-to steps, a message, action items, or translated captions. The video itself isn’t sent. The result is saved with the video until you delete it.

Anyone can report a video. Reports are reviewed by hand, and videos that break the rules are removed.

Studio in the browser

The studio at /studio runs in your browser. Media you import, your projects, and your exports are kept in the browser’s private storage on your device and are never sent to FrameCast. Clearing this site’s data in your browser deletes them. Nothing leaves the device unless you choose Save to cloud, which uploads that export to FrameCast Files, or generate a voice-over, which sends only that script and its delivery settings, as described above. Suggest voice & delivery from text sends only that script, with the list of studio voices, through Vercel’s AI Gateway to a language model provider to pick a voice and delivery; the script isn’t saved. Analyzing a video for an AI script sends a low-resolution copy, as described next.

AI scripts in the studio

When you choose Analyze in the studio’s Script tab, your browser makes a small, low-resolution copy of that video, including its sound, and uploads it in parts to FrameCast’s storage. Each part is sent to Google’s Gemini API to be described with timestamps, then deleted from FrameCast’s storage; requests ask Google not to store them. FrameCast keeps the resulting timeline (scenes, on-screen text, speech, and other moments), the file’s name and length, a fingerprint used to recognize the same file later, and the cost, so the video never needs analyzing again. Writing a script sends that timeline and your instructions to Gemini; FrameCast records the instructions, the number of passages, and the cost, not the script. Delete a timeline from the Script tab at any time. Your original video file stays on your device.

In the Mac app you can also have the analysis follow the mouse. For a FrameCast recording, each part is then sent with where the pointer moved and clicked and when keys were pressed, never which keys. That log goes to Gemini with the part and isn’t stored; only the resulting timeline is kept.

When you start a project from a website, in the studio or the Mac app, FrameCast’s server reads that public page and up to three more pages on the same site, like its features or pricing, and sends their text with your instructions to Gemini to write the script. It only reads addresses on the public internet. FrameCast doesn’t keep the pages or the script; it records the cost.

Usage statistics

To see which features people use, the app sends short usage events to FrameCast at getframecast.com: that the app opened, that a recording finished (its length and whether the camera, microphone, and system audio were on), that an export finished (its format and whether captions, voice clean-up, or a voice-over were used), and that a video brief was made. Each event carries a random install id created by the app, the app and macOS or iOS versions, and your language setting. If you’re signed in, events are linked to your account. An approximate country is derived from the connection; the IP address isn’t stored.

Events never include video, audio, screen contents, captions, scripts, keys you press, or file names. They are kept for up to 13 months and aren’t sold or shared with advertisers. Turn them off any time in FrameCast under General → Usage statistics on the Mac, or Account → Share usage statistics on iPhone.

This website

Sign-in uses Apple, email and password, or a one-time email code, and sets a session cookie for that account. On your first visit, the site also sets one first-party cookie that notes the page you arrived on, the site that linked you there, and any campaign tag in the link. It is read only if you create an account, to record where that account came from, together with an approximate country and city from your connection. Optional Meta and Trybe ad measurement runs only after you choose “Allow ad measurement.” It sends visits to public marketing pages, browser and device information (including the connection’s IP address), advertising cookie identifiers, and the value and currency of a confirmed Pro or Team purchase to Meta to measure and improve our Facebook and Instagram ads. An opaque purchase event identifier helps prevent duplicate reporting. We do not enable automatic matching or send names, email addresses, payment card details, recordings, scripts, or editor contents as event data. Private account and workspace pages do not send page-view events; a verified checkout return can send the purchase event. Meta processes this data under its own privacy policy. Trybe receives consented public-page visits, campaign tags, browser/device information and an anonymous visitor cookie through track.getframecast.com. At checkout, that visitor ID and your consent are attached to the Stripe checkout. Once Stripe confirms payment, our server sends Trybe the actual amount, currency, payment time and an opaque order ID, without your name, email or card details. Trybe credits creators using its seven-day last-click attribution. Free downloads, signups, unpaid checkouts and automatic subscription renewals are not reported as new checkout conversions. A consented checkout already in progress can still be reported when Stripe confirms it. No measurement script loads before consent, and declining does not affect recording, editing, or purchases. Choose “Privacy choices” on the website to withdraw consent; future browser measurement stops and the site clears its Meta and Trybe cookies. Global Privacy Control overrides an opt-in. Your choice is kept in this browser for up to 180 days, and local purchase markers help avoid sending the same purchase again. Ad blockers, declining consent, or not returning from checkout can limit Meta attribution. Trybe receives paid checkout events server-side and does not require a return visit. The voice-over API on this site runs when the app requests an overlay. Payments for voice credits are handled by Stripe. FrameCast stores the credit balance and a Stripe customer id for the account, not the card number. The app download is served from Cloudflare R2 storage through a short-lived link. The App Store link for the iPhone app leaves this site for Apple.

Deleting your account

Delete your account any time from the account page on this site, or in the iPhone app under Account → Delete account. It removes your share links and their files, your files and synced photos, your devices, comments you left, voice credits, studio video analyses and AI script records, usage events linked to the account, and your sign-in, and it cancels any subscription by deleting the Stripe customer. Videos and files you added to someone else’s team stay with that team, still showing that you added them. If you own a team other people are in, transfer it to an admin or close it first; closing a team moves each person’s uploads and recordings into their own My Files. Teams only you are in are deleted with your account.