Privacy Policy
Last updated: November 2026
The short version: your footage is isolated to your account, and My Feature Flow does not use your recordings or rendered videos to train models. Specialist processors also handle content under their own policies; the supplier training caveat is explained below. Sign-in uses one-time email codes, not passwords.
1. What this privacy policy covers
This Privacy Policy explains what My Feature Flow collects, why, and how it is handled when you visit our website or use the My Feature Flow service. It applies to account holders and visitors to the public site. If team or organization features are introduced, this policy will be updated to cover them before they launch.
2. Personal data we collect
- Account data: your email address, name, and optional company name, used to create and secure your account.
- Content you provide: screen recordings, uploaded media, edited scripts, brand assets, and the videos rendered from them.
- Usage and billing data: videos produced, generation credits consumed, and technical logs needed to operate, meter, and audit the service.
- Support communications: messages you send via the contact form or support channels.
3. What we do not collect
My Feature Flow does not use account passwords (sign-in is via one-time email codes), does not sell personal data, does not run advertising trackers inside the signed-in app (our public website's ad measurement is described below), and does not use your recordings or rendered videos to train machine-learning models.
We also do not collect or store presenter likenesses — photographs or video of a person’s face used to build an on-screen presenter. That is not a rule we apply by hand: there is no way to give us one. Presenters come from our fixed cast, the only presenter identity a project holds is which one you picked, and the product has no way to accept your own photo or video to create one. This is separate from the profile photo you can add in Settings and from people who may appear in footage you upload. See “On-screen presenters” in the Terms of Service.
4. How we use information
- To provide the service: processing, editing, rendering, and delivering videos.
- To secure accounts and enforce per-account isolation of content and data.
- To meter usage, prevent abuse, and enforce plan limits.
- To respond to support requests and send essential service notices.
- To improve reliability using aggregated, de-identified operational metrics.
5. Where your content lives
Content and data are stored on Amazon Web Services infrastructure in account-isolated storage: every object, record, and processing job is scoped to your account and authorized server-side on every request. Finished videos are delivered through signed, expiring URLs. Provider credentials used by the pipeline are held in AWS Secrets Manager — never in application code.
6. Subprocessors we rely on
We use a small set of specialist providers to run the service. Each one receives the information used for the features you choose, and handles it under its own terms and privacy policy:
- Amazon Web Services — hosting, storage, databases, sign-in, email, transcription, and content-safety checks, including reading the text shown in your recordings and photos.
- Anthropic — AI planning of your video, translation of its script, content-safety checks, and quality checks of moving photos and of the finished cut. These can send Claude your scripts, your photos, frames from your recordings, and frames sampled from the clips made from your photos.
- OpenAI — AI script rewrites you ask for, translation when our main translator is unavailable, “Check specs with AI”, and reading a product page from a link.
- ElevenLabs — narration voices.
- Shotstack — video rendering.
- HeyGen — presenter clips, only for videos with a presenter.
- Google — AI-generated scenes, AI title-card artwork, and moving clips made from your photos. For these we send Google the photos or reference pictures involved and the instructions for the clip.
- Stripe — payments, only when you buy a plan or credits.
- Cloudflare — the security check on the sign-up and sign-in forms.
When you choose “Check specs with AI” on a product video, the brand, model and product details you typed are sent to an AI provider that searches the web for that product, together with a one-way code for your workspace that the provider uses only to detect abuse; nothing else from your workspace is sent.
7. How presenter videos are made
You can choose a presenter when you create a project. This section was published before the feature was, so that what we will and will not do with a presenter was on the record before anyone could make one — and it has not changed since.
When a video uses an on-screen presenter, that part of it is generated by a specialist supplier rather than by us. The narration audio for the presenter’s clip is uploaded to that supplier as a file, along with the settings for the shot — which character presents, how long the clip runs, how it is framed — and the finished clip is downloaded back into your account’s storage. Your recordings, screenshots, transcripts, and rendered videos are not sent.
We spell this out because it is genuine third-party processing of your content: for those clips your narration audio is handled on the supplier’s systems as well as ours, and it is kept and deleted there under the supplier’s own practices, not ours. Videos made without a presenter never involve this step.
There is one thing we cannot promise on a supplier’s behalf. The privacy policy of the supplier that generates presenter footage permits it to use content submitted to it to train and improve its own models, and opting out of that is a request made to that supplier rather than a setting. Our own commitment not to train models on your content covers what My Feature Flow does; it cannot rewrite another company’s policy. We would rather say so plainly here than let it be assumed.
8. Data retention and deletion
Recordings, plans, and rendered videos are kept while your account is active. When you delete a project in the app, its files are deleted, and backup copies of its records expire within 35 days. To close your account or ask us to delete other data, email support@myfeatureflow.com and we will reply within one month. Usage and billing records are kept separately for billing integrity and audit, for as long as tax and accounting law requires, and may keep a deleted project’s identifier. We delete a kept ad click reference and campaign name 6 months after sign-up, or sooner if your workspace owner erases them in Settings, or refuses cookies in a browser they then sign in with.
9. Your privacy rights
Depending on your jurisdiction, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. In the app you can update your profile, download your videos and delete projects; for anything else — including a copy of your data or closing your account — email support@myfeatureflow.com and we will reply within one month.
10. Cookies and browser storage
My Feature Flow sets no advertising or cross-site tracking cookies inside the signed-in app. On our public website, Microsoft Advertising's cookies are set only if you accept them (see “Microsoft Advertising measurement on our website” below). If you accept, we also keep the ad click reference and campaign name from your visit with your account, so we can tell which ads lead to sign-ups. We never keep your IP address with it. Sign-in sessions are kept in your browser's local storage by the authentication SDK rather than in cookies. The sign-up and sign-in forms run a Cloudflare security check, which processes technical information such as your IP address and browser details to stop bots and abuse. The contact form keeps a one-way code of your IP address briefly, only to limit abuse.
11. Microsoft Advertising measurement on our website
Our public website can use Microsoft Advertising's Universal Event Tracking (UET) tag to measure whether our ads on Bing and Microsoft's other sites work. If you arrive by clicking one of our Microsoft ads and then create an account, the tag records that a sign-up happened. To count each sign-up only once, this website keeps a small record in your browser's local storage. The sign-up event carries nothing else: we never send Microsoft your account ID, your email address, your name or anything from your workspace, and the tag never runs inside the signed-in app.
The tag only loads after you choose “Accept” on our cookie banner — the same choice as for any other advertising tag on this website. Until you choose, or if you choose “Reject”, it does not load and nothing is sent to Microsoft. You can change or withdraw your choice at any time with “Cookie settings” at the bottom of this page. We ask again after six months. Withdrawing stops the tag from then on; cookies it already set stay in your browser until they expire or you clear them.
When the tag runs, your browser sends Microsoft information such as the address of the page you're visiting and your IP address, and the tag sets or reads cookies. On this website: “_uetsid” (a visit, 1 day) and “_uetvid” (a returning browser, 390 days), plus “_uetmsclkid” (90 days, as Microsoft states) when you arrive from a Microsoft ad. On Microsoft's own sites: “MUID” (bing.com, 390 days) and “MR” (bat.bing.com, 7 days). Those lifetimes are what Microsoft's tag set when we checked on 20 October 2026; Microsoft lists the tag's cookies in its UET FAQ. Microsoft decides for itself how it uses that information, under the Microsoft Privacy Statement.
To control the ads Microsoft shows you, use Microsoft's ad settings. You can also block or delete cookies in your browser's settings.
12. Changes and contact
If this policy changes materially, we will notify account holders by email before the change takes effect. Privacy questions or requests can be sent to support@myfeatureflow.com or through the contact page and are routed to the team responsible for data protection.
