Leash

Service providers and subprocessors

Last updated: September 2, 2026

This page identifies external services visible in the current Leash product and deployment configuration. A provider's legal role may be processor, subprocessor, or independent controller depending on the service and customer relationship. The list is not a certification or a promise that every optional integration is enabled for every account.

ProviderPurposeData involved
Google Cloud PlatformHosted application and API infrastructureCloud account, device, security-event, approval, organization, and operational data needed by the deployed service
OpenAIManaged Leash AI safety evaluation and Business company-name extractionRelevant supported action context for a Cloud evaluation, or public company-site signals used to identify a new workspace
Lemon SqueezySubscription checkout, billing, and merchant-of-record servicesBilling contact, subscription, order, and payment-related information
Google AnalyticsPublic website analyticsPage, referral, approximate location, browser, and device analytics described in the Privacy Policy
Google, Microsoft, and GitHubAccount sign-in where the user selects one of these identity providersAuthentication identifiers, name, email, and provider metadata returned by the selected sign-in flow
GitHubPublic source and official release distributionPublic repository and release data; download requests are also subject to GitHub's own service terms and logs

Changes to this list

We update this page when a material hosted dependency changes. Business customers with contractual notice requirements should confirm those terms in writing; this public page alone is not a guaranteed advance-notice service. Questions can be sent to privacy@openleash.com.

Data processing agreements

Leash does not currently publish a pre-signed DPA template. If your organization requires a DPA, contact privacy@openleash.com before sending production organization data and confirm the applicable terms in writing.

Related information