Counts leave the device. Video does not.
We count people. We do not identify them.
Four design rules.
Processing on the device
The counting model runs on the box at the screen, not in the cloud.
Video stays local
Video never leaves the device. There is no video archive to leak.
No identification
We do not recognise, name or follow individuals. Faces are not stored or matched.
Counts only
What reaches the dashboard is anonymous: how many, how long, per play.
Measurement should not cost a venue its customers’ trust.
Cameras in a store or café are only acceptable if the people in front of them are respected. Counting without identifying is how Gridcast gets proof of audience while collecting no personal profile of anyone.
Every venue and every law is different. If you have specific compliance questions, including under India’s data protection rules, take them to your own legal adviser, and ask us anything about how the system works.
Privacy questions
Do you store faces?
No. Faces are not stored or matched.
Does video leave the device?
No. Video is processed on the device and never leaves it.
What data do you collect?
Anonymous counts per play and per hour, such as people present and dwell time, along with proof of play.
Can an advertiser see individuals?
No. Advertisers see counts, never individuals.