Public webcam or security CCTV? The difference matters in Durban

Durban already has camera views that ordinary members of the public can open: beach and surf cameras, hotel webcams and SANRAL’s KZN traveller-information camera map.

They may look like CCTV, and in a broad technical sense they are cameras sending video or images to viewers. But a public webcam and a security CCTV system are usually designed around different purposes.

That difference decides whether the picture is recorded, how long it exists, who can retrieve it, whether it can support an incident and whether another website may legally reproduce it.

Public describes the audience, not the evidence

A public webcam is intentionally made available to a broad audience. Its purpose might be checking surf, weather, beach activity or road conditions.

A security CCTV system is generally deployed for protection, monitoring, investigation, access control or operational oversight. Its live view may be restricted to authorised users and its recordings managed to a retention policy.

The same physical camera technology could be used in either role. What matters is the system around it:

• why the camera exists;
• who is allowed to view it;
• whether it records continuously, by event or not at all;
• where footage is stored;
• how long it is retained;
• what image quality and timestamps are preserved; and
• who is responsible for disclosure and privacy.

Seeing a moving picture in a browser does not answer any of those questions.

Durban’s public-camera examples serve different purposes

Blue Waters Hotel publicly links live camera pages for its North Beach property and Belaire Suites. These are beachfront views presented for public viewing through Angelcam.

OceanEye intentionally publishes many named surf-camera locations across Durban and KZN. It uses a free-registration and subscription model, with access and features controlled by the publisher.

SANRAL’s i-TRAFFIC service is different again. It provides traveller information for national roads, including access to current camera images and traffic conditions. SANRAL’s Traffic Management Centres use road CCTV operationally, but the public-facing service is designed to inform travellers—not to provide unrestricted incident footage.

These sources can all be useful. They should not be treated as one interchangeable camera network.

A live page may not keep any history

Some public-camera services are live only. Others may create a short time-lapse, retain limited rewind for subscribers or keep operational recordings outside the public interface.

If a collision, theft or weather event occurred yesterday, the fact that a camera was visible online does not prove yesterday’s footage still exists.

Before relying on a public camera for evidence, establish:

• whether it was recording at the relevant time;
• whether the clock and date were correct;
• whether the required view and detail were captured;
• whether the retention window has already expired;
• whether the operator accepts preservation requests; and
• what lawful process applies to obtaining footage.

SANRAL’s current FAQ makes the boundary clear for road-camera footage: unrestricted release could affect road-user privacy, and recorded footage is handled through a formal SAPS investigation process rather than as a public download.

Do not wait until the retention window has passed before approaching the relevant operator or investigating officer.

Resolution and viewpoint may suit weather—not identification

A beach webcam can show wave height, cloud, visibility and general activity while being useless for identifying a person on the promenade.

The camera may be:

• aimed at a wide scenic view;
• compressed for many public viewers;
• refreshed as occasional still images rather than full video;
• backlit by sunrise or ocean glare;
• positioned too far from people or vehicles;
• missing useful timestamps; or
• deliberately limited to reduce bandwidth and privacy impact.

That is not a faulty camera. It is a camera serving a different purpose.

Security CCTV should begin with the evidence task: overview, detection, recognition, identification or a specific operational event. A tourism camera begins with a useful public view.

Publicly viewable does not mean free to republish

This is one of the most important rules for Durban CCTV’s planned public-camera map.

A publisher can make a stream available for people to watch while retaining copyright, platform and distribution rights. Normal linking, live embedding, screenshots, thumbnails, recording and redistribution are separate uses.

Examples from current terms:

• SANRAL permits public access to i-TRAFFIC but prohibits redistribution, republication and framing without written consent.
• SkylineWebcams allows sharing through its provided links, while saying live video embedding is reserved for camera hosts. Its terms restrict copying and screenshots.
• OceanEye reserves rights in its camera service and content; its views should be linked rather than copied without permission.
• Angelcam distinguishes a public camera-page URL from the camera owner’s paid, controlled embed capability.

Our map can therefore point users to an operator’s official public page. It must not extract hidden stream addresses, mirror frames or place a player on our site unless the rights holder supplies permission and an appropriate embed.

An unsecured camera is not a public webcam

A camera that appears without a password because it was misconfigured has not necessarily been published intentionally.

The ethical and security test is not “Can we open it?” It is:

• Does the camera operator publicly advertise this view?
• Is there a normal publisher landing page?
• Is the viewed area clearly intended for public observation?
• Do the operator and platform terms allow the proposed use?

Durban CCTV’s Eye will not scan IP ranges, search exposed-device databases, try default passwords, query ONVIF/RTSP endpoints or list private cameras found by accident.

If a view appears to expose a home, private workplace, security access point or other unintended scene, it is rejected even if no login prompt appears.

Public cameras still raise privacy questions

Making a camera view public increases its audience. Operators should consider whether the scene captures identifiable people, neighbouring private spaces, vehicle details, children or patterns of movement beyond the intended purpose.

South Africa’s Protection of Personal Information Act establishes principles including accountability, processing limitation, purpose specification, openness and security safeguards. It does not create one universal rule for every webcam or CCTV camera, and this article is not legal advice.

Good public-camera practice includes:

• aiming at the intended public scene rather than private windows or entrances;
• limiting detail and retention to the stated purpose;
• explaining who operates the camera;
• providing a privacy/contact route;
• protecting the administration interface even when the view is public; and
• responding quickly to reports of unintended exposure.

The public player can be open while camera administration remains strongly secured.

What Durban CCTV’s Eye will show

The planned map will act as an attributed directory, not a surveillance console.

Each entry should state:

• the public place or area viewed;
• the camera publisher;
• whether access is open, registration-based or subscription-limited;
• the last date the public landing page was checked;
• whether the entry links out or has explicit embed permission; and
• how to report an offline or privacy concern.

Map coordinates will identify the viewed public area, rounded to an appropriate precision. We do not need or want the exact mounting coordinate, network address or hardware identity.

The map will also distinguish a public page being available from a camera being confirmed live. An HTTP 200 response only proves the page loaded. It does not prove current imagery is moving or fresh.

What the map cannot promise

Third-party cameras can go offline, change direction, become subscription-only or disappear without notice. Publishers can change their terms. Road or beach conditions can change after an image is captured.

Durban CCTV should therefore never promise:

• continuous availability;
• real-time accuracy;
• safety for swimming, surfing or driving;
• recording or evidence retention;
• coverage of an incident;
• ownership or operation of the third-party camera; or
• permission to download or redistribute the view.

The correct button is “Open on publisher website,” not “Watch our camera.”

Can a public webcam supplement security?

It may provide situational context. A business near the beachfront could use a public weather view to understand conditions, and a traveller can use i-TRAFFIC for current road information.

It should not replace a security system designed around the property’s own risks, retention, power, image quality and access control. A public camera can disappear at the moment it is needed, and the viewer has no control over its recording or maintenance.

For incident evidence, the relevant property still needs cameras aimed at the right scenes, recorded to a defined system and managed by an accountable owner.

The useful distinction

A public webcam answers: What does this place look like now?

A security CCTV system should answer: What happened, when did it happen, and can an authorised person retrieve reliable footage?

Sometimes one camera service contributes to both. Never assume that from the live page alone.

Durban’s public camera views deserve a useful, carefully attributed map. Building that map responsibly means linking only to intentionally public sources, respecting publisher rights and being honest about the difference between a scenic live view and controlled security evidence.