Subprocessors

Our subprocessors include Microsoft, Amazon Web Services (AWS), and other service providers supporting the features you use. The providers involved depend on your selected services and deployment.

• Microsoft, including Microsoft Azure services.
• Amazon Web Services (AWS), for cloud infrastructure services.
• Other providers in the service categories described below.

Contact our team for the provider entities, services, and processing locations applicable to your account.

Skytells operates Relam as a governed platform. Subprocessors are engaged to perform defined functions on our behalf—not to bypass our access controls, memory settings, sharing rules, or model-routing policies. The providers involved in a request depend on enabled features, selected models, connected services, and deployment configuration. They may process only the data needed to perform their service for us.

Core service operation—including authentication, databases, object storage, background jobs, and Skytells-native model inference—runs on infrastructure controlled by Skytells.

Requests routed to Skytells-native models are processed on Skytells private network infrastructure. From the moment Skytells receives request content for those models, inference workloads are handled inside our controlled internal environment and are not exposed to the public internet for model processing.

When a request requires a third-party model, Relam routes it through enterprise deployments operated by leading cloud providers. Examples include Microsoft Azure OpenAI Service and comparable governed offerings from major AI infrastructure vendors. We do not route those requests through the mass-market public API products sold directly to general consumers for chat applications.

The specific provider, region, and deployment engaged for a request depend on the model selected, account configuration, and applicable plan. Provider processing is subject to our agreements and the provider's applicable terms.

• Hosting, databases, authentication, caching, and networking providers that operate the service and protect account data.
• Object-storage providers that store uploaded files and generated assets under access-controlled URLs.
• Payment providers that process subscriptions, invoices, and payment-method information.
• Search, media-generation, and specialty model providers selected to fulfill a specific enabled feature or request.
• Product analytics, error monitoring, and customer-support providers used to maintain and improve the service.
• Connected services that an account holder expressly authorizes, such as email, calendar, design, or knowledge-base integrations.

We assess subprocessors for the services they perform and require them to protect applicable personal data through contractual, technical, and organizational safeguards. Processing locations and transfer mechanisms may vary by provider and selected service. Organizations with a Data Processing Addendum may request deployment-specific details relevant to their account.

We may add, replace, or remove subprocessors as the service changes. For organizations subject to our Data Processing Addendum, material changes are governed by the notification and objection terms in the applicable agreement.

Organizations may request the current subprocessor details relevant to their deployment and enabled services by contacting our team through the contact page.