Oshy Role Bots · Terms of Service · Privacy Notice · Data Processing Agreement · Subprocessors

Subprocessors and third-party providers

Last updated 4 November 2026. This list forms Annex 3 of the Data Processing Agreement.

Subprocessors engaged by Oshylabs

ProviderServiceData involvedLocation
Vercel Inc.Web application hosting and operational logsAll data passing through the web application; logs with secrets and content redactedFunctions run in Stockholm, Sweden (arn1); global edge network for delivery
Supabase Inc.Managed PostgreSQL databaseAll stored workspace and account dataStockholm, Sweden (eu-north-1)
Resend, Inc.Account emails from Oshylabs (password resets, member invites)Recipient name and email address, workspace name, the email textIreland (eu-west-1)

Providers the Customer contracts with directly

These providers act under the Customer's own account and agreement. Oshylabs sends data to them only on the Customer's instruction (by adding a key or token and running a Bot), and they are not Oshylabs subprocessors.

ProviderServiceData involvedWhen
AnthropicAI model processing (Messages API) under the Customer's own API keyPrompts containing workspace content and model responsesEvery Bot run that uses a real model
GitHubRepository connector: read file list; open a draft pull request after an admin approves itRepository file list (not stored by Oshylabs); code and text in approved pull requestsOnly if the Customer connects a repository
The Customer's email provider (for example Google, Microsoft, Zoho)Sends approved emails and calendar invites from the Customer's own account over SMTPRecipients, subject, message text and invite details of each approved emailOnly if the Customer connects email
Slack or MicrosoftPosts approved messages to the Customer's channel through the Customer's webhookThe approved message textOnly if the Customer connects a channel

Not used

  • Other AI model providers: not supported.
  • Object storage: not used. Uploaded files are converted to text and not stored.

Changes

We give at least 30 days' notice of a new or replacement subprocessor by email to each workspace owner and by updating this page.