- FelbaCare may depend on hosting, database, payment, M-PESA/Daraja, email, SMS, push, analytics, security, AI, customer-support, storage, and professional-service providers.
- The live subprocessor register must name each provider, purpose, data categories, country, safeguards, retention, contact path, and replacement or exit procedure before publication.
- Payment-provider availability, settlement, reversal, chargeback, callback, and statement data may be governed by the provider's own rules and technical limits.
- No third-party provider should receive raw private member data, sensitive claim data, or AI-training data unless the product flow, lawful basis, contract, security review, and disclosure have been approved.
Third-Party Provider Disclosure
Hosting, database, payment, communications, analytics, AI, support, and professional-service provider categories.