Plan footage retention around a defined purpose
Set a reasoned retention rule, then check how the recorder applies it under real conditions.
Start with the time needed to notice an event
Work backwards from a realistic reporting routine. At a shop with daily deliveries, the manager may find out about an issue when paperwork is reconciled. In a shared building, the people who raise concerns may be away when an incident occurs. Note how long it would take an authorised person to receive the report and review the relevant interval. Record why that period is useful, who decides, and when it should be reconsidered. Where a legal requirement, complaint or investigation might apply, ask a qualified Zimbabwean adviser or the appropriate authority how it affects the decision.
Check how the recorder behaves
Ask the installer to show you the exact recorder or service settings and the manufacturer documentation that describes them. Some devices overwrite older recordings when space runs low, and the actual period can depend on settings and how much the cameras record. Observe the oldest retrievable footage after normal use rather than treating the storage size on a box as a measured retention period. Record whether motion or continuous recording was used in the test. Note how the recorder shows a full drive, a stopped camera or footage gaps, and agree who checks those conditions.
Agree an exception process
Separate ordinary footage from material that needs to be preserved for a specific, documented reason. An incident record should name an authorised decision-maker, the relevant time range and a review date. Keep the retained extract in a location with agreed access controls. Write down which copies exist and how their handling is reviewed. As an example, a reported damage claim might need a short extract covering the agreed period; copying the complete day introduces footage of unrelated people. If an authority or an adviser needs the original file preserved, seek instructions before modifying or deleting relevant material.
Review the rule in practice
At handover, ask an authorised person to find the oldest sample and then locate a known test recording. Repeat after a change in image quality, camera count, recording mode or subscription. For each check note the time of the test, the scope and any discrepancy with the written policy. If storage forces earlier overwriting than expected, revisit both the justified period and the technical proposal. If recordings are kept longer than expected, look for an unexamined archive, manual export or backup. The useful record is a repeatable check that helps the people responsible understand what the system actually keeps. Keep the policy review date on a calendar used by the responsible person, alongside the particular checks and the record they should bring.
Sources for this guide
- Data Protection Authority implementation guidelines
Zimbabwe context for impact assessment, cross-border transfers and small-enterprise data handling.
- AXIS OS knowledge base
Manufacturer reference. Verify the manual and features for the exact equipment on your site.
Next guide: Compare local and cloud recording