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 29 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.
Some chat pages open with a paragraph the platform itself wrote about the character. It goes out with every submission, ticked or not, and there is no switch — without it the model has to guess her looks. One block from the open chat: never your history, never another chat, never your own words. The panel names it and its length first; a page without one sends nothing.
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 and from the setting block, 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. Neither the messages you ticked nor the setting block are written into them — what appears is a count and a character total, and for the setting block a character count on its own, so that a block you did not tick can be seen to have gone out without its words being kept. 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.
Five parties, each of them given only the piece of the job it has to do.
Receives the messages you ticked, the setting block where the page has one, 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, plus this website's visitor counts through Google Analytics. It sees that you signed in, not what you rendered.
Only if you buy credits. Stripe hosts the payment page, so it receives your email address and your payment details and sends you the receipt; we are told which size you bought and nothing else. Your card number never reaches the extension, this website, or our server. Nothing about your chats or your clips is sent to Stripe.
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.
Sign-in is the only place Google is involved. This is the whole of it.
Three things, from the sign-in itself and nothing else: an account id that Google issues for this app, your email address, and your display name and avatar URL. No contacts, no calendar, no files, and no access to your Google account beyond that one moment.
Attaching your render history, usage and credit balance to you rather than to a browser. It is not used for advertising, it is not sold, and it is not used to train anything.
In the database described above, on Cloudflare. It is not passed to the model providers or to Stripe. Besides us, the only party that sees any of it is Cloudflare, which runs the server.
Write to the address below from the account you signed in with. The account row, the render history and the clips are erased together.
Lore Clip's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
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.
This website does, in the ordinary way: it loads Google Analytics, which counts page views
and shows us roughly where visitors came from. That sets two first-party cookies
(_ga and one more for this property) so that a second page view is not counted
as a second person, and it sends Google the page address, the referring link, your language,
your device type and an approximate location worked out from your IP address. Google
Analytics is the only third party this website contacts, and the only thing here not
served from this domain — Stripe is reached from the extension when you buy credits, never
from a page on this site. It is also confined to this website: the extension itself carries no
analytics of any kind, and nothing about your chats, your picks or your clips is visible to
it. Block it with any content blocker if you would rather not be counted — nothing on this
site stops working.
support@loreclip.com. That address reaches the people who built it.