Most retailers install a camera to count foot traffic and never think about it again. The problem is that the moment a camera records an image of an identifiable person, you are no longer just counting shoppers. You are collecting personal data, and that pulls your store into the scope of privacy laws like GDPR and CCPA.
That is an uncomfortable surprise for a lot of store owners. You wanted a number: how many people walked in today. What you got was a data protection obligation, complete with signage rules, retention limits, and the risk of a fine if you get it wrong.
The good news is that counting foot traffic and staying compliant are not at odds. You just need to understand what the law actually asks for, where camera-based counting creates exposure, and why a GDPR-compliant people counter does not have to capture a single identifiable image. Here is how it fits together.
What Retail Privacy Laws Actually Require
Under GDPR, personal data is any information relating to an identifiable person. A video frame that shows someone's face qualifies. So does footage clear enough to recognize a person by their build, clothing, or gait. Once you are processing that kind of data, GDPR expects you to have a lawful basis for it, to tell people it is happening, to keep it only as long as you need it, and to honor requests from individuals who want to see or delete their data.
CCPA works differently in the details but lands in a similar place: California consumers have rights over personal information a business collects about them, and imagery that can identify a person can count. Retailers operating across regions often end up managing the strictest standard that applies to any of their stores.
None of this is meant to stop you from understanding your own traffic. Regulators are not worried about a store knowing that 400 people visited on Saturday. They are worried about businesses quietly building records tied to identifiable individuals. The distinction between the two is where compliance lives, and it is the distinction most counting hardware ignores.
Why Camera-Based Counting Is a Compliance Risk
A camera counts people by recording them. Even if your software only cares about the head count, the device is still capturing images of identifiable shoppers, and that footage is personal data the moment it exists.
That creates a chain of obligations most retailers never signed up for. You need clear signage telling customers they are being recorded. You need a defined retention period and a way to actually delete footage when it expires. You need to be able to respond if a customer asks what you hold on them. And you need to secure the footage against breaches, because a leak of in-store video is a reportable incident.
Get any of it wrong and the penalties are not trivial. GDPR allows fines of up to 20 million euros or 4% of global annual turnover, whichever is higher. Beyond the legal exposure, there is the trust cost: shoppers increasingly notice and care when a store is filming them, and "we only use it to count" is a hard message to put on a door sign.
For a fuller breakdown of how the two technologies stack up on accuracy and cost, not just privacy, see our comparison of thermal vs. camera people counters. The short version: cameras carry compliance baggage that thermal counting simply does not.
How Anonymous Counting Stays Compliant
Here is the key idea. If a device never captures data that can identify a person, most of the privacy burden disappears, because there is no personal data to protect in the first place.
That is how thermal sensing works. Instead of recording images, a thermal people counter detects body heat and uses machine learning to distinguish shoppers from one another as they pass through an entrance. It sees heat signatures, not faces. There is no video, no photo, and nothing that ties a count back to a specific individual. The output is a number, which is exactly what you wanted from the start.
Because the data is anonymous by design, a thermal counter sidesteps the signage, retention, and access-request machinery that cameras drag along. Dor's sensors are 100% anonymous and GDPR-compliant for this reason, and the ML that powers them was built by former Apple engineers to match camera-level counting accuracy without ever capturing an image. More than 2,000 stores run on that approach today.
Privacy-first counting also removes a practical deployment barrier. Retailers in privacy-conscious markets, or inside malls and venues with their own data rules, can install anonymous counters without a legal review of what the device records, because it records nothing identifiable.
A Privacy Compliance Checklist for Foot Traffic Data
Whatever hardware you use, run your foot traffic setup through these questions:
- Does the device capture identifiable images? If yes, you are processing personal data and GDPR or CCPA obligations apply.
- Do you have a lawful basis and clear signage? Camera-based counting needs both. Anonymous counting generally sidesteps this.
- Is there a defined retention period? You should know exactly how long data lives and how it is deleted.
- Can you honor a data subject request? If a customer asks what you hold on them, you need an answer.
- Is the data secured against a breach? Stored video is a liability; a head count is not.
- Would you be comfortable putting your data practice on a sign by the door? If the honest answer is no, that is worth sitting with.
If you are choosing hardware for the first time, our guide to people counters for retail walks through the sensor types, costs, and tradeoffs in more detail. (This guide is general information, not legal advice; confirm your specific obligations with qualified counsel.)
Getting Accurate Counts Without the Privacy Headache
The reason retailers reach for cameras is usually accuracy. They assume a privacy-safe counter must be a worse counter. That tradeoff no longer holds. Thermal sensing paired with modern machine learning matches the accuracy retailers expect from cameras, without the images that create the compliance problem in the first place.
That means you can track your conversion rate, spot your peak hours, and staff against real traffic, all the things a people counter is actually for, without taking on a data protection project you never wanted. If you want to see what your store's traffic looks like without collecting a single identifiable image, Dor counts anonymously out of the box, installs in minutes with no IT, and stays compliant by design.
Counting your shoppers should not mean surveilling them. With anonymous counting, it doesn't have to.