Privacy policy

Your account. When you sign in with Google, our sign-in provider Supabase passes us your email address, name and profile picture. We keep your email address and a user id, and use them to find your workspace and to contact you about the service.

Your workspace — on your computer. The scripts, prompts, scene plans, cast and library entries, job history, thumbnails and settings you create live on your own computer, in the agent's folder. Our server does not store them. When you open the studio away from that computer, our server passes your requests to it and its answers back to you, encrypted between our server and your computer, and keeps nothing of what passes through.

Workspaces created before this design were kept on our server. Each one moves by itself to the first of its owner's computers whose agent connects (or to the one chosen with Move workspace here on the account page), and is then deleted from our server. Our server no longer runs any workspace; a copy that is never claimed is deleted with the rest of the account's data, as below.

Billing. Payments are taken by a payment provider — Razorpay in India, Dodo Payments elsewhere — which handles your card, UPI or wallet details under its own privacy policy; we never see or store card numbers. For each payment we keep a record of the provider, its payment and order ids, the plan, the amount, the currency, the date and the period it paid for, linked to your account. It is kept on our server and in our sign-in provider (Supabase) as your transaction history, and stays for as long as tax and accounting law requires, even after your account is deleted. Payments are final; see the terms.

A fingerprint of each provider account you connect. When you connect a VideoExpress or Higgsfield account, our server keeps a one-way hash (SHA-256) of that account's email address — not the address itself, and never the password — tied to your workspace. It is used for one thing: the same provider account cannot be connected to a second Imanginable workspace, which is how we keep the free trial to one per person. It cannot be turned back into the address, and it is removed when you delete your account.

Technical records. Server logs (IP address, requested address, time) and an audit trail of security-relevant events in your workspace, such as sign-ins, computers paired or removed, a workspace moved and plan changes. We keep them to run and protect the service. We do not log what your requests contain.

Reports you send. When you report a problem or suggest an idea, we keep what you write, your email address, the screen you were on and your versions, any screenshots you add and, if you leave it ticked, the diagnostic logs (passwords, keys and tokens are removed before they leave your browser). Only you and our team can read them, and you can delete one yourself from the account page.

Client requests. If you take requests for videos from clients, the request page keeps what each client sends you — their name, email address, what they ask for, the files they attach and your messages — on Cloudflare, for you to read and answer. Only you and the client can see a request. A delivered file is kept for 14 days; the request itself is kept until you delete your account, when it goes with it. If you send a request, the creator you send it to receives it.

How you use the service. To see what works and where people get stuck, we record how the website and studio are used: the screens you open, what you click, scroll and type into ordinary fields (password and key fields are masked), and a replay of the session, through Microsoft Clarity and Google Analytics — Clarity only if you allow it. Clarity is then told your email address so we can find a session when you report a problem; Google Analytics gets only an anonymous user id. For AI assistants (MCP) and the agent, our server records, with your email address, which tool or event it was, which assistant or computer made it, whether it worked and how long it took — never its arguments, prompts or results. The same names (not your email) also go to Google Analytics, with the same anonymous user id, so we can see which features are used from the studio and which from assistants.

The studio runs through the agent, a program you install on your own computer. It keeps your workspace there and does the work there, so your data does not rest on our servers:

• Video and audio files are downloaded to, processed on and kept on your computer.
• Your provider accounts — your VideoExpress login, your Higgsfield sign-in and any API keys you add (OpenAI, the video reviewer, image search) — are stored encrypted on your computer by the agent, never on our disks or database. A remembered VideoExpress password lives in the agent's vault (%LOCALAPPDATA%\Imanginable\secrets on Windows,~/Library/Application Support/Imanginable/secrets on macOS,~/.local/share/imanginable/secrets on Linux), encrypted with your workspace's key; your studio holds it in memory only while it runs.
• Calls to those services (generating pictures, clips and voices, writing scripts, searching for images) are made from your computer, so the services see your own connection, not our server.
• Your YouTube connection is stored on your computer by the agent, and uploads go from your computer straight to your channel.

