Subprocessors

Every third party we use to help run DivineAPI, and where each one is located.

Last updated: 22 September 2026

A subprocessor is a third-party company we use to help run DivineAPI, and which may process customer data as part of that. We publish this list so customers can review it before signing, and we notify customers of changes before a new subprocessor starts handling their data.

Infrastructure (all in India)

Subprocessor Purpose Data processed Location
Amazon Web Services Primary database and storage Account records, API usage records India (ap-south-1, Mumbai)
DigitalOcean Application and API hosting API requests in transit, request logs Bangalore, India (blr1)

Chatbot endpoint only

The chatbot endpoint may route requests to one or more third-party large language model providers. We may use any of the providers listed here, and we may change between them for quality, cost or availability reasons without that constituting a new subprocessor.

Subprocessor Purpose Data processed Location Applies to
OpenAI Generating chatbot responses The question sent to the chatbot endpoint United States Chatbot endpoint only
Anthropic Generating chatbot responses The question sent to the chatbot endpoint United States Chatbot endpoint only
Google (Gemini) Generating chatbot responses The question sent to the chatbot endpoint United States Chatbot endpoint only

None of these providers use data submitted through their APIs to train their models, and none retains it for longer than 30 days.

Where we run models on our own infrastructure in India, no third party is involved and no data leaves our environment.

This applies only if you call the chatbot endpoint. Every other DivineAPI endpoint — horoscope, natal, panchang, numerology, compatibility, reports and all other calculation endpoints — is served entirely from our own infrastructure in India, and no data from those endpoints reaches any AI provider.

Business operations

Subprocessor Purpose Data processed Location
Stripe Payment processing and billing Billing contact details, payment records. No API request data. United States, EU
Zoho Customer support (live chat, email) and demo bookings Support conversations and booking details you choose to send us India
Mailchimp (Mandrill) Sending transactional and account emails Recipient address and email content United States
Sentry Error monitoring Technical error reports, which may include request metadata United States

Changes to this list

We will update this page and notify affected customers by email before adding a subprocessor that handles customer data. Customers may object to a new subprocessor by contacting admin@divineapi.com.

Related: the Data Processing Agreement and the Trust & Compliance page.