IoT data ownership and privacy: cameras, trackers and staff

When you install cameras, GPS trackers or sensors, you are collecting data, and some of it is about people. The plain answer to "who owns it" should be: your business, under a written agreement that says so, with the right to export and delete it. The harder question is how to use data about staff and customers fairly. Monitoring that people know about, for a clear business purpose, kept no longer than needed, is the safe direction. Secret or open-ended monitoring is not.

I am not a lawyer, and rules on data protection, workplace monitoring and recording people can change. Treat this article as practical guidance, and check the details for your situation with a lawyer.

Three kinds of IoT data

It helps to sort what your devices collect into three groups:

• Machine and environment data. Temperature, humidity, fuel level, electricity use, machine running time. Usually low risk for privacy, though still commercially sensitive.
• Location and activity data. GPS tracks of delivery bikes, door-open logs, attendance taps. These often show where a specific person was, and when.
• Images and audio. CCTV footage, and any device that records sound. This is the most sensitive, because it captures faces, conversations and behaviour.

The further down this list you go, the more care you need.

Who owns the data?

Many systems send data to a cloud platform run by the vendor. Before you sign, get clear written answers to these questions:

• Does the data belong to my business?
• Can I export all of it, in a common format such as a spreadsheet file, whenever I want?
• What happens to my data if I stop paying, or the vendor closes?
• Who at the vendor can see it, and for what reason?
• Is it ever shared with, or sold to, anyone else?
• Where is it stored, and how is it backed up?

If a vendor cannot answer plainly, treat that as a warning. When I build a system, I prefer set-ups where the business itself holds the accounts and passwords for its own data, not the developer.

Monitoring staff fairly

Cameras and trackers can protect stock, staff and customers. Handled badly, they can also damage trust and drive good people away. A few principles:

1. Tell people. Explain in writing what is monitored, where and why. Put clear signs where cameras are.
2. Have a real purpose. "Security of the warehouse" or "knowing when deliveries arrive" is a purpose. "Seeing what everyone is doing all day" is not.
3. Respect private spaces. No cameras in toilets, changing areas, prayer rooms or rest areas. Do not record audio by default.
4. Track work, not lives. A tracker on a company motorbike during working hours is different from tracking a rider's personal phone or their evenings.
5. Limit who watches. Footage and location history should be visible to a small, named group, not forwarded around WhatsApp groups.
6. Let people raise concerns. Give staff a way to ask questions or object without fear of losing their job.

Some of these may be legal requirements where you operate. All of them are good practice regardless.

Customers and visitors

People walking into a shop, clinic or showroom should see a notice that cameras are recording. Footage of customers should be used for security and safety, not posted online or used to embarrass anyone. If a customer asks about footage that involves them, have a calm process for handling it, and take advice before releasing recordings to anyone outside the business.

Keep less, for less time

The simplest privacy protection is not keeping data you do not need:

• Decide how long each type of data is kept, and set the system to delete it automatically after that.
• Keep summaries, such as daily averages or trip totals, longer than raw footage or detailed tracks.
• Remove access promptly when staff leave.
• Protect devices and accounts with strong passwords and regular updates. The basics are in IoT security basics.

A checklist before you install

• What exactly will this device record, and why?
• Who has been told, and how?
• Who can see the data, and how is access controlled?
• How long is it kept, and how is it deleted?
• Does the contract say the data is ours, with the right to export it?
• Have we checked the legal side with a lawyer?

If you are planning GPS tracking for delivery vehicles or other monitoring, these questions belong in the design from the first day. The IoT development service page explains how I approach projects, and you can get in touch to talk through yours.