Legal ·

What happens to your video, told straight.

A privacy policy is usually written so that nothing in it can be held against the company. This one is written so you can find out what actually happens: which provider gets your audio, which gets your transcript, what never leaves our servers, and how long any of it survives.

01Who this is from, and what it covers

Cueits is operated by [full legal name — to be filled in], a sole proprietor in India, at [postal address — to be filled in]. We are the data fiduciary — the data controller, if you know the term from the GDPR — for everything described here.

This policy covers the Cueits app, this website, and the emails we send. It does not cover anything you do after you download your video: a platform you upload it to has its own policy, and we are not part of that.

02What we collect

Your account

  • Your name, email address, and a password stored only as a bcrypt hash — we cannot read it, which is why a forgotten one is reset rather than recovered.
  • If you use Sign in with Google instead: your name, email address and profile picture as Google provides them. No password exists in that case.
  • What you told us during onboarding — the kind of videos you make, and a preferred preset. Both are optional, both can be skipped, and nothing in the product behaves differently because of them.

What you make

  • The video file you upload, and any brand assets you add.
  • The transcript taken from it, including word-level timings, and the panel plan built from that transcript.
  • The finished render, and the settings that produced it.

Billing

Your plan, your credit balance, and a ledger of what each render cost, plus the customer reference our payment provider gives us. The payment itself, and your card, belong to them — see clause 3.

Technical

  • A session cookie so you stay signed in, and server logs containing your IP address, browser, and the requests you made. Logs are operational: they exist to find faults and abuse.
  • Product analytics through PostHog — pages viewed, actions taken, and an approximate location derived from your IP address. See clause 10.
  • A record of any upload refused by automated screening, and any strike on the account.

03What we never collect

  • Your card details.They are entered on our payment provider’s own checkout. They never reach our servers, and there is nowhere in our database for them to go.
  • Advertising identifiers, or any cross-site tracking. There are no ad pixels on this site or in the app.
  • Your contacts, your camera roll, or anything you did not hand us. Cueits sees the file you chose to upload and nothing else.

We do not sell personal data, and we do not share it for advertising. There is no version of this business where your video is the product.

04What we use it for

  • Making your video. Transcribing it, planning the panels, rendering, storing the result and letting you download it.
  • Running your account.Signing you in, showing your library, metering credits, applying your plan’s limits.
  • Billing. Taking payment through our provider, keeping the ledger straight, and issuing what tax law requires us to keep.
  • Safety. Screening uploads against prohibited content, and acting on abuse of the service.
  • Support. Answering your email, which sometimes means looking at the job you are asking about.
  • Improving the product. Aggregate analytics — which features are used, where people get stuck, how long renders take.

05Where your video actually goes

This is the part most people want, so it is stated plainly rather than as a category.

  • The audio trackof your video is sent to a speech-to-text provider to produce the transcript — OpenAI for animation videos, Google’s Gemini for caption videos. Audio only, never the picture.
  • The text transcript and your brief are sent to Anthropic to plan what the panel should say and when each part should appear. The video itself is never sent there.
  • The video file is stored with Cloudinary and rendered by our own render service. Nothing else receives the frames.
  • Content screening runs on our own servers, using a model that ships with the software. Your frames are not sent to a third-party moderation service to be checked.

We use these providers through their business APIs. We do not grant any of them permission to train models on your content, and we do not train models of our own on it either.

06Who else touches your data

The complete list. Each of these is bound by its own agreement with us, and each gets only what its job needs.

ProviderWhat forWhat they get
CloudinaryMedia storage and deliveryYour uploaded video, the finished render, and any brand-kit images
MongoDB AtlasThe database behind the productYour account, plans, credit ledger, transcripts and video records
OpenAISpeech-to-text for animation videosThe audio track of your video, and nothing else
Google (Gemini)Speech-to-text for caption videosThe audio track of your video, and nothing else
AnthropicPlanning the panels from what you saidThe text transcript and your brief — never the video or its frames
Google (Sign in with Google)Signing you in, if you choose that routeYour name, email address and profile picture
Dodo PaymentsPayments, as merchant of recordYour name, email, billing country and card details — held by them, never by us
ResendThe one email we send: a password reset linkYour email address
PostHogProduct and site analyticsPages viewed, actions taken, approximate location from IP address

