HomeSubprocessors

Subprocessors

Third-party service providers used to help operate ScaleAPIs.

Last Updated:April 23, 2026

Effective Date:April 23, 2026

Scope

This page identifies the third-party service providers that Scale APIs uses to help operate the ScaleAPIs platform and related services, including ProdaPic and ProdaDoc.

A subprocessor is a third-party service provider that may process personal data or other customer-related data on behalf of Scale APIs in connection with hosting, infrastructure, storage, or similar operational functions.

Current Subprocessors

Provider

Service area

Purpose

Data involved

Region

Railway

Application and API hosting

Hosts the ScaleAPIs website, related backend services, and product runtime environments

Account-related data where applicable, API requests, customer-submitted inputs, generated outputs processed by the service, logs, and technical metadata

Hosting regions configured by Scale APIs on Railway

Upstash

Managed Redis infrastructure

Provides managed Redis services used for transient application state, rate limiting, queueing, job metadata, replay protection, and related operational controls

Request identifiers, transient operational state, quota and rate-limit data, job metadata, cache metadata, and related technical metadata

Managed regional deployments selected by Scale APIs

DigitalOcean Spaces

Object storage

Provides object storage used for bounded output-storage and delivery workflows where enabled for Scale APIs services

Generated outputs, output metadata, delivery-related artifacts, and related technical metadata

DigitalOcean Spaces regions selected by Scale APIs

How We Use Subprocessors

Scale APIs uses subprocessors only for operational purposes such as:

hosting and running the platform and product services

storing bounded operational state or delivery-related data

supporting output handling and customer-requested storage workflows

maintaining reliability, abuse prevention, and service continuity

Scale APIs does not publish subprocessors on this page as a placeholder for tools that are not actually in use. This list is intended to reflect the live operational vendor stack used for the covered services.

Updates

Scale APIs may update this subprocessor list from time to time as vendors or service architecture change.

The current version of this page reflects the subprocessors used by Scale APIs at the time of publication.

Questions

Questions about this subprocessor list may be sent to:

privacy@scaleapis.com

Questions about this document?

If you have questions about this policy, contact us at legal@scaleapis.com.