A smartphone camera, an editing application, and an internet connection can turn an ordinary moment into viral content.
But from a privacy and engineering perspective, there is an important question:
When a creator records an identifiable person and publishes the footage, what responsibilities arise?
The Nigeria Data Protection Commission (NDPC) recently warned content creators against photographing or recording unsuspecting members of the public and publishing the content without consent. The Commission referenced street-based reality-style content and stated that processing images in such circumstances requires consent unless another lawful basis can be established.
Public Data Is Not Automatically Free-to-Use Data
Developers and creators should distinguish between information that is visible and information that can be freely collected, processed, and redistributed.
A person’s face, voice, or other identifiable features may constitute personal data. The fact that an individual appears in a public location does not automatically resolve questions about purpose, fairness, consent, or lawful processing.
The legal assessment depends on context. The NDPC’s statement should not be interpreted as a blanket prohibition on every photograph taken in public. However, creators should not assume that public location provides unrestricted permission to publish identifiable people for entertainment.
A Basic Privacy-Aware Content Workflow
A content production system could include a privacy review before publication.
This is a simplified conceptual workflow, not a substitute for legal advice.
What Developers Can Build:
If a platform supports user-generated video, developers can incorporate privacy-related features such as:
Consent Records
Store when and how a participant agreed to be recorded, where appropriate.
Face Blurring
Provide tools to obscure individuals who are not intended subjects of the content.
Review Queues
Allow moderators or content owners to review videos before publication.
Reporting Systems
Give individuals a clear way to report unauthorised or harmful appearances.
Audit Logs
Track changes to content, moderation decisions, and removal requests.
These features do not guarantee legal compliance, but they can support better privacy practices.
Consent Should Be Designed Into the Product
Consent should not be treated only as a checkbox added at the end of a project.
A responsible product design may explain:
What data is being collected.
Why it is being collected.
Where the content will be published.
Whether it will be monetised.
How a participant can raise concerns.
The level of information and consent required depends on the circumstances and applicable law.
Platform Accountability
The NDPC directed platforms including TikTok, X, and Meta to strengthen enforcement of community guidelines. It also warned that platforms could face sanctions for failing to respond promptly to harmful unlawful or unfair processing.
This creates an opportunity for developers to think beyond engagement metrics and consider privacy-by-design principles.
Practical Checklist for Creators and Developers
Before publishing content featuring identifiable people:
Identify the purpose of the recording.
Determine whether consent is required.
Explain the intended use to participants.
Avoid unnecessary personal information.
Consider blurring or anonymisation.
Provide a reporting or removal process.
Review applicable privacy laws and platform policies.
Digital professionals need skills in both technology implementation and responsible technology use. Training environments such as TEKHUB can support practical learning in areas including software development, cybersecurity, and digital technology.
Final Thought:
A technically functional content platform is not necessarily a responsible one.
When building tools for recording, publishing, and sharing content, developers should ask:
Can this system help users create freely while also protecting the people captured by the camera?
Top comments (0)