Shot list, not script
Does a set-logging app upload your script to an AI?
Clapper does not take a script at all. It reads a shot list, the breakdown table a 1st AD or script supervisor already builds, and parses that on the device itself: no upload, no AI model in the loop for the parsing step. The only thing that ever reaches a server is the already-parsed shot division, scene and shot numbers and short descriptions, sent so a small model can turn them into tappable key-moment buttons. The document itself never leaves the phone.
Shot list, not script: the distinction that matters
A shot list is the breakdown, a table of scene and shot numbers with a short description of what each shot covers. A script is the full screenplay, dialogue and all. This used to be a bigger ask: the app tried reading full scripts. That changed. As of mid-2026, it only takes shot lists, and the reason was not primarily privacy, it was accuracy. A model asked to retype 137 rows out of a document is exactly where truncation and invented rows come from. Reading structure on the device instead removes that failure mode entirely, and not uploading the document is what falls out of doing it that way.
What actually gets parsed, and where
The shot-division table is parsed on the phone by a deterministic parser, not a language model. It either reads a row correctly or flags it as unparseable, and it cannot summarize, guess, or invent a row that was not in the table. Nothing about this step touches a network connection.
What the model does see
Once the shot list is parsed into structured rows on the device, that structure, not the original document, gets sent so a model can turn each shot into a set of tappable key-moment chips: a closeup, an over-the-shoulder, a slammed door. The model receives scene numbers, shot numbers, and short descriptions already extracted. It never receives the PDF, never receives dialogue, never receives pages of the screenplay.
Why this matters beyond privacy: an unreleased script is often the single most sensitive document on a production. A tool that only ever needs the shot breakdown, not the screenplay, has a smaller category of things that can go wrong, by design, not by policy.
Free, offline, no account for logging
Log takes without handing anything to a server
Take logging and tagging work fully offline with no account. Shot-list enrichment, and PDF, Premiere XML, and CSV export, all need a free sign-in and draw on a small free quota. Shot-list enrichment is the only one of those that touches a server with any content beyond your own taps, and it only ever sees the parsed structure, never the document.
Open Clapper →