Privacy Policy

NeoMotion Studio (“NeoMotion”, “we”, “us”) makes an AI motion-graphics editor. This policy covers two things:

• This website — neomotion.net, including your account, licence, checkout, support and email.
• The NeoMotion desktop app — the parts of it that talk to us. That is sign-in and licence activation, plus, only if you switch it on, the Cloud Link relay that lets a web chat drive the app.

For the data described here, NeoMotion Studio is the data controller. If you want to reach a person about any of it, write to privacy@neomotion.net.

Account data

Your name and email address, and — if you sign up with a password — a hashed version of that password. We never store the password itself. If you sign in with Google or GitHub instead, we receive your name, email address and avatar from that provider; we never receive your password for it. We also store whether your email has been verified, and short-lived tokens used for verification, password resets and sign-in links.

Licence and activation data

Your licence key, the plan it belongs to, its status, and the payment reference it was issued against. When you activate a device, we store a SHA-256 hash of that device's id — not the id itself — plus an optional device label you can set (e.g. “Adi's MacBook”) and the time the device was last seen. That is how a two-device licence knows it is on two devices. It is not a location, and it does not tell us what you did in the app.

Payment data

Checkout runs through PayPal. Your card or PayPal credentials go to PayPal, never to us. We receive and store the transaction reference, the plan, the amount, and the status — enough to issue your licence, show you an invoice, and honour a refund.

Things you send us

Support tickets, newsletter or waitlist subscriptions, and any email you write to us, including whatever you choose to put in them.

Technical data

Ordinary server logs, and your IP address at the moment you submit a public form. We use the IP for rate limiting and abuse prevention — stopping a bot from burning our email budget — not to build a profile of you.

This is the part worth reading twice, because it is the opposite of how most AI video tools work.

• Your projects, footage, audio, images and renders. NeoMotion is a desktop app. Your media sits on your own disk, and rendering happens on your own machine. We have no upload endpoint for it and no copy of it.
• Your prompts and your timeline. What you asked the agent for, and what it built, stays on your machine.
• Your AI provider keys. They are stored locally by the app, in your operating system's own storage. We never receive them, which is also why we cannot mark up your AI usage.

We do not, and cannot, use your work to train any model — ours or anyone else's. There is nothing to train it on.

One honest exception, and it is yours to switch on: Cloud Link routes traffic between a web chat and your desktop through a relay we run. It is off unless you turn it on, and it is described in full below.

A growing amount of what NeoMotion does needs no cloud service at all. Transcription and voiceover run on your own machine — a local Whisper model for English speech, and local voices for narration, including the one that clones a voice from a reference recording. That material never leaves your computer, not to us and not to anyone else. If you drive the app from your own AI agent, the whole core production chain can run without a single key configured.

Where you do add a key — Replicate for generated imagery and cutouts, OpenAI for the built-in director or non-English transcription — the app sends the relevant material directly from your machine to that provider, billed to your account at their price. It does not pass through our servers and we never see it, which also means that provider's own privacy policy governs that traffic rather than ours.

Voice cloning deserves its own line: the reference recording, the model and the generated audio all stay local, but the responsibility does not disappear with the upload. Clone your own voice, or one whose owner has agreed — in many places that consent is a legal requirement, not a courtesy.

A chat running on claude.ai or ChatGPT cannot reach a server on your own machine; its connectors run on the vendor's infrastructure. So if you want to drive NeoMotion from a web chat, something has to carry the traffic between them, and Cloud Link is that something: a relay we operate, which you switch on in the app and authorise by signing in here and clicking approve.

What that means in practice, said plainly:

• It is off until you turn it on, it needs your explicit approval on this website, and it stops the moment you close the app or switch it off. Everything on this page other than this section describes the app with Cloud Link off.
• What passes through is the conversation between the agent and the app — the instructions it sends and the answers the app returns, which can include a preview frame the agent asked to look at. Your media library, your project files and your renders are not sent through it; they stay on your disk.
• The relay forwards, it does not keep. It holds no store of your traffic — the only thing it persists is a timer for when your connection token expires.
• The web chat is a third party. Once you connect one, whatever it can see through the connection is also governed by that vendor's privacy policy — Anthropic's or OpenAI's — not only ours.

