Legal

Privacy policy

Camera Hub and your data: what stays on the machine, which is all of it.

Last updated: 2 September 2026

1. Who processes the data

The controller is Ubiquitous S.r.l., Via Ariosto 25, 00185 Roma, Italia, P.IVA 17584931004. For anything about this policy, write to [email protected].

In practice there is very little to process: the application does not send us anything, so the only personal data we hold about a user of Camera Hub is whatever they put in an email to us.

2. What the application stores, and where

Camera Hub keeps the cameras you add in a file on your own machine, under $XDG_DATA_HOME/camera-hub/ — usually ~/.local/share/camera-hub/cameras.json. It holds the address, port and credentials of each camera, because it needs them to talk to the camera on every connection. Preferences live in GSettings, in the usual per-user location.

Recordings are written where you tell the application to write them, and nowhere else.

These are ordinary files owned by your user account. They are covered by whatever backup and disk encryption you already use, and by nothing we provide. We never see them.

3. What leaves the machine

Traffic to the cameras on your own network, and nothing else:

• a WS-Discovery probe to the multicast address 239.255.255.250:3702, which is how ONVIF cameras announce themselves;
• ONVIF SOAP requests and RTSP video, to the addresses of the cameras you added.

There is no telemetry, no crash reporting and no analytics. The application does not report anything about you, about your cameras or about how you use it, and it works with the machine disconnected from the internet entirely.

4. The update check

There is one exception to the paragraph above, and it is the only connection the app makes to us. Camera Hub is in no distribution's archive and not on Flathub, so nothing else on the machine will ever tell you a new version exists. Once per launch, the app fetches a single static file:

https://camerahub.synapsi.ai/appcast.json

It holds the current version number and the address of the download page. The request carries no identifier, no version and no query string — the comparison happens on your machine, on the answer. What our server sees is a request for a file and the address it came from, which is the same thing it sees when you download a package, and it goes into the same web logs described below.

It can be turned off in Settings → Updates, and when it is off the application makes no connection to us at all.

5. Cookies and this website

This site sets no cookies and carries no analytics or third-party scripts. Its fonts are served from this domain rather than from a font provider, so visiting a page tells nobody but our own server that you did.

The server keeps standard web logs — the request, the time, and the address it came from — for security and troubleshooting, and they are deleted on a rolling basis.

6. Downloading the application

Downloading a package, or adding one of the repositories, is an ordinary HTTP request to this domain and appears in those same logs. Adding a repository means your package manager will check it for updates on its own schedule; that check is also just a request for a file, and it carries nothing about you beyond what any HTTP request carries.

7. Your rights

Under the GDPR you may ask for access to, correction of or erasure of personal data we hold about you, and you may complain to the Garante per la protezione dei dati personali. Since the only data we can hold is an email you sent us, in practice a request means asking us to delete that correspondence, which we will do.

8. Changes

If this policy changes, the date at the top changes with it. It would have to be because the application started doing something it does not do today, and that would be announced in the changelog as well.