Application configuration guidelines
The MPA's Content Security Best Practices (v5.3.2, AI Supplemental TS-7.1) ask a production to "source, apply, and annually review Application Configuration Guidelines provided by the licensor". These are ours. They say how to set Shotlore up for each level of confidentiality, what to switch off, and how to keep the record a commissioner will ask for. Review them once a year, or when a new version says this page changed.
Before the shoot
- Decide the confidentiality level with the commissioner (see notes for commissioners): On this Mac (nothing leaves; on a PC, keywords from the on-device picture model do the same), paid Gemini, or wait for the Google Cloud route. Write the decision into the production's AI inventory with the date and who approved it.
- Install Shotlore from shotlore.app/download only. On a Mac the app is notarised by Apple; check Shotlore › About shows the version you expect. On Windows the installer and every program in it are code-signed: right-click the installer › Properties › Digital Signatures shows the signature.
- Turn on disk encryption on every computer that will hold the job: FileVault (Mac) or BitLocker (Windows). Shotlore keeps the job, previews and phone mirrors in your home folder; the disk is their protection at rest.
- Keep the Gemini key, the job folders and the phone mirrors out of folders that sync to a cloud you don't intend (Desktop and Documents on a Mac with iCloud Desktop & Documents on, for example). Shotlore's own data is in Library › Application Support › Shotlore (Mac) or AppData › Roaming › Shotlore (Windows).
The Gemini key
- In Google Cloud, make a new project for this production (or for your company's confidential work). Don't reuse a personal project.
- Link billing to the project. This is what puts the key on Google's Paid Services, where Google doesn't use your content to improve its products and its Data Processing Addendum applies. Accept the DPA in the Cloud console (it is accepted by using the paid services; keep a copy of the version you accepted: version 10, 7 May 2026, at the time of writing).
- Set a spend cap (Billing › Budgets & alerts), so a mistake costs a known amount.
- Make the API key in that project and restrict it to the Generative Language API only. Name it after the production.
- In Shotlore › Settings › Gemini key, paste it, Test key, and tick "This key is in a Google Cloud project with billing on". Shotlore cannot tell the tier from the key; that tick is your confirmation and is written into every send-log entry. If Google ever answers with a free-tier quota error, Shotlore marks the key as free by itself and warns before the next run.
- Never type a key into a message, a job file or a document. The key lives in the Keychain or Credential Manager and goes only to Google. If a key is ever exposed, revoke it in Google Cloud and make a new one.
- Model: new jobs use Gemini 3.5 Flash-Lite. The model name is in each send-log entry; don't change it mid-job without noting why.
Choose the level
| Level | Set in Shotlore | What leaves the computer | Use when |
|---|---|---|---|
| On this Mac | Keywords & captions › keywords from On this Mac; leave Transcribe off; no Gemini key needed. | Nothing (place names still go to OpenStreetMap as cell centres unless you skip Look up places). | Channel 4 jobs without CE approval; any job where the commissioner says no cloud AI; shoots at highly sensitive sites. |
| Paid Gemini, confidential job | A paid key confirmed as above; Keywords & captions › Confidential job ticked. | Previews and your instructions only. No position, place, time or speech. No transcripts. Nothing at all if the key isn't confirmed paid. | Unreleased material, named talent, a commissioner who asked for minimum data. |
| Paid Gemini, standard | A paid key confirmed; Confidential off; Sensitive locations on (it is by default). | Previews, instructions, time, position and place name (rounded or withheld for sensitive places), the speech summary if transcribed; transcripts if you run Speech in clips. | Most work. Tell the commissioner; keep the send log. |
Whatever the level, keep Sensitive locations on (Credits & places › Sensitive locations) and add the production's own sensitive words (species, a contributor's name, a site) to its list. Mark sensitive named places as sensitive when you create them.
Per job
- Preview size (Previews step): 2048 px is the default and plenty for keywords; use 1600 px for confidential jobs. Fewer frames per clip (Previews › frames) means less sent.
- Speech in clips sends sound. Run it only when the commissioner has agreed (ITV treats voices as personal data needing pre-approval); it is off on confidential jobs.
- People shown stays on the Mac, but it is face grouping: use it only where the people have agreed (release forms), and use Delete face data at wrap if the production's policy says so.
- Look up places sends cell centres to OpenStreetMap; for a job at one sensitive site, skip it and name the place yourself.
- Leave files out of tagging (Every file › Leave out) for anything that must not be described by a cloud model: a particular contributor, a location reveal, a prop.
- Before the first run on a client's job, open Keywords & captions and read the line under Confidential job: it says what will leave this computer.
Shoot sync and Field
- Choose the shoot's level in the pack editor (Shoot packs › Sync & security): Open, Need-to-know or Locked. The levels are described in Shotlore Field; the shoot security sheet (Shoot sync › Security sheet for the client) prints what you chose for the client.
- The shoot folder lives in the production company's cloud account, shared with named crew accounts only, never "anyone with the link". A client's Workspace often blocks sharing outside its domain, so the production owns the folder unless the client issues accounts.
- On a Locked shoot: make the shoot key on the coordinator's computer before sharing the folder, write the recovery code down once and keep it sealed (it is shown once), and key each phone in person over the link (the phone pairs with that computer through Share with Shotlore). Lost key and lost computer means the encrypted files are gone; nobody, including us, can recover them.
- Crew install Field from the App Store or Google Play (or the beta links while in testing), open the pack, and pick their folder once. Their phones hold their own days; a Locked shoot can delete them after the production confirms it holds them.
- The local-network link works on any Wi-Fi where devices can see each other; lodge and office guest networks often isolate devices, in which case the phone's own hotspot with the laptop joined to it always works.
The computer
- Disk encryption on; a login password; the screen locks when idle (System Settings › Lock Screen, or Windows Settings › Accounts › Sign-in options). Shotlore has no session lock of its own yet (MPA TS-1.17 asks for a 15-minute expiry; the operating system's lock is the control until then).
- Keep Shotlore updated: it checks download.shotlore.app at launch and installs updates you accept; the update is signed and verified before it is applied.
- Don't run Shotlore on a shared account. The Gemini key and the shoot key are per user.
- Back up the job folder with the production's normal backups; the job file holds the send log and everything you approved.
The record
- The send log (Keywords & captions › Save the log…) is the per-project audit record: save it as CSV into the production's compliance folder at the end of tagging and at wrap. The library manifest, if you export one, carries a summary.
- Keep with it: this page's version, the model card, the commissioner's written approval, the confidentiality level and who chose it, the Gemini project name and the date billing was confirmed, and the shoot security sheet.
- If something goes wrong (a key exposed, the wrong level used, a file sent that shouldn't have been), the MPA supplemental asks for client notice within 24 hours; the send log tells you exactly what went and when.
At wrap
- Save the send log and the wrap report (Shoot sync › Wrap report…).
- Archive and unshare the shoot folder; forget the phones in Shotlore (their mirrors are deleted); on a Locked shoot, keep the key with the archive if the encrypted copies are kept, or destroy both.
- Delete face data if the production's policy says so; revoke a production-specific Gemini key in Google Cloud if the production is over.
Checklist
- Level agreed with the commissioner and written down.
- Gemini key in its own billed project, restricted, capped, confirmed in Shotlore.
- Disk encryption on; screen lock on.
- Sensitive locations on, with the production's words; sensitive places marked.
- Confidential job ticked where agreed; Transcribe only with approval.
- Shoot level chosen in the pack; folder in the production's account, named accounts only; key made and recorded (Locked).
- Send log and security sheet saved to the compliance folder.