Effective date: 2026-09-24
To support the delivery of Sleev’s hosted control-plane services, account management, organization administration, and subscription billing, Sleev Labs Inc. (“Sleev”) engages third-party service providers (“Subprocessors”) that may process Customer Personal Data.
This page describes service providers supporting Sleev’s hosted services and the subprocessor notice process under our Data Processing Addendum (DPA). A provider’s role depends on the processing it performs under the applicable agreement.
1. Local Gateway vs. Hosted Services
As detailed in our Privacy Policy, the Sleev software operates as a local-first gateway residing on the customer’s machine (127.0.0.1).
- Local Gateway: The gateway runs on customer-controlled infrastructure and connects to configured upstream endpoints.
- Hosted Services: Service providers support account administration, licensing, billing, operational services, and optional diagnostic uploads. Data collection is described in the Privacy Policy.
2. Infrastructure & Service Subprocessors
The following third-party entities are currently engaged by Sleev Labs Inc. to process personal data:
| Provider | Service |
|---|---|
| Google Cloud Platform | Hosted API infrastructure, managed database, and diagnostic storage |
| WorkOS | Account authentication and organization identity management |
| Stripe | Payment processing and subscription billing |
| Resend | Transactional email delivery |
For transfers covered by DPA Section 11, the parties shall document the applicable processing locations and transfer safeguards before the transfer begins.
3. Direct Upstream AI Model Providers
An upstream provider engaged under the customer’s own account or agreement is not a Sleev Subprocessor merely because the local gateway connects to it. Where a provider processes Customer Personal Data on Sleev’s behalf, DPA Section 6 applies.
4. Data Protection Requirements
DPA Section 6 requires appropriate data protection guarantees and written terms for Subprocessors. International transfers must meet the requirements in DPA Section 11.
5. Notification & Objection Process
Sleev provides customers with advance notice of any planned addition or replacement of a Subprocessor:
- Advance Notice: Before an intended new or replacement Subprocessor begins processing Customer Personal Data, Sleev will notify each Customer with an effective DPA and update this directory. The Agreement or transfer supplement may specify a notice period.
- Notification Method: Direct notice will use the notice contact or method specified in the applicable Agreement.
- Objection Procedure: In accordance with Section 6.4 of the DPA, Customer may object in writing on reasonable data protection grounds before the intended change takes effect.
6. Questions & Inquiries
If you have questions regarding our Subprocessors, compliance, or third-party risk management practices, please contact:
Sleev Labs Inc.
Email: support@sleev.ai