1. Scope of API usage

CAMTECH AI uses Meta APIs for customer communication automation, appointment workflows, support operations, and approved transactional messaging in authorized client contexts.

• Business messaging and customer support flows.
• Booking confirmations, reminders, and service notifications.
• Client-authorized operational workflows with clear end-user context.

2. Consent and opt-in requirements

• Clients are responsible for lawful end-user opt-in before automated messaging starts.
• CAMTECH AI supports opt-in and opt-out flow design as part of implementation.
• Users must be able to stop automated conversations through clear opt-out paths.
• Emotion detection or sentiment profiling is not enabled by default and requires explicit written client approval plus lawful end-user consent where required.

3. Data handling principles

• Process only data required to deliver approved messaging workflows.
• Protect message content and metadata with platform and infrastructure controls.
• Do not use client or end-user channel data for unauthorized external model training.

4. Prohibited use

• No unsolicited spam or unlawful messaging.
• No prohibited content categories under platform rules and applicable law.
• No collection or exploitation of restricted sensitive data categories for unsupported use cases.
• No political, adult, or otherwise restricted campaign usage in conflict with platform policy or law.

5. Security and retention context

Meta-channel operational data is retained according to service necessity, legal obligations, and contractual context, typically within 12 to 24 months unless lawful exceptions apply.

Security controls include access restrictions, auditability support, and incident handling procedures aligned with CAMTECH AI governance.

6. Rights and requests

Rights requests related to channel interactions can be submitted through{' '} legal@camtech.ai and are handled through verification and lawful processing workflows.

CAMTECH AI coordinates with client account owners where controller responsibilities remain with the client organization.

7. Updates

This statement is updated when platform policy, legal requirements, or operational design materially changes.