Your video is yours. Full stop.

Last updated: 11 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 (Supabase) — your email and login metadata (including Google profile name/photo if you sign in with Google), to sign you in. Stored with Supabase (our auth/database provider).
Captions — speech-to-text (ElevenLabs, Deepgram)— when you click "Generate captions", the audio of the selected layer(never the video) is sent securely to ElevenLabs 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 is sent to Deepgram instead. We don't store your audio; the caption text lives in your browser, not on our servers.
AI features (OpenRouter/OpenAI) — 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 (Razorpay) — handled by Razorpay; we never see or store your card/UPI details, only the order and its status.
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.
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 PostHog to understand which features get used and Sentry to catch errors. No ad tracking, no data selling, no cross-site profiling. (Not yet active; ships behind the consent banner.)

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.

Your rights

You can withdraw analytics consent anytime (clearing site data resets the banner). Once accounts launch: you can export your data and delete your account, which purges our copies of your data (usage records we're legally required to keep for accounting are retained only as long as required). We honor rights under India's DPDP Act, 2023 and apply the same standard globally.

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 (Supabase) — your email and login metadata (including Google profile name/photo if you sign in with Google), to sign you in. Stored with Supabase (our auth/database provider).

Captions — speech-to-text (ElevenLabs, Deepgram)— when you click "Generate captions", the audio of the selected layer(never the video) is sent securely to ElevenLabs 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 is sent to Deepgram instead. We don't store your audio; the caption text lives in your browser, not on our servers.

AI features (OpenRouter/OpenAI) — 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 (Razorpay) — handled by Razorpay; we never see or store your card/UPI details, only the order and its status.

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.

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 PostHog to understand which features get used and Sentry to catch errors. No ad tracking, no data selling, no cross-site profiling. (Not yet active; ships behind the consent banner.)

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.

Your rights