Data protection impact assessment: template
For a production using Shotlore with Google Gemini · 23 October 2026 · Not legal advice; a starting point for your data protection lead
A DPIA is advisable (and under UK and EU GDPR often required) where new technology, geolocation and footage of identifiable people meet. This template is filled in with what Shotlore does; the parts in [brackets] are the production's to complete. Print it or paste it into your own form.
1. The processing
| Item | Answer |
| Controller | [Production company, address, contact] |
| Processor | Google (Gemini API Paid Services) under Google's Data Processing Addendum, version [10, 7 May 2026], accepted on the production's own Google Cloud project [project name]. Nova Insight Ltd (the maker of Shotlore) holds no data from the job and is neither controller nor processor. |
| Purpose | Cataloguing the rushes of [production]: suggested keywords, captions and headlines per still or clip, and optionally transcripts of interviews, reviewed by a person before use, so the material is searchable and deliverable with metadata. |
| Data subjects | People who appear in frames (contributors, crew, members of the public), people who speak in transcribed clips, and the crew whose positions are recorded by Shotlore Field. |
| Personal data | Images of people at preview size; voices (transcripts) where Speech in clips is used; names typed by the production (People shown, credits); positions and times of the crew's day (Field). Special-category data only if the content itself reveals it (e.g. a documentary about health); [say whether it does]. |
| Source | The production's own footage and the crew's own phones. |
| Where it goes | Previews with instructions to Google's Gemini API under the production's key (see Security › What leaves). Positions to OpenStreetMap as cell centres. Field days to the production's own cloud folder, if shoot sync is used. Nothing to Nova Insight. |
| Retention | Google: 55 days for abuse monitoring, then deleted (Google's abuse-monitoring page, 9 June 2026). The production: the job, approved metadata and the send log for [retention period]; the shoot folder archived or deleted at wrap [say which]. |
| International transfers | Google may process in any country where it has facilities; Google is certified under the EU-US Data Privacy Framework and its UK extension, with SCCs in the DPA as fallback. For data of people in Kenya: [the safeguard relied on under the Data Protection Act 2019 and the ODPC's 2026 transfer guidance]. |
2. Necessity and proportionality
- Why AI at all: [volume of material; delivery deadline; the archive or library that needs the metadata].
- Minimisation: only previews (not originals) are sent; frames spread through each clip at a rate you set (3 a minute by default, at most 60 a clip); confidential jobs send no position, place, time or speech; sensitive places are rounded or withheld; files can be left out of tagging altogether; on-device keywords are available where nothing may leave.
- Lawful basis: [legitimate interests of the production in cataloguing its own material, balanced below; or consent in release forms where relied on].
- Transparency: release forms and the production's privacy notice say that AI-assisted cataloguing is used and that previews may be processed by Google outside the UK/EU (Articles 13 and 14). Suggested wording: "Short preview images and, where interviews are transcribed, audio from the material you appear in may be processed by an AI service (Google Gemini) under our own account to suggest keywords and captions, which we review. Google does not use this to improve its products and deletes it within 55 days."
- Rights: subject access and erasure apply to the job's metadata and previews on the production's computers; Google's deletion is time-limited by design.
3. Risks and measures
| Risk | Likelihood / severity | Measures | Residual |
| Previews of identifiable people processed by a third party abroad | [ ] | Paid tier only (no training; DPA; DPF); confidential mode where agreed; on-device route for the most sensitive; send log records every call. | [ ] |
| Google's 55-day abuse log holds content longer than the commissioner allows | [ ] | Disclose it; use the on-device route for that commissioner's unreleased material; Google Cloud route when available. | [ ] |
| A free-tier key used by mistake | [ ] | Shotlore blocks confidential jobs and EEA/UK/CH computers without a confirmed paid key, warns elsewhere, and marks a key as free on a free-tier quota error. | [ ] |
| Exact positions of sensitive species or private sites leave | [ ] | Sensitive locations on by default: rounded to about 10 km or withheld in exports, lists, reports, manifests, the files' own GPS if chosen, and in what goes to Gemini and OpenStreetMap; names withheld. | [ ] |
| Face grouping amounts to biometric processing | [ ] | On the computer only; per job; only where the people have agreed; Delete face data at wrap. Not used for identification across jobs. | [ ] |
| Crew positions (Field) reveal where people were | [ ] | Days stay on the phone and in the production's own cloud folder; Need-to-know keeps each member's days to themselves; Locked encrypts them and can delete them from phones after the production holds them. | [ ] |
| Loss or theft of a computer or phone | [ ] | Disk encryption (FileVault/BitLocker); phone lock required on Need-to-know and Locked shoots; a lost phone is removed from the shoot folder and signed out of its account. | [ ] |
| Inaccurate AI descriptions of people (wrong name, wrong attribute) reaching an archive | [ ] | Nothing is written without a person's approval; names are only those the production types; the model card lists the failure modes to check for. | [ ] |
4. Sign-off
- Data protection lead: [name, date].
- Commissioner's approval of AI use, where required: [name, date, reference].
- Review date: [date], or when the level, the model or the processor changes.