Ownership and privacy.

Your organization does. What is made in an organization belongs to that organization, and we assign to it any rights that come to us. You can use it commercially and hand it to a client. There is no separate license to buy: this page is about who owns the work, who sees it and where it goes.

Your scripts, pictures and clips stay yours. We use them only to make what you ask for.

We never train AI models on your work.

To make a picture or a render we send your prompts and reference files to the AI companies listed below, through their paid business services. Each one's terms say it does not use that material to train its generative models unless we opt in, and we have not opted in.

They may keep copies for a time to check for abuse, and longer for what their own safety checks flag. As each published it on 8 October 2026: OpenAI: Up to 30 days, to check for abuse. Longer only where the law requires it. Anthropic: Up to 30 days. What its safety checks flag: up to 2 years, and the scores those checks give up to 7 years. Google: 55 days, to check for abuse. It may use what it logs for those checks to improve the checks themselves. BytePlus: What its safety filter flags: 180 days. A face registered with it stays until it is removed (we remove it when the organization or the person is deleted). TypeSafe: As long as it needs to run its service. It says it does not train on what it is sent. Tencent Cloud: The clip, while it is upscaled.

An AI assistant you connect yourself, such as Claude or ChatGPT, is under your own agreement with its maker, not ours.

The people you invite, by the role you give each of them.

Owners and managers can open every project in the organization. Members and viewers can open the projects they are given, and their own loose work. A role decides what each person may change, generate or spend. A freelancer added as a Member to one project sees that one.

Story Atlas staff see who is on the team, counts, money, timings and error codes, never scripts, boards, prompts or files. Two exceptions: a request our safety check blocks, which a person reviews, and a file named in a report or a legal notice, which a person may open to decide whether it must be removed.

Both exceptions are there to keep the service lawful. An automated check reads a prompt before anything is made, and a request it stops as sexual content involving anyone under 18 is kept and read by us. And when someone reports a file or sends a legal notice about it, the person who decides may open that one file; each time is written in your security record. Nothing else you write or make is seen this way.

The owner can let support in for 24 hours: support then also sees the names of the projects and how many sequences each has, not what is in them. For a legal or safety case Story Atlas can give itself that same view for four hours without asking, and it is written in the security record as “Emergency access by Story Atlas”. The owner can take support's access back at any time, and letting support in is recorded too.

Yes. Upload pictures of the product, or of a person who has given permission, and call them by name in a shot like any other asset.

Video models refuse faces they take for a real person. We register the ones you have the right to use with the video model, at no charge, so yours are not refused.

Save to device gives you the original file of any picture or clip, at any time. Your library stays online for as long as your organization exists.

If we ever close the service, we will tell every customer in good time to save their work first.

People sign in with Google or with a code sent to their email; there are no passwords to leak. An owner can require two-factor sign-in for everyone, sign a person out everywhere, and remove them at once.

Sign-ins, failed attempts, invites, role changes and AI connections are kept in a security record you can search and export.