Providers supporting AstrologyAPI
AstrologyAPI uses third-party infrastructure and AI services to deliver its products. This page describes our principal providers and their functions. The applicable provider, contracting entity, data access and processing location depend on the product and arrangement.
A service-specific subprocessor register forms part of the signed Data Processing Agreement. This overview does not by itself authorise a provider for a particular customer's processing or establish an exhaustive contractual register.
Principal infrastructure and AI providers
| Provider or service | Function | Location and scope |
|---|---|---|
| Amazon Web Services (AWS), including S3 | Cloud infrastructure and object storage | Our AWS and Google Cloud infrastructure uses India and US regions at an overall level. Product-specific storage and access arrangements require a service-specific assessment. |
| Google Cloud | Cloud infrastructure | India and US regions form part of our overall cloud infrastructure. This is not an exclusive per-product residency commitment. |
| Cloudflare, including R2 | DNS, website hosting and object storage | Processing depends on the Cloudflare service and configuration. This page does not assign all Cloudflare activity to India or the US. |
| OpenAI | AI processing for relevant features | One of our main AI providers. Inputs and service-specific arrangements depend on the feature and integration. |
| Gemini | AI processing for relevant features | One of our main AI providers. Inputs and service-specific arrangements depend on the feature and integration. |
AstrologyAPI never trains models on user data. We prohibit AI providers from using customer data for their own evaluation. Provider-specific retention, human review, safety monitoring and model-use arrangements are separate matters to assess for the intended service. Read the AI & image data notice.
Website tools and independent services
Our website also integrates Google analytics and tag-management scripts and Intercom support. See the Cookie Policy. These website activities are distinct from the processing of customer API inputs.
Payment services, customer-managed integrations and third-party AI clients may act under their own terms and privacy notices. A service is not automatically AstrologyAPI's subprocessor simply because a customer connects it to an AstrologyAPI integration.
Contractual authorisation and changes
For processing covered by a DPA, the executed agreement determines the authorised subprocessors, notice route and objection process. Refer to that agreement for the arrangement applicable to your account. This page does not create a new notice period or replace an agreed approval process.
Before agreeing a DPA, the parties identify the services, relevant provider legal entities, processing locations and applicable transfer arrangements. The public infrastructure overview alone does not execute an international-transfer instrument or guarantee a particular residency configuration.
Request service-specific information
Email [email protected] with your organisation's name, the product or endpoint families you intend to use, and any subprocessor, location or transfer requirements. The DPA page explains how contractual processing terms and schedules are agreed.