Who is responsible for camera data
Video from cameras usually contains personal data: people who can be identified by their face, clothing, or vehicle. Under the GDPR, the organisation that decides why and how cameras record is the controller of that data. When you run Agent, Vault, Hub, or Factory, that is you, not UUG.AI.
If UUG.AI hosts, operates, or supports a deployment for you and can access recordings or user accounts while doing so, UUG.AI acts as your processor. In that case we sign a data processing agreement with you, as required by Article 28 of the GDPR.
Self-hosted deployments
When you install and run the platform on your own infrastructure or in a cloud account you control, UUG.AI does not process your data. In that case UUG.AI is neither controller nor processor under the GDPR: recordings, metadata, and user accounts stay in your environment and never reach us.
This assumes all connections stay in your environment. Agent's default settings point to services operated by UUG.AI: the Hub cloud API, the MQTT broker at mqtt.kerberos.io, and the STUN/TURN relay at turn-fra1.kerberos.io. When you self-host, point these settings to your own services. If you keep using ours, for example to relay live video, UUG.AI processes that connection data for you and acts as your processor for it.
As the operator of a self-hosted environment, you are responsible for:
- who can access the environment and the data in it;
- securing servers, networks, storage, and credentials, and installing updates;
- backups, availability, and recovery;
- reporting personal data breaches to the authorities and to the people affected.
To the extent permitted by law, UUG.AI is not liable for unauthorised access to, or loss of, data in an environment that UUG.AI does not operate. The terms of your licence or service agreement apply.
If you give UUG.AI access to a self-hosted environment, for example during installation or support, we act as your processor for that access and agree it with you first.
Where your data lives
The platform is built to run where you choose: on edge devices, in your own data centre, or in a cloud account you control.
- Agent records on site, close to the cameras.
- Vault stores recordings on the storage you pick, such as on-premise object storage or a cloud bucket in a region of your choice.
- Factory runs an Agent for every camera on your own Kubernetes cluster.
- Hub can be installed in your environment, so accounts, metadata, and recordings never have to leave it.
Because you choose the location, you can keep data inside the European Economic Area and avoid international transfers altogether.
Controls that support GDPR compliance
These features help you apply the GDPR principles of data minimisation, storage limitation, integrity, and accountability. How you configure them remains your responsibility as controller.
Retention and deletion
With the cleanup service running, Hub automatically deletes recordings and related data once they are older than the retention limit set for each account, so footage is not kept longer than needed. Accounts without a limit are not cleaned up, so set one for every account. See Cleanup.
Access control
Give people access only to the cameras and features they need, with standard roles (owner, admin, editor, guest) and custom roles. See Roles.
Single sign-on
Connect Hub to your own identity provider through OpenID Connect, so accounts follow your joiner and leaver process. See SSO.
Audit trail
Owners and administrators can review who accessed or changed what, and whether it succeeded. See Audit events.
Face redaction
Blur faces in recordings before sharing them, for example when answering an access request without revealing other people. This is an optional feature that you switch on in your deployment. See Video editing and face redaction.
Tamper-evident recordings
When you configure a signing key, Agent signs every recording it makes, so you can prove it has not been altered. See MP4 verification.
What remains your responsibility
As controller you decide how the platform is used. Typically this means:
- Having a lawful basis and a clear purpose for each camera.
- Following national camera law. In Belgium this is the Camera Act of 21 March 2007, including pictograms and registering cameras with the police.
- Carrying out a data protection impact assessment (DPIA) where large-scale monitoring is involved.
- Setting retention periods that match your purpose.
- Answering requests from people who were filmed, such as requests for access or erasure.
We are happy to explain how the platform can support your assessment.
Data subject requests
When someone asks for footage of themselves, you can find the relevant recordings in Hub by date, site, and camera, redact other people with face redaction, and download or share the result. Who may download or share recordings follows the roles you assign. See Recordings.
If UUG.AI receives a request about data we process on your behalf, we forward it to you without delay and do not answer it ourselves.
Data processing agreement and security
If UUG.AI hosts, operates, or supports a deployment for you, we sign a data processing agreement that covers confidentiality, security measures, sub-processors, breach notification, and the return or deletion of data at the end of the contract.
To request a data processing agreement or ask about our security measures, email support@uug.ai.
Our website
This page is about our products. How UUG.AI handles personal data on uug.ai and learn.uug.ai is described in our privacy policy.