Docs / CAMZA.AI
Agree the boundary before the stream.
A camera evaluation should have a written data-handling scope before any stream or recording is shared. Identify the parties, processing location, permissions, retention and deletion procedure. This checklist describes the information to request; Camza’s final security packet, deployment commitments and legal terms still require confirmation and review.
UPDATED
Create a data inventory
- Continuous streams, selected clips and derived event metadata
- Camera credentials, user accounts and support access
- Diagnostic logs and any identifiers they contain
- Downstream messages, recipients and evidence links
Ask for the deployment-specific answers
| Area | Answer required |
|---|---|
| Purpose | What event is being evaluated and why? |
| Location | Where are processing and storage performed? |
| Access | Which people and services can see which data? |
| Retention | How long does each data type remain? |
| Deletion | How is deletion requested, verified and recorded? |
| Third parties | Which providers participate in this evaluation? |
Make identity features an explicit decision
The final Camza identity-features policy has not been verified. Do not assume facial recognition, face blurring or biometric processing is either present or absent. Resolve the actual feature set and permitted purpose in writing before the evaluation.
A few useful questions.
Can I try this on my own cameras?
Start with a compatibility request. Share camera models, firmware and the event you want to find. An evaluation needs an agreed scope before any camera access is arranged.
Is the website demonstration a product benchmark?
No. The sample demonstration uses illustrative scenes and predefined events. It does not measure accuracy, response time or compatibility on your cameras.
What should we agree before a pilot?
Agree which streams are in scope, who can access the data, where processing runs, retention and deletion, expected outcomes, and the person responsible for reviewing results.
YOUR CAMERAS. YOUR CONTEXT.
Start with one
useful question.
A camera inventory. An event to find.
A clear next step for your team.