Privacy Policy

Account details: your name, email address and the organisation you belong to. These come from Clerk, who handle sign-in for us.

Billing details: your plan, your invoices and your payment status. Payments are processed by Stripe. We never see or store your card number.

Your content: the images, video, audio, 3D files and prompts you upload or generate, and the projects they sit in.

Usage records: what you generated, which model was used, when, what it cost, and whether it succeeded. This is how billing and the provenance record work.

Support conversations, if you use the chat widget or email us.

To run the service you asked for: making the thing you asked us to make, and showing it back to you.

To bill you accurately, and to show you where your credits went.

To keep the provenance record, which exists so you can show how a piece of work was made.

To keep the service working and secure — diagnosing failures, preventing abuse, and investigating anything that looks wrong.

To answer you when you get in touch.

We do not use your material to train our own models. That covers what you upload and what you generate — your inputs, your prompts and your outputs alike. We do not sell it or share it for advertising, and we do not pass it to anyone else to train on.

When you train a custom model, that happens only on material you deliberately upload for the purpose, and the result is available only to your organisation.

To run the service we pass data to the companies below. Each one only receives what it needs for its job.

Model providers receive the content of a request — your prompt and any reference material — at the moment you ask for a generation. Which provider receives it depends on the model you choose.

Which third parties receive a request depends on the model you pick, and the list changes as models are added and retired. The current list is shown in the app wherever you choose a model, and includes providers for image, video, voice and 3D generation.

One 3D capability is provided under our own name using an upstream supplier.

If you supply your own API key for a provider, that provider bills you directly and processes your data under your own agreement with them, not ours.

While your account is active we keep your content so you can use it. You can delete a project or an individual file at any time, and doing so removes it from the service.

Plans describe an asset retention window — 30 days on the free plan, and no fixed limit on the paid plans.

BEING PRECISE ABOUT THIS, BECAUSE IT MATTERS: that window describes what your plan entitles you to and what we may do. There is no scheduled process today that deletes your project content when a plan window expires. If you need something gone, delete it, or ask us and we will.

Separately, some temporary files — export archives and similar — do carry their own expiry and are deleted automatically by a scheduled job when they lapse. Deleted files are removed from storage shortly afterwards rather than instantly.

Account and billing records are kept for as long as the law requires us to keep them, which is longer than your content.

Cancelling stops future billing. Your content is not deleted at the moment you cancel.

If you want your material removed when you leave, email us and we will do it.

You can ask us for a copy of the personal data we hold about you, ask us to correct it, or ask us to delete it. You can also object to some uses of it.

Email info@vfxlosangeles.com and we will deal with it.

Depending on where you live you may have further rights over your personal data. We will honour any that apply to you.

Our suppliers operate internationally, so your data may be processed outside the country you are in.

Where we transfer personal data across borders we do so under the safeguards the applicable law requires.

We use cookies that are necessary to sign you in and keep you signed in. We do not use advertising cookies, and the app has no analytics or tracking service.

Our support chat is provided by Crisp and loads on every page, including before you sign in. It sets its own cookies so it can recognise a returning conversation.

Your projects, assets and generations are scoped to your organisation and are not visible to other customers.

Two exceptions, stated rather than glossed. Our support and engineering staff can access account data where it is necessary to investigate a fault or abuse. And anything you post to the community forum is public to every signed-in customer by design.

Voices you train are built on our own infrastructure and belong to your organisation like any other model.

Any provider keys you add are stored encrypted and are not shown back to you in full.

No service is perfectly secure. If something happens that affects your data, we will tell you.

We may update this policy. The date at the top tells you when it last changed, and we will tell you about anything significant.