Skip to content
Studio previewSelf-host Studio locally.Run it

Legal · Kortyx Cloud

Cloud Subprocessors

Information about service providers supporting Kortyx Cloud.

Updated

Contents5 sections

Draft schedule

Kortyx S.L. (operator name supplied; registration not verified) has not yet published an approved production subprocessor schedule for Kortyx Cloud. This page intentionally names no unverified provider legal entity, location or contractual safeguard. It is a review draft, not a statement that Cloud has no subprocessors. Use only synthetic or non-sensitive staging data until the required agreements are completed.

What must be published

Before approved personal-data processing, the schedule must identify each provider’s verified legal entity, role and service, processing scope and data categories, relevant processing locations, and applicable transfer mechanism. Hosting, delivery, communications and other services must be reviewed against the actual Cloud deployment. Their final contracts and safeguards require operator confirmation.

Customer-selected services

Evaluation endpoints, application services and model providers selected by a customer depend on that customer’s configuration. They are not automatically Kortyx-appointed subprocessors. The parties must determine their roles, instructions and transfer arrangements for the intended processing. Self-hosted SDK/Studio operators maintain their own provider arrangements.

Changes and authorization

The finalized DPA must define subprocessor authorization, change notifications and objections before an approved schedule is used. No invented notice period or objection deadline is established by this draft. A change to the published schedule requires a new version; previous published versions remain available at their permanent URLs.

Related documents

The Cloud DPA at https://kortyx.io/cloud/dpa and Cloud Privacy Notice at https://kortyx.io/cloud/privacy describe the outstanding agreement and disclosure requirements. A verified private legal/privacy contact is still required; do not send confidential requests through public GitHub channels.