If you remove the agent's data from your computer, those connections are gone. You can connect them again at any time.

We use your information to provide the service you signed up for, keep it secure, bill you and tell you about changes that affect your account. We do not sell personal data. We do not use it for advertising. We do not use your scripts, prompts or videos to train AI models. We share it only with the service providers listed below, and only as far as each one needs.

• Supabase: sign-in with Google, user identity, and your payment history.
• Google: sign-in, and YouTube if you connect a channel.
• Cloudflare: our DNS and the landing page; keeps the problem reports and ideas you send us, with their screenshots and logs; serves agent downloads and updates and the studio's news file (dl.imanginable.com), so it sees the IP address of a computer fetching them; and carries the traffic between an AI assistant you connect and your computer (mcp.imanginable.com), without keeping it.
• Razorpay: payments in India, in rupees.
• Dodo Payments: payments everywhere else, in US dollars. Dodo is the merchant of record for those payments: it charges you, collects any sales tax or VAT and invoices you, under its own privacy policy.
• Microsoft Clarity: how the website and studio are used, including session replays, linked to your email address.
• Google Analytics (Firebase): usage statistics — screens, clicks, and the names of assistant and agent actions — with an anonymous user id, never your email.
• Oracle Cloud: hosting of our sign-in, account and relay server, in India (Hyderabad). It holds workspaces only for customers who have not yet moved theirs to their computer.
• The generation providers you connect — VideoExpress, Higgsfield, Kling, Runway, Google (Gemini), ElevenLabs, Suno — with your own accounts or keys, which the studio uses from your computer, on your instruction, to generate pictures, clips, voices and music. They receive the prompts, scripts, pictures and voice samples you send them. What you send them is governed by their own terms and privacy policies.
• OpenAI: only if you add your own OpenAI API key in Settings. That key is kept on your computer, and every call goes from your computer under your own OpenAI account. It sends the text of prompts and scripts you ask the studio to write or improve. If you also use Insights (Virally), it reads your own channel's videos: their titles, descriptions and words, stills taken from them, their audio (to transcribe it when there are no captions), their thumbnails, and the text of their comments. Each video is read once and the result is kept on your computer. You can switch the picture reading off on the Insights screen, and nothing is read without a key. Credentials are never sent.
• Image search (Brave, Google, Pexels): only if you add your own key; the studio sends them the words you search for, from your computer.
• The AI assistant you connect (for example Claude or ChatGPT): it receives what it reads from your workspace when you ask it to, under its own terms.
• GitHub: a second copy of agent downloads, used only if the first cannot be reached; it sees the IP address of a computer fetching one.

Our server is in India. Several of the services above — Supabase, Cloudflare, Microsoft Clarity, Google Analytics, Dodo Payments and the providers you connect — may process data in other countries, including the United States and the European Union. We use only providers that commit to protect it, through their data-processing terms and, for data from the EEA, the UK or Switzerland, the European Commission's standard contractual clauses or an adequacy decision.

• To provide the service you asked for (a contract with you): your account, your plan, payments, pairing your computers, passing the studio's requests to them, and the reports you send.
• Because you agreed (consent, which you can withdraw at any time): analytics cookies and session replays, connecting YouTube and other providers, and reading your channel with your OpenAI key.
• Because the law requires it: payment and tax records, and security logs.
• To keep the service safe and fair (legitimate interests): the audit trail, the record that keeps the free trial to one per person, and counting which assistant tools are used.

Imanginable's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google sign-in data only to identify you. We use YouTube access only for the actions you ask for, such as uploading a video you chose to publish to the channel you selected, and never for advertising. People do not read this data, except with your permission, for security or to comply with the law.

The YouTube features use YouTube API Services. By connecting a channel you agree to the YouTube Terms of Service, and Google handles your data under the Google Privacy Policy.

When you connect a YouTube channel, Imanginable asks Google for these permissions:

• youtube.upload: to upload the videos you choose to publish, with their title, description and thumbnail. Nothing is ever published without you pressing Upload.
• youtube.readonly: to list your channel's own videos, their details and view counts, and whether an upload has finished processing.
• youtube.force-ssl: to read the comments on your own videos and their captions, and to post the replies you write.
• yt-analytics.readonly: to read your own channel's analytics (views, watch time, subscribers, impressions, retention and traffic sources).