The alternative, if you would rather nothing of ours sat in the middle, is to use an agent that runs on your own machine — Claude Desktop, Claude Code, Cursor and other local clients connect straight to the app over loopback, with no relay involved.

• To run your account and licence — signing you in, starting your 14-day trial, activating your devices, sending your licence key. Necessary to perform our contract with you.
• To take payment and meet our tax and accounting duties — contract, and legal obligation.
• To answer you when you write to support. Contract, and our legitimate interest in running a supportable product.
• To keep the service standing up — rate limiting, fraud and abuse prevention, security logging. Our legitimate interest, and yours.
• To send you product email — release notes and news, only if you asked for them. Consent, withdrawable at any time from the unsubscribe link in every message.
• To understand how the site performs in aggregate, so we know which pages are broken or unread.

We do not sell your personal data, we do not share it with advertisers, and we do not run behavioural ad tracking on this site.

Only the service providers it takes to run the product, and only the minimum each one needs:

• PayPal — payment processing and invoicing.
• Resend and Mailketing — transactional email (licence keys, verification, password resets) and, if you subscribed, the newsletter.
• Vercel — website hosting and delivery.
• Cloudflare — the Cloud Link relay, but only while you have switched it on.
• Our managed database and storage providers — where your account and licence records live, and where the images on this site are served from.
• Product analytics — where enabled, event-level analytics about how the site and funnel are used. It runs server-side and never carries your licence key.

We will also disclose data if the law genuinely requires it, or to establish or defend a legal claim. If NeoMotion is ever acquired, account and licence records would transfer with it; you would be told before that happens.

We use the cookies it takes to keep you signed in and to remember your language, and no advertising cookies at all. The full list, and how to control them, is in the Cookie Policy.

• Account data — for as long as your account exists, then deleted or anonymised.
• Licence and activation records — for as long as the licence is valid. A lifetime licence is, by definition, kept for as long as we can honour it. Device activations are released when you deactivate a device.
• Payment and invoice records — for as long as tax and accounting law requires us to keep them, typically several years, even after you close your account.
• Support email — kept while it is useful for context, then cleared.
• Newsletter subscriptions — until you unsubscribe.
• Server and security logs — a short rolling window, then rotated out.

You can ask us to:

• give you a copy of the personal data we hold about you;
• correct anything that is wrong;
• delete your account and the data attached to it;
• stop sending you marketing email — or just click unsubscribe;
• restrict or object to a particular use;
• export your data in a portable format.

Write to privacy@neomotion.net from the address on your account and we will act within 30 days. There is no charge. Deleting your account also ends any active licence on it — including a lifetime one — so tell us if you would rather transfer it than lose it.

Depending on where you live, you may also have the right to complain to your national data protection authority. We would rather you told us first.

Passwords are hashed, never stored in readable form. Traffic to this site is encrypted in transit. Device ids are hashed before storage. Licence keys are treated as secrets and are never included in analytics events. Access to production data is limited to the people who need it to operate the service.

No system is perfect. If you believe you have found a vulnerability, write to privacy@neomotion.net and we will take it seriously and credit you if you want the credit.

NeoMotion is run from Indonesia, and the providers listed above operate globally — so your data may be processed in countries other than your own, including the United States and the European Union. Where a transfer leaves a jurisdiction with data-transfer rules, we rely on the safeguards our providers put in place, such as standard contractual clauses.

NeoMotion is a professional tool and is not directed at children. We do not knowingly collect personal data from anyone under 16. If you believe a child has given us data, write to privacy@neomotion.net and we will remove it.

When this policy changes we update the date at the top of the page. If a change materially affects how we handle your data, we will tell account holders by email before it takes effect, rather than quietly editing the page.

Privacy questions, data requests, and anything else on this page: privacy@neomotion.net.

For product help, the support page is faster.