Updated 31 October 2026
Privacy and deployment
This notice explains the website’s pilot enquiries and the current versus intended handling of store data. A pilot needs its own agreed scope and data arrangements.
Why we ask for enquiry details
We ask for your name, email, organization and operating question to assess a pilot and follow up. Store count and camera notes are optional. Do not send footage, credentials or sensitive personal information.
Access and service providers
Pilot enquiries are for Zujaj’s authorized follow-up team. Contact email forwards through Cloudflare to Ali’s verified inbox. Attio connection is being prepared; it is not active in this local preview. No enquiry contents are sent as marketing analytics.
Retention and deletion
No fixed automatic expiry is set for enquiries. We keep details while they remain necessary for pilot evaluation and follow-up, subject to deletion requests and applicable requirements. Contact hala@zujaj.ai to request access, correction or deletion; information no longer needed for its purpose should be removed.
Current recording pilot
Recording files, reference images and review material stay local. Configuration and pilot metadata can reach the workspace; these are not accepted analytical results.
Know what leaves the store.
The intended design keeps continuous video on site while selected operational records synchronize. Evidence access depends on authorization and available retention.
Footage and evidence access
Current recording work keeps raw files and review material local. The intended platform design synchronizes selected operational records, with evidence access handled separately. Availability, permissions and retention must be agreed for each pilot. No continuous-video cloud service is promised.
Connectivity and freshness
Local buffering and later synchronization are intended architecture, not a verified offline guarantee. Connection loss can delay or interrupt observations. Missing or stale coverage must stay visible, and an unknown value is not zero.
Permissions and audit visibility
The workspace uses organization and store permissions. Evidence access requires appropriate authorization. The pilot agreement must identify access roles, audit visibility and the records available for review; no certification or blanket compliance guarantee is claimed.
Backups, removal and responsibilities
Product backup and deletion schedules must be agreed before a pilot. The store must have the right to use its cameras and recordings and nominate a person to support evaluation. Local preview test data is separate from customer and product records.
Questions or privacy requests
Contact Zujaj at hala@zujaj.ai. The legal entity and final pilot terms must be confirmed before commercial launch.