Making a clip means part of your chat leaves your computer. This page says which part, where it goes, what is kept, and how to have it removed. Last updated 13 September 2026.
One request, sent when you press the button — not while you browse, and not while you tick.
In full, as they appear on the page. The spoken lines are included on purpose: the text model needs them to write the screenplay, and one of them may be picked to be said aloud in the clip and burned across the picture.
At most 60 messages, 2000 characters per message and
20000 characters in total. Past the cap whole messages are dropped, oldest first,
and the panel tells you how many were dropped.
A public image link from the platform's content network. The server fetches the file itself, which is why none of this needs your session.
How long the clip should run, an id used to tie the log lines of one request together, and your sign-in token. Nothing else rides along.
The side panel uses the local storage Chrome gives an extension. This is all of it, and all of it goes when you uninstall.
A string that expires on its own, and the time it expires. Signing out means deleting this one entry from this computer.
Three things only: the job id, the time it started, and the request id that ties its log lines together. Closing the panel and opening it again picks the progress back up from those. None of your words are in it.
The server address, an optional access token, how long the clip should be, how verbose the log is, and one yes-or-no remembering whether you have seen the first-run checklist.
The stretch you tick lives in that page's memory and is never written to storage. Reloading the page loses it, on purpose.
Chrome lists these when you install. This section says where each one is actually used.
Everything below lives on Cloudflare, in a database and an object store that only this server can reach.
The account id, email address, display name and avatar URL that Google hands us when you sign in, plus when you first signed in, when you were last seen, and your daily quota.
One row per clip: how many messages went in, how long the clip runs, its frame size and byte size, the seed, the request id, and an error string if it failed. The row can tell you how long a clip is; it cannot tell anyone what is in it.
The finished mp4, the character art the server fetched, and the prompt that was sent to the video model. That prompt is written from your messages, so it describes them — and when a line is to be spoken, the prompt holds that line word for word.
Request logs record what happened and how long it took. The messages you ticked are not written into them — what appears is a count and a character total. The screenplay the text model wrote, and the prompt sent to the video model, are written out as well, with one exception: a line meant to be spoken is replaced by its length, because that line is yours and not the model's. Only the copy stored next to the clip holds it.
There is no automatic deletion window yet. When one exists it will be stated here; until then, assume a clip and its row stay until you ask for them to go.
Four parties, each of them given only the piece of the job it has to do.
Receives the messages you ticked and returns the screenplay.
Receives the screenplay and the art URL, and returns the clip. Not your messages themselves — except a line meant to be spoken, which is passed word for word — and the screenplay was written from the rest, so it describes the scenes and the action in them.
Runs the server, the database and the storage this product is built on.
Sign-in only. It sees that you signed in, not what you rendered.
We do not train models on your chats, and we do not sell or hand them to anyone beyond the two model providers above. What those providers do with what they receive is governed by their own terms; we send them the least the job needs.
The server can erase everything tied to your account in one go — the account row, the render history, the clips and the fetched art. There is no button for it in the panel yet, so ask by email at support@loreclip.com, from the address you signed in with.
It forgets the token on your computer. Sign-in tokens are stateless and expire on their own, so signing out is a local act — it is not something the server is told about.
No. There are no cookies, no analytics and no third-party requests — every file this page loads comes from this domain.
support@loreclip.com. That address reaches the people who built it.