1. About this list
1.1. DIVAI LLC (“DIVAI,” “we,” “us”), an Alaska limited liability company (Active / Good Standing), uses the third-party providers below (“subprocessors”) to deliver the DIVAI service at divai.ai and app.divai.ai. Contact: privacy@divai.ai.
1.2. This list states, for each provider: its purpose, the categories of data it may process, and an honest status label.
1.3. Status labels used in this list:
- Active — verified live at the time of publication.
- Under integration — being connected; not yet processing customer data in production.
- Planned — not yet active — intended for future use; not processing customer data.
- To be determined — provider not yet selected.
2. Subprocessor list
| Provider | Purpose | Data categories | Status |
|---|---|---|---|
| Hostinger | Website hosting (divai.ai) | Website visitor data: IP addresses, request logs, contact-form submissions | Draft item pending confirmation before activation. |
| Render | Application hosting (app.divai.ai) | Application data in transit and at rest on the hosting tier: account identifiers, request logs, IP addresses; application payloads may include customer content and AI prompts/responses | Draft item pending confirmation before activation. |
| Supabase | Primary database and file storage | Core store of account data, project content, files, Project Brain memory, and related records | Draft item pending confirmation before activation. |
| Clerk | Authentication and user identity management | Names, email addresses, authentication and session data, device data | Draft item pending confirmation before activation. |
| Expo / EAS (Expo Application Services) | Mobile app build infrastructure (builds, signing support, updates) | Build logs and application bundle contents; limited personal data, if any Draft item pending confirmation before activation. | Under integration — mobile experience planned |
| OpenRouter | AI request routing to underlying AI model providers | Prompts, messages, files, and related context included in AI requests; completions returned | Draft item pending confirmation before activation. |
| Underlying AI model providers (via OpenRouter) | AI model inference for DIVAI features | Prompt content and completions, as routed per request | Provider identities vary by routing. They are disclosed where required. Draft item pending confirmation before activation. |
| Google Analytics (GA4) | Website and product analytics | Pseudonymous identifiers, IP addresses, device and usage data — only after consent | Planned — consent-gated; not loaded before consent Draft item pending confirmation before activation. |
| Stripe | Payment processing | Billing name, email, billing address, payment metadata; card data handled by the processor, not stored by DIVAI | Planned — not yet active. Payments are not live. |
| Email service provider | Transactional and service email | Recipient names and email addresses; message content | To be determined — provider not yet selected; will be added to this list before use |
3. Rules that apply to all subprocessors
3.1. Sensitive-data routing. Sensitive data is routed only to approved routes, under our data classification, data-processing-agreement, retention, and least-data rules. No provider receives data outside its stated purpose and data categories.
3.2. No zero-retention claims. We do not claim zero data retention for any provider, AI route, or model. No such claim is made anywhere in our customer-facing documents, and none may be made without exact-route proof.
3.3. Provider abstraction. DIVAI selects providers and AI models internally. Customers interact with DIVAI by default. This list, and any required processor disclosures, remain available.
3.4. Agreements. We intend to have data-processing agreements (or equivalent terms) in place with each provider that processes personal data, before that provider processes customer personal data in production. Draft item pending confirmation before activation.
4. Changes to this list
4.1. We update this list when a provider is added, removed, or when a provider’s data scope materially changes.
4.2. We give advance notice of changes before a new subprocessor begins processing customer personal data. Draft item pending confirmation before activation.
5. International transfers
5.1. Some providers may process data in countries other than your own. Where required, transfers are intended to be covered by appropriate safeguards, such as Standard Contractual Clauses and the UK addendum. Draft item pending confirmation before activation.
6. Contact
6.1. Questions about this list: privacy@divai.ai.