Frequently asked questions

Clear answers.
Before the first camera.

What to know about compatibility, analytics, privacy and a practical rollout.

Can I use my existing cameras?

Often, yes. 4cecam is designed around compatible RTSP camera streams and on-site hardware. We check camera codecs, main/sub streams, network access and available compute during the pilot. Compatibility is verified rather than assumed.

Is 4cecam only for retail?

No. Healthcare is a primary focus, with use cases across medical facilities, clinics, retail, restaurants, warehouses, farms and factories. Camera placement, policies and workflows are tailored to each environment.

Where can cameras be used in a healthcare facility?

The healthcare approach is limited to waiting rooms, entrances and common areas—never exam or treatment rooms. Plan coverage to avoid clinical spaces, exposed records and other unnecessary sensitive detail.

Is 4cecam HIPAA certified?

We do not claim HIPAA certification or automatic compliance. Healthcare deployments require a documented assessment, appropriate agreements where applicable, access controls, audit logging, retention rules and validation by your privacy and security team before use.

What can I use today, and what is planned?

The current pilot supports live viewing, local recording playback, on-device person detection and configurable inbound line-cross counting. POS/transaction integration, 30-day cloud playback, wait-time analytics and expanded fleet management are planned capabilities; scope and availability are confirmed before a rollout.

How does inbound counting work?

A confirmed person moves from an approach zone A into an inside zone B within the configured time window. Reverse movement is ignored. Each camera can have its own line configuration. Real walk tests are required to calibrate placement and direction.

Does video leave the location?

Recording and detection run on-site. Authorized remote viewing transmits video when it is requested. An offsite recording tier is planned separately; remote viewing alone is not a backup.

Do I need to open inbound ports?

The pilot uses an outbound tunnel for remote access rather than public inbound port forwarding. The application still requires authentication. Network and access design are reviewed for each deployment.

How long is video retained?

Local retention depends on storage, camera settings and your deployment policy. The pilot is configured for seven days locally. A 30-day cloud playback tier is planned and must be separately scoped; it is not a current default.

Are there per-feature upcharges?

Our commercial direction is a clear, agreed platform scope without charging to unlock individual features. Final pricing, hardware, cloud storage, support and integration work are documented in a proposal; no public price or unlimited-storage promise is implied.

Can I manage multiple cameras and locations?

The app discovers configured cameras dynamically. The site architecture is designed for repeatable deployments, with broader multi-location and fleet management on the roadmap. We agree the rollout scope before deployment.

How do I request a demo?

Use the contact page to prepare a demo inquiry in your email app. Include your industry, number of locations and camera count. Do not include passwords, footage, patient information or other sensitive data.

A clearer next step

Still have a question?

Tell us about your operation and what you need to understand.

Request a demo