A privacy notice should describe the system people actually encounter. Gather the operating facts before polishing the wording.
The idea in view · Planning diagram
Prepare facts before approving wording
- Actual purpose
- Areas and functions
- Organizations involved
- Access and copies
- Retention and contact
- Approved live notice
Describe the operation honestly
List camera areas, live viewing, recording, any audio functions and the provider’s role. Do not call a system anonymous if identifiable people may appear. Distinguish an outbound warning speaker from an audio recording function.
Gather the governance facts
Ask the privacy owner to confirm the controller identity, purposes, applicable basis, contact route, disclosures and rights process. Use the full current legal guidance rather than adapting a sign from another business. A sign alone may not explain every relevant detail.
Keep notices aligned with changes
Review the notice when views, analytics, providers or retention change. Check that physical notices are visible where appropriate and that the fuller information can be reached. Record who approved the final version and which operational facts were verified.
Use the notice as a check on the design
If the team cannot explain what is captured, who uses it or how long it remains, the missing fact needs an operational decision. Ask the privacy owner to confirm the relevant legal basis, organizational role and rights process from current guidance. Do not borrow those statements from a neighboring business’s sign.
Have the site and technical owners verify the facts before final approval. Camera masks, audio settings and cloud access may differ from what a planning drawing suggests. Keep a review trigger for material changes. The ICO’s surveillance guidance is under review following the Data (Use and Access) Act, so avoid describing an old template as a permanently compliant solution.
Gather the facts the notice must accurately describe
Start with the actual camera operation: the organization responsible, purposes, locations or areas observed, relevant recording or audio functions, monitoring access and the people who can receive information. The notice should reflect what happens in practice. A generic sentence copied from another site can omit remote review, event clips or a separate incident-record system.
This worksheet prepares operational facts for the person responsible for the notice and applicable compliance review. It is not a completed legal notice for every jurisdiction. Current ICO guidance is explicitly under review, so check the relevant authority and advice when making the actual decision. Where the business operates internationally, do not assume one country's wording or process is sufficient for every location.
Reference context: ICO: surveillance data protection principles
Trace access and copies before writing broad statements
Ask where ordinary recordings, event clips, thumbnails and reports are stored and who can view or export them. A statement that footage stays on site may be incomplete if remote reviewers receive clips or incident attachments are held elsewhere. The data-flow map helps identify those paths without requiring the notice author to guess the architecture.
Confirm the approved retention decisions and contact route rather than filling blanks with assumed periods or a personal email address. Identify any uncertainty as a preparation task with an owner. A draft that looks polished but contains unverified facts is harder to correct once it is printed or published. Keep the factual evidence and the final approved wording distinguishable in the review process.
Align notices with later operating changes
A new camera purpose, audio function, provider or data flow can change the facts the notice describes. Link notice review to the site's change process. The person changing the technical system may not be the person responsible for transparency, so the handoff needs to be explicit. An accepted camera configuration should not silently expand the operation beyond the description that people encounter.
Check the actual displayed or published version after approval. The right text in a project folder does not prove that the current sign, page or linked detail has been updated. Assign the implementation and verification, including accessibility and practical readability where relevant. Keep a controlled version and review date so staff can identify the current information when responding to a question.
A fictional draft that overstates local-only storage
A site prepares a notice saying that all video remains on its recorder. The technical review finds that event clips are sent to a reviewing service and selected incident records can be exported to an approved platform. The original statement describes only one part of the operation.
The notice owner gathers the relevant organizations, purposes, access paths and retention decisions, then obtains the appropriate review of the wording. The data-flow map is corrected alongside the draft. No legal conclusion follows merely from finding a remote copy; the task is to understand and accurately govern the operation. Publishing a more confident local-only statement without checking would leave the notice disconnected from the system it is meant to explain.
Make the call
Which fact needs confirmation?
| Situation | Decision to make | What to ask for |
|---|---|---|
| Remote reviewers can see footage | Who has access and for what purpose | The proposed provider and access map |
| A speaker is installed | Whether it only broadcasts or also records | A verified function description |
| An old notice names a former provider | Which statements no longer match | A reviewed current notice and change record |
Before you move on
- Map video and audio functions accurately.
- Provide verified facts to the privacy owner.
- Review notices after material system changes.
A worksheet you can actually use
Start with the blank sheet. Add one row per item, assign an owner and mark anything unresolved as pending. The completed example shows the level of detail to aim for.
Keep completed security plans private. Use aliases; keep passwords, access codes, personal contacts and footage links in your approved systems.
How to fill the worksheet
- Fact to verify
- Name a specific operational fact needed for the notice rather than copying a legal conclusion from another organization's wording.
- Operational answer
- Record the confirmed answer about the actual purpose, functions, recipients or lifecycle, keeping unknowns explicitly pending.
- Evidence owner
- Identify the person who can substantiate the technical or operating fact and supply an appropriate controlled reference.
- Privacy review status
- Distinguish factual preparation, responsible review, approval and implementation of the version people actually encounter.
A worked example
Fictional preparation: a depot adds remote live review but no audio recording. Its privacy owner reviews access and provider details before updating the notice.
| Fact to verify | Operational answer | Evidence owner | Privacy review status |
|---|---|---|---|
| Audio recording enabled | To verify | Installer and site owner | Pending |
Questions readers bring to this task
What else should you know?
Can we use a downloaded CCTV notice template?
Use it as a prompt for the responsible privacy adviser, not as proof of compliance. Replace every assumed fact with the actual organization, purpose and process, then check the current applicable rules. This worksheet gathers facts; it deliberately does not supply universal legal wording.
Link to this answer ↗Can I use a privacy notice from another business?
Use external examples only as prompts for review. The final information must reflect your actual organization, purposes, systems, access, retention and applicable requirements. Copying another notice can import facts or claims that do not describe your operation.
Link to this answer ↗Does the worksheet replace legal or data-protection advice?
No. It organizes operational facts for the responsible reviewer. Questions about legal basis, rights, international transfers or jurisdiction-specific obligations need assessment in the actual context using current authoritative guidance. Do not treat a completed template as a compliance certificate.
Link to this answer ↗When should the notice be checked again?
Review when purposes, recording functions, providers, access, storage or contact arrangements change, and at the organization's agreed interval. Also verify the version people actually see. A correct unpublished draft does not establish that the live notice is accurate.
Link to this answer ↗Notes & sources
UK scope only; this is a fact-gathering worksheet, not a ready-made compliant notice. ICO guidance is under review and should be rechecked.
Reviewed October 27, 2026. The examples and worksheets are planning aids, not customer results or a statement of contracted service.
- ICO: surveillance data protection principles
UK surveillance guidance on purpose, retention, secure access and transparency. Guidance is under review; check it when making a decision.