InnerWeb
Skip to main content

Checklist: privacy of screen recordings in a film

A screen recording of the system in a training film reaches guests and external companies, meaning people outside the organisation. One frame with a real surname on a list is enough for the film to have to be withdrawn. The checklist below describes how to check a recording for personal data before the film enters the library.

Principle one: demo data instead of real data

The safest protection is not recording real data at all. Demo data is used for training films: invented people, companies and permits. The risk of a leak is then limited to a mistake in preparing the environment, rather than an accidental shot of a real employee.

Before recording, check that the demo environment does not contain copies of production data, even partial ones. The data protection specialist should know the source of the data in the instance being recorded, and not assume it is artificial.

Also make sure the frame does not contain other windows, system notifications, browser tabs or bookmark bars that could reveal personal data or internal names.

Principle two: switch features on only for the recording

For training films demo data is used, and features needed only for the recording, for example open registration, are switched on for the duration of the recording and switched off afterwards. This way the recording does not leave anything in the system that could be used by outsiders.

Note in the documentation which features were enabled, for how long and who switched them off. After the recording check that registration has returned to its normal state and that demo accounts do not have more permissions than needed.

This is a simple practice that is often skipped: open registration left on after a recording is a gap that exists independently of the film itself.

Frequency of OCR frame checks in a screen recording

Frequency of OCR frame checks in a screen recordingBars: a one-per-second review is 1 frame per second, OCR every 0.1 seconds is 10 frames per second.0246810frames per second of checkingHuman eye (illustrative, 1 frame/s): 1 frames per second of checking1Human eye (illustrative, 1 frame/s)OCR every 0.1 s: 10 frames per second of checking10OCR every 0.1 s
Source: Sample calculation: 0.1 s step from the recording check procedure, compared with a one-per-second review

Principle three: automatic frame checking

The human eye can miss a single frame. That is why screen recordings are checked automatically: OCR of frames every 0.1 seconds detects personal data that has to be blurred. A sequence of several hundred frames per minute gives a chance to catch what a person would see only for a fraction of a second.

The most common problem is the first frames of lists and drop-down fields. Data can be visible before blurring, for example at the moment a user list is expanded, before the effect is applied. That is why blurring has to cover the whole time the field is visible, from the first frame, not only from the moment the list has settled.

After applying the blur, repeat the OCR on the finished video file, not on the source material. The check should concern what the viewer will see.

Principle four: the recording stays in the private library

Film files in the video library are private company material. They have no public addresses, and playback runs through an authenticated stream with support for seeking. This limits the consequences of a possible error, because only logged-in users see the film, not everyone who knows the address.

This does not replace the content check. The film reaches guests and external companies, who are people outside the organisation, so personal data in the frame would be a disclosure outside the plant. Always carry out the privacy check before uploading the file to the library.

Adding a film to the library is a data change on the installation, and before every edit of the catalogue the system saves a copy of the previous file. If you detect a problem after publication, withdraw the entry and upload the corrected film.

Evidence of the check for data protection documentation

Record in the documentation: the date of the recording, the source of the data, the features enabled for the recording, the result of the frame OCR check and the publication date. This provides evidence that the plant exercised due care in preparing the material.

The data protection specialist approves the film after watching it in full at normal speed and after checking the OCR report. Only then does the film go to the BHP manager's check before publication. The checklist does not replace the plant's legal assessment, but it organises the evidence.

Checklist

Video

Frequently asked questions

Why OCR every 0.1 seconds and not every second?

The first frames of lists and drop-down fields can be visible before blurring for a fraction of a second. A denser check increases the chance of detecting such a frame.

Does a private library replace the check of the recording?

No. The library limits access to logged-in users, but the film reaches people outside the organisation, so personal data in the frame would be a disclosure.

What to do with open registration after the recording?

Switch it on for the duration of the recording and switch it off afterwards, and note the change in the documentation.

Who approves the film for privacy?

The plant's data protection specialist, after watching the film and checking the frame check report.

Let's talk about the induction film at your plant

We will show how the video library, the registration kiosk and the evacuation list connect into one entry flow. Book a conversation or a demo.

Let's talk