Security and confidentiality
Productions ask us the same three questions: what leaves the computer, who can see it, and whether anyone trains on it. This page answers them with the facts we can stand behind, quotes Google's and the broadcasters' own words with their dates, and says plainly what Shotlore doesn't yet have. The supporting documents a compliance team usually asks for are linked from each section and listed at the end. What Gemini costs is on the Questions page.
The short version
- Shotlore has no account, and no server of ours can read your material. Nothing from a job reaches us. The one service we run for shoots is the optional crew relay (crew.shotlore.app): if you take a shoot online for a crew, it carries the crew's items encrypted with the crew's key, which we never hold, and deletes them 30 days after the last change (Privacy). The app asks our website whether a newer version exists and, for a key bought on shotlore.app, checks once (from 14 days after buying) that the key wasn't refunded, sending only the key. Trial keys are never sent.
- Your rushes never leave. Not the clips, not the raw files, not a full-resolution frame. When you use AI, a small preview goes to Google under your own Gemini key, and nothing goes anywhere if you choose keywords found on the computer (On this Mac, or the optional on-device picture model on a Mac or a PC).
- On a paid Gemini key, Google says it doesn't train on your content and processes it under its data-processor terms. It does keep prompts and responses for 55 days for abuse monitoring. If that is too long for your production, there is an on-device route today and a Google Cloud route coming.
- Sensitive places never leave exact. Positions of rhino, nests, dens and private land go to Gemini and OpenStreetMap rounded to about 11 km, or not at all, and their names are withheld (0.7.4).
- Every call to Gemini is logged in the job (what was sent, which model, when, how many tokens), and the log exports as CSV or JSON for your commissioner (0.7.4).
- Video and cinema raw files are never rewritten. Editors get import files. Stills keep an untouched copy beside them.
What leaves your computer, and where to
Every outside service Shotlore talks to, and exactly what it is sent. There are no others. This table is also inside the app: the shoot security sheet (Shoot sync › Security sheet for the client) prints it with the shoot's own settings.
| Service | What is sent | When | Under whose account |
|---|---|---|---|
| Google Gemini API | Per still or clip: a JPEG preview (longest side 1600, 2048 or 3072 px; for a clip, frames spread through it at a rate you set, 1 to 12 a minute and 3 by default, at least 3 and at most 60 a clip), your shoot description and instructions, the capture time, the position and place name, and a one-line speech summary if the clip was transcribed. For a sensitive place: the position rounded to about 11 km or withheld, and no place name. On a confidential job: the previews and instructions only. For transcripts: the first 45 minutes of the clip's sound as low-bitrate mono audio. | Keywords & captions, Speech in clips, "Write the instructions from this" | Yours. The key is in your Keychain (Mac) or Credential Manager (Windows) and goes only to Google. |
| OpenStreetMap (Nominatim and Overpass) | The centre of a 2 km cell (place names) or a 5 km cell (park boundaries), never a file's exact point; for a sensitive place the rounded position or nothing. Requests identify the app as Shotlore/<version> (hello@shotlore.app), as OpenStreetMap's policy requires; none of your details. One request a second, results cached. | Look up places; "nearby names" for a place you're naming (a 1 km-grid point) | Public service, OpenStreetMap Foundation. |
| Map tiles (Esri World Imagery, OpenStreetMap) | Which map tiles to draw, so roughly where you're looking. | Any map view | Public services. |
| download.shotlore.app | A request for the current version number. No job data. | About four seconds after launch, when online | Ours (Vercel). |
| Your own mail app | Only if you choose Report a problem: a plain-text report you read first (app version, system, the error, the last lines of the activity log; nothing from the job), addressed to hello@shotlore.app. | When you send one | Yours. The app sends nothing itself. |
Shotlore has no analytics, no crash reporting and no telemetry. Licence keys are checked on the computer. Tides are worked out on the computer. All connections use TLS. What Shotlore Field sends is in its own section.
What never leaves
- The clips, the raw files, the sound files, and full-resolution frames.
- Your Gemini key, which is sent only to Google, in the request, and is never written to job files, logs, diagnostics or problem reports.
- The job itself (positions, keywords, captions, transcripts, touch-ups): it lives in Pictures › Shotlore on your computer, and anywhere you choose to put it.
- Faces. People shown groups faces on the computer (with Apple's own frameworks on a Mac, and an on-device face-recognition model on Windows); no face data is sent anywhere, and Delete face data removes it.
- Anything at all, if you choose On this Mac (free, private) for keywords and leave Gemini off.
Gemini: your key, Google's terms
Shotlore never holds your pictures or your key, so the contract that matters is between your company and Google. Google's rules differ sharply between free and paid keys. Quotes are from Google's Gemini API terms (effective 23 March 2026, updated 28 April 2026) and its abuse-monitoring page (updated 9 June 2026), as read on 23 October 2026.
| Free key (no billing on the Google Cloud project) | Paid key (billing linked) | |
|---|---|---|
| Used to improve Google's products | Yes. Google uses content "to provide, improve, and develop" its products, and "human reviewers may read, annotate, and process your API input and output." Google's own advice: "Do not submit sensitive, confidential, or personal information to the Unpaid Services." | No. "Google doesn't use your prompts … or responses to improve our products." |
| Contract | The same Gemini API terms, without the Data Processing Addendum. | Google's "Data Processing Addendum for Products Where Google is a Data Processor" (version 10, 7 May 2026), which lists "Gemini API Paid Services" as a covered service. Google is your processor; you are the controller. |
| Kept for abuse monitoring | Prompts, context and output are retained "for fifty-five (55) days", can be "accessed for human review only by authorized Google employees" when flagged, and are "not used to train or fine-tune any AI/ML models besides those used specifically for policy enforcement." They "may be stored transiently or cached in any country in which Google or its agents maintain facilities." | |
| In the EEA, Switzerland or the UK | Google's terms say an app like Shotlore may use "only Paid Services" for users there. Shotlore 0.7.4 won't start a Gemini run from a computer in those regions until the key is confirmed as paid. | |
| Transfers out of the UK/EU | Google is certified under the EU-US Data Privacy Framework and its UK extension, with standard contractual clauses in the DPA as fallback. | |
Our advice to every production: make a key in its own Google Cloud project with billing on, restrict it to the Gemini API, set a spend cap, and never use a free key on client work. Shotlore walks you through it under Gemini key, and asks you to confirm the key is paid; a quota error that names the free tier marks the key as free by itself. Shotlore cannot tell the tier from the key alone, so the confirmation is your word. Step by step: Configuration guidelines.
Three levels of confidentiality
On this Mac
Keywords from Apple's image recognition, or from Shotlore's optional on-device picture model on a Mac or a PC. No key, no cost, no frame leaves the computer. No captions or transcripts. Choose it per job. Available now (Mac and Windows).
Paid Gemini
Keywords, captions and transcripts to your brief, under your own paid key. No training; Google's DPA; a 55-day abuse log you can't shorten. Right for most work; tell the commissioner. Available now.
Your own Google Cloud (Vertex AI)
The same models through your production's own Google Cloud project: pick an EU or UK region, keep processing in region, and apply to Google to switch off prompt logging (customers on a Google Cloud Master Agreement are exempt by default). Google's ISO 27001, 27018, 42001 and SOC 2 reports cover this route. Coming.
Within any level, a job marked Confidential (0.7.4) sends Gemini the previews and instructions only: no position, place name, capture time or speech; transcripts are off; and nothing is sent at all unless the key is confirmed as paid. Smaller previews, one frame per clip, a scrubbed brief and faces blurred on the Mac are the next step.
The send log: what left this computer
From 0.7.4 every call to Gemini is recorded in the job: when, which file (by name), how many previews and at what size, or how many minutes of audio; the model and endpoint; whether the position went exact, rounded or not at all, and whether the place, time and speech went; a version hash of the instructions, so a reviewer can see when the prompt changed; Google's token counts; the result or error; the key's tier and whether the job was confidential. Keywords & captions shows the count and saves the log as CSV or JSON, and the library manifest carries a summary. This is the "audit log of all AI actions" the MPA AI Supplemental asks for, and the "keep the prompts" that TV 2 Danmark asks for. Nothing from the files themselves is in it.
What broadcasters and streamers ask
The full dated table, with more broadcasters, is on broadcaster AI rules; Google's terms in detail are on Gemini API for productions.
Where a broadcaster has published rules for its production partners, here is what they say and how Shotlore fits. Quotes were checked against the documents on 23 October 2026; where a document is only available to partners, we say so. Always check your own commissioning agreement, which may say more. A one-page note per broadcaster, ready to send with your disclosure, is at Notes for commissioners.
| Who | Their rule | How Shotlore fits |
|---|---|---|
| Netflix "Using Generative AI in Content Production", August 2025 (partner portal; wording as reported by trade press) | Tools must "not store, reuse, or train on production data inputs or outputs" and be used "in an enterprise-secured environment" where possible; written approval where personal data or unreleased assets are involved. | Paid Gemini meets "train"; Google's 55-day log means it doesn't literally meet "store". Expect to ask your Netflix contact. On this Mac, or the Google Cloud route, is the clean answer. |
| ITV "Use of AI in ITV Commissioned Content" v2, September 2026 | An approved-tools list that includes Gemini; logging and transcription are low-risk uses to be "notified to ITV as part of the final deliverables"; "any use of AI which involves personal data (such as names, faces, voices, images, or recordings)" needs pre-approval. | Good fit. Note the pre-approval when frames show people or clips are transcribed. |
| Channel 4 "AI Editorial Guidelines for Commissioned Content" | "No uploading of confidential, personal, or rights-sensitive information into external systems." All AI use agreed with the Commissioning Editor in advance and documented, "including purpose, scope, and human oversight involved." | Read literally, that rules out sending frames of rushes to any cloud AI without approval. Use On this Mac unless your CE agrees otherwise; the send log documents the rest. |
| Sky "Framework on using AI in Commissioned Programming" | "Only use secured, self-vetted and 'enterprise' graded tools"; confirm the tool "will not reuse, retain, or train on production materials"; written approval for moderate and high-risk uses; "clear auditable records of AI use". | Paid Gemini gives you the no-training confirmation in Google's terms; the retention point needs stating. The send log is your auditable record. |
| BBC Editorial Guidelines, "Guidance: The use of Artificial Intelligence" | Warns that inputs "may be used by the developer of that AI to train it further or be shared with third parties"; indies need "a senior editorial figure … responsible and accountable for its use of AI" and should raise material uses at commissioning. | Have this page and Google's terms ready for that senior figure. Metadata is unlikely to be a material impact on content, but say what you're doing. |
| Disney, Nat Geo, Apple TV+, Amazon, Warner Bros. Discovery, Paramount | No public partner rules; handled in your contract, their security questionnaire and, for post vendors, TPN. | See the MPA section below. |
MPA best practices and TPN
The Motion Picture Association's Content Security Best Practices, which the Trusted Partner Network assesses against, gained an AI Supplemental in version 5.3.2 (23 September 2026). It places duties on the production company, and Shotlore is built to make them easy to meet:
- Client approval before AI touches client content (OR-5.0, TS-7.2): the notes for commissioners are the disclosure; the confidentiality setting and the send log give you the per-project record.
- Configuration guidelines and a model card from the licensor (TS-7.1): Configuration guidelines and the model card.
- An audit log of AI actions, "including prompts submitted … outputs produced … and timestamp" (TS-7.2): the send log, from 0.7.4.
- Third-party AI that cannot train on content, with least or zero retention (TS-7.4): paid Gemini, or the Google Cloud route for zero retention.
- Encryption (TS-3.0): TLS in transit; FileVault or BitLocker for data at rest on your computers; on a Locked shoot, the phone's files are encrypted before they leave it.
Shotlore is not TPN-assessed. As a desktop app whose only service is a relay for encrypted crew data, there is little for an assessor to visit, but we intend to publish a TPN self-assessment once the AI Supplemental questionnaire is available to small vendors.
Data protection: who is responsible for what
- Your company is the controller for the frames and positions you send. Google is your processor under its DPA. Nova Insight is neither: we hold no job data. The list of everyone who does is at Who handles your data.
- A face in a frame is not biometric data under GDPR unless it is processed "through a specific technical means allowing the unique identification" of a person (Recital 51). Captioning isn't. Face grouping on the Mac is closer to it, which is why it stays on the Mac and can be deleted.
- A DPIA is advisable where you combine AI with geolocation and footage of identifiable people. A filled-in starting point: DPIA template.
- Tell contributors. Your release forms and privacy notices should mention AI-assisted cataloguing and overseas processing (Articles 13 and 14). Suggested wording is in the DPIA template.
- Kenya. The Data Protection Act 2019 applies to anyone processing data of people in Kenya. Transfers abroad need appropriate safeguards, adequacy, necessity or explicit consent; the ODPC published guidance notes and Kenyan standard clauses in 2026.
- EU AI Act. Article 50's transparency duties (from 2 August 2026) cover deep fakes and AI text published to inform the public. Catalogue keywords and captions that are reviewed by you before use are neither; Shotlore still records which calls produced them, and marking AI-suggested fields in the files themselves is coming.
Sensitive species
Exact positions of rhino, pangolin, nests and dens are the one kind of metadata that must not travel. Shotlore's Sensitive locations feature rounds them to about 11 km, or withholds them, in every export, list, report and manifest, can protect the GPS in the photos themselves, and from 0.7.4 applies the same rule to the position sent with a preview to Gemini and to OpenStreetMap, withholding the place's name as well. The rounding follows the GBIF guidance for high-sensitivity taxa (coordinates to about 0.1°); park authorities such as Kruger ask visitors to switch off geotagging for the same reason, and Kenya's 2015 Wildlife Database regulations treat such data as classified and restricted.
Shotlore Field and shoot sync
- No account, no analytics, no tracking. Days stay on the phone and, if you turn it on, in your own iCloud Drive. Apple says third-party app data in iCloud is "always encrypted in transit and on server"; with Advanced Data Protection on your Apple Account it is end-to-end encrypted.
- Crew shoots live in the producer's own iCloud; nobody at Nova can see them.
- Weather comes from Apple Weather on iPhone and from MET Norway on Android, when switched on; each receives a position rounded to about a kilometre.
- Country packs are downloaded from shotlore.app; the country is worked out on the phone and nothing about you is sent.
- The local-network link (Field 1.4, Shotlore 0.7.4): the phone and the computer talk directly over the same Wi-Fi or a hotspot, after pairing with a code shown on the phone. Nothing goes through the internet.
- The shoot folder (Field 1.4): a production can share one folder in its own Google Drive, OneDrive or iCloud Drive; every phone writes its signed day files into it and Shotlore reads them. The folder is the production's; Shotlore and Field reach it through the phone's and computer's own Drive apps, and we hold no credential for it.
- Levels. A production chooses Open, Need-to-know or Locked when it makes the shoot pack. Need-to-know keeps each member's days to themselves, turns off sharing by message, and asks for the phone's lock. Locked encrypts every file on the phone before it leaves, with a key that only travels in person, and can delete days from phones once the production holds them. The full description, including what no level can promise, is in Shotlore Field and printed for the client by Shotlore as the shoot security sheet.
The detail is in the privacy policy.
About Nova Insight
Shotlore is made by Nova Insight Ltd, Nairobi (registered with Kenya's Office of the Data Protection Commissioner (ODPC) as a data controller and a data processor), and built by Barny Trevelyan-Johnson of Highly Visual, who has been filming since 2001. We run no servers that can read your material: the optional crew relay holds only data encrypted with the crew's key. Our website keeps the name and email you give us for a trial or the beta, and sends mail through Resend. Problem reports you choose to send arrive as ordinary email. That is the whole list; it is written out at Who handles your data.
What we don't have
- No SOC 2 or ISO 27001 certification. Google's certifications cover its Vertex AI / Gemini Enterprise service, not the plain Gemini developer API.
- No TPN shield yet.
- No independent penetration test yet. The Mac app is notarised by Apple; both apps ship a content security policy and limit file access to your home folder, external drives and their own folders. The Windows installer and every program in it are code-signed.
- No way to shorten Google's 55-day abuse log on the developer API. That is Google's, not ours; the Google Cloud route is the answer.
- Not yet: the Google Cloud (Vertex AI) route; AI-suggested fields marked as such in the files; a client-level confidentiality setting; the smaller-preview minimise mode; a TPN self-assessment.
Documents
- Application configuration guidelines: how to set Shotlore up for a production, by confidentiality level (MPA TS-7.1 and TS-1.17).
- Model card: Shotlore keywords, captions and transcripts: which models, what goes in, what comes out, how it fails, where the human is.
- Data protection impact assessment template: for a production using Shotlore with Gemini.
- Notes for commissioners: one page each for Netflix, ITV, Channel 4, Sky and the BBC.
- Who handles your data: every company in the chain, what it sees, under whose terms.
- The shoot security sheet and wrap report: printed by Shotlore for each shoot (Shoot sync panel).
Questions from a compliance or legal team are welcome at hello@shotlore.app. We'd rather answer them before the shoot than after.