Retail analytics with clear data boundaries.
CountPort is designed to process camera streams on-site and report aggregate store analytics. This page summarizes the posture buyers usually review first.
What CountPort processes
Compatible camera streams are analyzed to produce counts, movement, zones, dwell, queue, and conversion-related analytics.
What CountPort stores
Plans may store analytics records such as counts, timestamps, zone events, and aggregate reports. Retention depends on plan and deployment.
What cloud sync is for
Cloud sync is designed for analytics reporting across locations. Raw video upload is not part of the normal analytics path.
Facial recognition boundary
The retail analytics described on this site do not require facial recognition. CountPort is designed around anonymous store behavior.
GDPR review
Customers should review CountPort as part of their own data-protection obligations, signage, retention, and vendor documentation.
EU AI Act review
Classification and obligations can depend on deployment details. We provide architecture and product information for customer review.
Questions to answer before rollout.
Will shoppers need signage?
Most retailers should expect to disclose camera analytics in-store according to their local requirements and internal privacy policy.
Can CountPort run without cloud reporting?
Yes. CountPort is designed for on-site processing, and cloud sync can be disabled where local-only operation is required.
Does CountPort identify named shoppers?
The product described on this site is built for anonymous retail analytics and aggregate reporting, not named shopper identification.
Where do security documents come from?
Use the contact page and select security review. We can route requests for architecture details, vendor review material, and data handling questions.
Need a security or privacy review?
Send the request through the contact form and choose security and privacy review.
Contact us