This data is about your own channel only. It is stored on your computer, in your workspace, and is used only to show it to you and to do what you ask. It is not shared with anyone, with one exception you choose: if you add your own OpenAI key, your videos' words, stills, audio, thumbnails and comment text are sent from your computer to OpenAI under your account to read them for Insights (see above). Other people never see it, and we never receive it. Scores, patterns and predictions the studio shows (for example “3× your usual”) are calculated by Imanginable from your channel's numbers and are not YouTube metrics.

Comments are written by other people, and their names and words are their personal data: the studio reads them only to show you your inbox and what your viewers ask for, shows their names only while you read them, keeps only the text, and never builds a record of any commenter. The text of your videos' captions and of the comments read from YouTube is kept for no longer than 30 days; after that only the numbers measured from it remain. Your channel's statistics are kept while the channel stays connected, and Imanginable checks at least every 30 days that it still has your permission.

You can take back this access at any time on Google's security settings page, or remove the channel in Imanginable's Settings. Removing the channel, or taking back the access, deletes the stored connection and all the YouTube data kept for that channel from your computer.

A workspace on your computer is yours to keep or delete; we hold no copy. We keep your account (email, plan, paired computers) while your trial or subscription is active, and for 90 days after it ends so you can come back. A workspace still on our server is deleted 90 days after your plan ends, or as soon as you move it to your computer.

You can delete your account yourself at any time from the account page, and we remove it straight away: your email address, sign-in, workspace on our server, paired computers, provider fingerprints, audit trail and record of assistant use, invite code, leaderboard name, and the reports, ideas and client requests you sent or received. We keep only what we must or what stops abuse: the payment records (tax law), a one-way hash of your email address that says a free trial was used, and which invites were rewarded (by account number, without your name or email). What Clarity and Google Analytics recorded is deleted on their own schedules (Clarity keeps recordings for at most 30 days). The audit trail of an account that is not deleted is kept for 180 days. Server logs are kept for 180 days, as Indian law (CERT-In) requires, and then deleted; our record of assistant and agent use is also kept for up to 180 days.

On the account page you can see your account details, remove any paired computer or AI-assistant access, and delete everything. The first time you visit we ask whether Clarity and Google Analytics may set cookies. Until you say yes, Clarity does not run at all (no recording of your session) and Google Analytics counts visits without cookies or any id; neither is told who you are. You can change your answer at any time: Cookie choices.

You have the right to:

• get a summary of the personal data we hold about you and who we shared it with;
• have it corrected, completed or brought up to date;
• have it erased, unless the law makes us keep it (such as payment records);
• withdraw any consent you gave, as easily as you gave it, for what comes after;
• object to a use based on our legitimate interests, and ask for your data in a portable form (in the EEA and the UK);
• name someone to act on these rights for you if you die or can no longer act yourself (in India);
• have your complaints answered.

Grievance officer. Kiran Benny Joseph, reachable at imanginable@googlegroups.com. Write there for any of the rights above, a complaint, or anything else about your data. We acknowledge a complaint within 48 hours and answer it within one month. If you are not satisfied, you can complain to your data-protection authority: in India the Data Protection Board of India; in the EEA or the UK the authority where you live or work.

All traffic to the service is encrypted with TLS, and the studio's traffic to your computer is encrypted again to a certificate made on your computer, which our server checks. Each computer you pair signs in with its own device token, which you approve and can revoke. No system is perfectly secure. If we learn of a breach that affects you, we will tell you without undue delay — what happened, what it may mean for you and what we are doing — and report it to the authorities the law names, such as the Data Protection Board of India and CERT-In.

The service is for adults. It is not meant for anyone under 18, and we do not knowingly collect data from children. If you believe a child has created an account, contact us and we will delete it.

If we change this policy in a way that matters, we will show a notice in the studio before the change takes effect. The date at the top shows when the current version was published.