Your video is yours. Full stop.

Last updated: 13 July 2026 · version 2026-07-11

The short version

Your footage and projects live on your device (browser storage), not on our servers. Exports render on your device too — the video is never uploaded.
We never use your content to train AI models. Not ours, not anyone's.
Analytics run only if you click "Allow" on the consent banner. Saying no changes nothing about how the product works.
When a feature needs to send data somewhere (e.g. transcription), we say exactly what goes where, below.

What we collect today

Account — your email and login metadata (including Google profile name/photo if you sign in with Google), to sign you in. Stored with our authentication and database provider.
Captions — speech-to-text— when you click "Generate captions", the audio of the selected layer(never the video) is sent securely to our speech-recognition partner to be transcribed, and the transcript is returned to your device. If the result comes back in the wrong script and you approve a retry, the same audio goes to a second recognition engine instead. We don't store your audio; the caption text lives in your browser, not on our servers.
AI features — when you run Auto Trim, Roman transliteration or caption translation, the text transcript (never the video or audio) is sent to a language-model provider and the result is returned to your device.
Usage meters & service logs — to enforce plan limits, bill honestly and debug failures, we record per request: transcription duration (seconds), language codes, word counts, AI tokens and provider-reported cost, latency, success/error status and provider error messages — tied to your account id. These logs contain no audio, no video and no caption text.
Payments — INR payments are handled by Razorpay; international (USD) payments are handled by Dodo Payments as Merchant of Record. We never see or store your card/UPI details — only the order, plan and its status. Payment processors receive the data they need to process the transaction (e-mail, amount, country) under their own privacy policies.
Devices— to enforce your plan's device limit we keep a small registry per account: a random device id (stored in your browser — no fingerprinting), a label like "Chrome · Windows", and first/last-seen times. You can see and remove devices anytime in Account → Devices. Clearing site data simply counts as a new device.
Fonts— Google Fonts load from Google's servers when you pick them (Google's standard font CDN; no account data is sent). Custom fonts you upload are stored only on your device (browser storage) — we never receive or host your font files.
Onboarding profile— when you first open the app we ask your date of birth, gender, what describes you (e.g. editor, creator), and optionally where you found us and what you'll caption. This is used to understand who we're building for and to improve the product — never for ads, never shared. Stored against your account; deleted with it.
Font favorites — fonts you star are saved to your account so they sync across devices (just the font names, nothing else).
Site notifications— when we show a site-wide announcement banner (maintenance, offers, terms updates) we keep a timestamped record of the announcement itself and of when it was dismissed (tied to your account if you're signed in) — our audit trail that a notice was given.
Consent choice— your Allow/Deny decision is stored in your browser (and alongside your account) so we don't re-ask.
Anonymous analytics (only after you Allow) — we use Google Analytics 4 (with IP anonymisation) to understand which pages and features get used. It loads ONLY after you press Allow on the consent banner. No ad tracking, no data selling, no cross-site profiling.

What may be collected as features launch

Each of these ships together with an update to this policy (the "Last updated" date and version will change, and you'll be re-asked for consent where required):

Cloud exports (Cloudflare R2) — today every export renders entirely on your device. If a cloud export feature launches, the video would be uploaded to our storage temporarily and auto-deleted after processing — and this policy will say so first.

What we will never do

Train AI models on your videos, audio, or transcripts.
Sell or share your personal data with advertisers.
Run analytics or tracking before you consent.
Say one thing here and do another in the product.

International transfers & legal bases

We are based in India; our processors (hosting, database, speech recognition, language models, analytics, payments) may process data in the US, EU or India under their own compliance programs (including standard contractual clauses where applicable). Where GDPR applies, our legal bases are: contract (providing the service you signed up for — accounts, captions, billing), legitimate interest (security, rate-limiting, fraud prevention, service logs) and consent (analytics, which never loads before you press Allow).

Your rights

You can withdraw analytics consent anytime (clearing site data resets the banner). You can request access to, correction of, export of, or deletion of your personal data by writing to support@fluxocut.comfrom your account e-mail — we act on verified requests within 30 days. Deleting your account purges our copies of your data; records we are legally required to keep (payments/tax) are retained only as long as required. We honor rights under India's DPDP Act 2023, the EU/UK GDPR (including the right to lodge a complaint with your supervisory authority) and the CCPA — and we apply the same standard globally. We do not sell personal data, and we do not knowingly collect data from children under 13.

Contact

Questions or requests: privacy@fluxocut.com. We reply to every mail.

The short version

Your footage and projects live on your device (browser storage), not on our servers. Exports render on your device too — the video is never uploaded.

We never use your content to train AI models. Not ours, not anyone's.

Analytics run only if you click "Allow" on the consent banner. Saying no changes nothing about how the product works.

When a feature needs to send data somewhere (e.g. transcription), we say exactly what goes where, below.

What we collect today

Account — your email and login metadata (including Google profile name/photo if you sign in with Google), to sign you in. Stored with our authentication and database provider.

Captions — speech-to-text— when you click "Generate captions", the audio of the selected layer(never the video) is sent securely to our speech-recognition partner to be transcribed, and the transcript is returned to your device. If the result comes back in the wrong script and you approve a retry, the same audio goes to a second recognition engine instead. We don't store your audio; the caption text lives in your browser, not on our servers.

AI features — when you run Auto Trim, Roman transliteration or caption translation, the text transcript (never the video or audio) is sent to a language-model provider and the result is returned to your device.

Usage meters & service logs — to enforce plan limits, bill honestly and debug failures, we record per request: transcription duration (seconds), language codes, word counts, AI tokens and provider-reported cost, latency, success/error status and provider error messages — tied to your account id. These logs contain no audio, no video and no caption text.

Payments — INR payments are handled by Razorpay; international (USD) payments are handled by Dodo Payments as Merchant of Record. We never see or store your card/UPI details — only the order, plan and its status. Payment processors receive the data they need to process the transaction (e-mail, amount, country) under their own privacy policies.

Devices— to enforce your plan's device limit we keep a small registry per account: a random device id (stored in your browser — no fingerprinting), a label like "Chrome · Windows", and first/last-seen times. You can see and remove devices anytime in Account → Devices. Clearing site data simply counts as a new device.

Fonts— Google Fonts load from Google's servers when you pick them (Google's standard font CDN; no account data is sent). Custom fonts you upload are stored only on your device (browser storage) — we never receive or host your font files.

Onboarding profile— when you first open the app we ask your date of birth, gender, what describes you (e.g. editor, creator), and optionally where you found us and what you'll caption. This is used to understand who we're building for and to improve the product — never for ads, never shared. Stored against your account; deleted with it.

Font favorites — fonts you star are saved to your account so they sync across devices (just the font names, nothing else).

Site notifications— when we show a site-wide announcement banner (maintenance, offers, terms updates) we keep a timestamped record of the announcement itself and of when it was dismissed (tied to your account if you're signed in) — our audit trail that a notice was given.

Consent choice— your Allow/Deny decision is stored in your browser (and alongside your account) so we don't re-ask.

Anonymous analytics (only after you Allow) — we use Google Analytics 4 (with IP anonymisation) to understand which pages and features get used. It loads ONLY after you press Allow on the consent banner. No ad tracking, no data selling, no cross-site profiling.

What may be collected as features launch

Each of these ships together with an update to this policy (the "Last updated" date and version will change, and you'll be re-asked for consent where required):

Cloud exports (Cloudflare R2) — today every export renders entirely on your device. If a cloud export feature launches, the video would be uploaded to our storage temporarily and auto-deleted after processing — and this policy will say so first.

International transfers & legal bases

Your rights