Legal
Cam-Events AI handles operational guest data that deserves careful protection. This page is a practical summary of the safeguards currently used for pilot customers; it is not a security certification or a promise of uninterrupted service.
Last updated: September 3, 2026
Guest lists, RSVP responses, hotel allocations, transport assignments, and check-in records use encryption at rest in managed AWS services. Supported client and API connections use HTTPS/TLS in transit.
Platform access is limited to authorized personnel and application roles. Pilot customers should request the current architecture and control summary when evaluating specific contractual or regulatory requirements.
The platform supports role-based access for organizers, check-in staff, drivers, hotel teams, porters, and VIP shadows. Operational views are scoped by workspace, event, role, and assignment where the workflow supports it.
Administrative actions such as exports, campaign launches, and manual RSVP overrides are logged for audit review.
AI voice and IVR RSVP flows process guest phone numbers and call outcomes through configured telephony providers. Call metadata may include status, duration, transcript or response data when enabled for operational reporting; it is not sold to advertisers.
Organizers are responsible for obtaining appropriate consent before outbound voice campaigns, including compliance with applicable telecom and privacy regulations in their region.
Core services use managed AWS infrastructure, service logs, database backups, endpoint rate controls, and application audit records. Pilot support investigates reported incidents and communicates material issues according to the applicable agreement and law.
Pilot customers may request the current security summary, provider list, or data-processing terms. Any required certification, dedicated infrastructure, recovery objective, or service level must be agreed in writing before onboarding.