Privacy Policy

To deliver automated multi-tenant messaging infrastructure and execute server-side AI workflows, we manage the following datasets:

• Account Credentials: Profile metadata including names, email communications, and administrative account configurations.
• Meta API Configurations: Cryptographic long-lived System User tokens, WhatsApp Business Account IDs (WABA IDs), and physical Phone Number IDs.
• Communication Logs: Webhook request payloads, text tracking parameters, and delivery state metrics (sent, delivered, read receipt indicators).

Data ingestion is restricted to functional processing operations required to maintain our microservices:

• Validating incoming HTTP validation headers from Meta edge routing instances (`hub.challenge` tokens).
• Isolating client message queues to ensure strict relational multi-tenancy rules inside our PostgreSQL database schema.
• Routing inbound text strings to designated Large Language Model pipelines to compute automated client responses.

All permanent credentials, security mappings, and operational keys are maintained under high-grade protective measures on our cloud instances. Production transactions enforce end-to-end cryptographic transport protocols including HTTPS and TLS layers. Data is retained strictly as necessary to populate your reporting interfaces or to preserve execution logs.

Our database layer mirrors individual field schemas to fulfill requirements for the Meta Developer platform. Information processing works directly via the cloud infrastructure rules to stream live API calls. No client information assets or session tokens are shared across unauthorized tenant parameters.