Privacy

Your account and work

Neon stores account details, password hashes, sessions, drafts, generation settings, and task history. Your Kie API key is encrypted before storage. The browser receives only its last four characters after connection. The server decrypts it when contacting Kie for your uploads and generations.

Media processing

Your references are inspected and resized on the studio server, then uploaded to Kie. Kie and the selected generation provider process your media and prompts. Temporary provider links may be accessible to anyone who has the URL. Successful reference uploads and completed media are copied to private server storage, where access requires your studio session. Saved originals let you prepare a fresh upload for a different model without uploading the same file again.

Keys and cookies

Character names, notes and reference metadata are saved in Neon. Character images, saved upload originals and sampled video frames are held in private server storage. Selecting a character or saved upload for a model sends a prepared copy to Kie. Running the auto-prompter sends timestamped video frames and your direction to Grok through Kie, using your API key and credits. Archiving a character hides it from the active library; it does not erase its stored files. Prompt drafts and reported usage are saved to recover interrupted requests without automatically charging again.

Session cookies keep you signed in. API keys are not stored in browser localStorage. Disconnecting deletes your saved key; active jobs keep an encrypted copy until completion so results can still be recovered. Motion Studio does not collect payment card information.

Retention

Provider reference links expire, while saved reference originals, drafts and generated outputs remain in the workspace until the operator’s retention policy or an authorized deletion applies. The operator must publish a contact method for access, correction, and deletion requests before launch.