Oshyn Inc uses service providers for hosting, storage and recovery, remote browsing, AI processing, search, notifications, email, payments, and other enabled Service functions. A provider is Oshyn's subprocessor where Oshyn engages it to process personal data on a Customer's behalf. Some providers also have separate responsibilities for their own processing.
Confidential provider information
Oshyn supplies affected Customers with a confidential register identifying the providers, their functions, information processed, relevant locations, and applicable processing arrangements. It includes the relevant downstream processing chain for managed AI services. Customer-specific schedules and the applicable agreement govern authorization, restrictions, and safeguards.
The named register is supplied directly to affected Customers rather than published on this page. Customers may request a current copy or raise a provider question through the contact below. Confidential delivery does not replace or reduce Oshyn's disclosure, authorization, or notice obligations. Principal hosting in one country does not mean every provider or personnel access remains there. A no-training restriction is different from a zero-retention commitment.
Customer-selected services
For model services, storage accounts, connectors, identity services, and other integrations independently selected and contracted by Customer, the providers are not subprocessors of Oshyn merely because ContextCloud transmits an authorized request. There is no exhaustive list of these services: Customers may connect supported services and custom integrations.
The relationship depends on the actual account and service arrangement, not the provider's name or the existence of an API key. Customer is responsible for its own provider arrangement and authorized instructions. Oshyn remains responsible for its own handling of Customer Data; a provider Oshyn engages to perform the Service remains subject to its applicable provider duties.
Notice of changes
Oshyn will update the applicable register before a provider change takes effect. For Customers with an executed DPA requiring 30 days' advance notice, Oshyn will give that notice before a new or replacement subprocessor starts processing, with the DPA's opportunity to object. This includes changes in managed model routing where the DPA requires notice. Updating this page or the register alone does not satisfy a separate obligation to notify Customer.
Contact
Oshyn Inc · Privacy Enforcement Representative · privacy@contextcloud.works