GDPR on Set

What this is about

The GDPR is the frame European productions work inside, and on set it shows up as ordinary questions. Who may see the casting list. How long call sheets with private numbers stay in a shared drive. What happens to footage of someone who later withdraws consent. Whether a crew photo belongs in a public feed. The useful habits are unglamorous: collect only what the shoot needs, give consent documents one owner and one storage place, and delete what has no purpose left. For a binding assessment of your own setup, bring in a data protection specialist rather than a template.

A term only helps when everyone on set means the same thing by it — so what follows is how it is used, not a dictionary definition.

What runs differently here

Where this differs from the general case:

• Collect only the data a shoot actually needs, and delete what has no purpose left
• Consent documents need one owner and one storage place, not five phone galleries
• Call sheets carry private numbers and addresses, so distribution lists deserve the same care
• Behind-the-scenes photos of the crew are personal data too, whatever the group chat assumes

With TillyGen

TillyGen keeps planning documents inside one structured project instead of scattered chats, which makes access and deletion manageable.

Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.