If we add one, this table is updated in the same change. It is the list, not an example of the list.

07Why we are allowed to

Where the GDPR or the UK GDPR applies to you, these are our legal bases.

WhatBasis
Running your account and making your videosPerformance of our contract with you
Billing, invoices and tax recordsContract, and our legal obligations
Content screening, abuse prevention, security logsOur legitimate interest in a service that is not used to harm people
Product analyticsConsent where required, otherwise legitimate interest
Support correspondenceContract, and legitimate interest

Where India’s Digital Personal Data Protection Act, 2023 applies, we process your data on the basis of the consent you give when you create an account and upload a file, and for the legitimate uses that Act allows.

08How long anything is kept

WhatHow long
Your uploaded source videoDeleted 24 hours after the render finishes
Your finished videoYour plan's retention window — see the pricing page — then deleted
A video saved to your Assets libraryUntil you delete it, within your plan's limit on saved videos
Transcripts and panel plansWith the video they belong to, and removed with it
Your account recordUntil you delete the account, then 30 days, then purged
Billing and tax recordsUp to 8 years after the transaction, because Indian tax law requires it
Server logsRotated within 90 days

Deleting your account is reversible for 30 days and final after that. During the window nothing is destroyed and signing back in offers you a restore; once it closes, the account and its media are purged.

09Your rights over it

Wherever you live, you can ask us to do all of the following, and most of them you can simply do yourself in the app.

  • See it. Get a copy of the personal data we hold about you.
  • Correct it. Your name and email are editable on the account screen.
  • Delete it. Delete a video from your library, or the whole account from the account screen.
  • Take it with you. Ask for your data in a portable format.
  • Object, or withdraw consent. Including to analytics, which you can also refuse in your browser.
  • Nominate someone.Under India’s DPDP Act you may nominate a person to exercise these rights if you cannot.

Write to [email protected] from the address on the account. We answer within 30 days, and it is free. If you are in the EU or the UK you can also complain to your local supervisory authority; in India, to the Data Protection Board once our grievance process has had its turn.

10Cookies, and what is stored in your browser

  • A session cookie, set when you sign in. Strictly necessary: without it there is no way to stay signed in. It is HttpOnly and cannot be read by scripts.
  • Your theme choice, kept in local storage so the site does not flash the wrong scheme on the next visit. It never leaves your browser.
  • Analytics cookies set by PostHog, which count a visit as one visit rather than several. These are the only non-essential ones.

Blocking cookies in your browser stops the analytics; blocking the session cookie stops sign-in from working at all, which is a limitation of how sessions work rather than a choice we made.

11How it is protected

  • Everything travels over HTTPS, between you and us and onward.
  • Passwords are stored as bcrypt hashes. A breach of our database would not hand anyone your password.
  • Media URLs are unguessable, and access to the database and storage is restricted to the people who operate the service.
  • Card data is out of scope entirely, because it never arrives.

No service is perfectly secure, and anyone who tells you otherwise is selling something. If a breach affects your data we will tell you and the relevant authority as the law requires, and we will tell you what actually happened rather than a sanitised version of it.

12Children

Cueits is not for anyone under 18. We do not knowingly collect data from children, and an account we find belongs to one is closed and its data deleted. If you believe a child has given us data, write to [email protected] and we will act on it.

13Where in the world it is

Cueits is operated from India, and the providers in clause 6 store and process data in the United States and the European Union. Using the service means your data crosses borders. Where the GDPR applies, those transfers rely on the European Commission’s Standard Contractual Clauses or an adequacy decision, depending on the provider.

14Changes to this policy

This version takes effect on 10 September 2026. When it changes, the date at the top of the page changes with it. For a change that materially affects how we handle your data — a new category collected, a new purpose, a new provider with real access — we will tell you by email or in the app before it takes effect.

15Contact, and complaints

Privacy questions, data requests and grievances all go to one place. Under India’s DPDP Act the operator named below is the person responsible for answering them.

[full legal name — to be filled in]
[postal address — to be filled in]
[email protected]

Read alongside the Terms of Service, which covers the agreement itself, and the Refund and Cancellation Policy.