Sub-processor List
Effective date: 1 June 2026
Last updated: 1 June 2026
SovereignEG uses the following third-party services to operate the Service. Changes to this list are communicated to customers at least 30 days before the new sub-processor begins processing data.
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Cloud infrastructure provider | Application hosting (compute, storage, networking) | Account data, usage metadata, billing records | Egypt |
| Managed PostgreSQL (TimescaleDB) | Primary database | Account data, usage metadata, billing | Egypt |
| Managed Redis | Caching, rate limiting, session speed layer | Session cache, rate-limit counters | Egypt |
| Resend | Transactional email (verification, password reset, invites) | Email address | United States |
| Upstream model providers | AI inference (when a model is backed by a third-party provider) | Request payload required to generate the response (not stored after processing) | Provider-dependent — see Provider Disclosure |
Payment processing is not yet live on the public Service. When card or wallet payments launch, this list will be updated before any payment sub-processor goes live.
Subscribing to Changes
To receive notifications when this list changes, email support@sovereigneg.com with the subject line Sub-processor notifications.
Objecting to a Sub-processor
If you object to a new sub-processor, contact support@sovereigneg.com within 30 days of the notification. We will work to address your concerns. If we cannot resolve the objection, you may terminate your account per the Terms of Service.