1. When a third party is used
EMEGA connects to a third party only when required for hosting or when an authorized organization enables the relevant feature. A provider receives only the data reasonably needed for its task, subject to contracts, configuration, and applicable law.
2. Typical service categories
- Hosting and infrastructure for the application, database, network, backups, and operational continuity.
- Official communication providers for Messenger, Instagram, WhatsApp, Telegram, email, SMS, or another enabled channel.
- AI providers selected for grounded drafting, classification, extraction, translation, or summarization.
- File, media, email-delivery, queue, monitoring, error-tracking, and backup services when configured.
- Customer-selected school information, learning, payment, identity, or reporting systems connected through an approved integration.
3. Independent providers
Some connected platforms act under their own terms and purposes rather than solely as EMEGA subprocessors. For example, a messaging network may independently manage accounts, delivery, abuse prevention, and legal requests. The organization should review each provider’s documentation.
4. Selection and oversight
The operator should assess security, privacy, processing locations, access, retention, breach terms, deletion support, and contractual safeguards before enabling a provider. Access should be limited, credentials protected, and provider status reviewed periodically.
5. Changes
Material changes to active subprocessors should be recorded and communicated according to the customer agreement and applicable law. Customers may raise a documented objection through the contractual or support contact where that right is provided.
6. Current deployment record
The authoritative list for a customer is the active provider and hosting record maintained by the EMEGA operator and the customer’s connected-channel settings. A feature appearing in the interface does not mean its external provider is active.