Application configuration guidelines

Shotlore 0.9.0 for Mac and Windows · Shotlore Field 1.5 · 9 November 2026 · For the person setting Shotlore up on a production

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

  1. 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.
  2. 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.
  3. 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.
  4. 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

  1. In Google Cloud, make a new project for this production (or for your company's confidential work). Don't reuse a personal project.
  2. 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).
  3. Set a spend cap (Billing › Budgets & alerts), so a mistake costs a known amount.
  4. Make the API key in that project and restrict it to the Generative Language API only. Name it after the production.
  5. 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.
  6. 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.
  7. 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

LevelSet in ShotloreWhat leaves the computerUse when
On this MacKeywords & 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 jobA 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, standardA 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

Shoot sync and Field

The computer

The record

At wrap

Checklist