Service Providers and Subprocessors
Updated 8 September 2026 · Version 2026-09-08
Provider directory and account schedules
The providers below support different parts of the service. A provider may be our processor, the customer’s authorised subprocessor or an independent controller for a separate activity. This directory is not a representation that every provider receives every customer’s content.
For customer-directed personal data, the supplier schedule supplied for the account identifies actual contracting entities, purposes, data, processing locations, retention and transfer safeguards, including infrastructure and downstream model recipients. Request that schedule at contact@shinobiops.ai before authorising a route whose details you have not received.
| Provider | Service | Scope |
|---|---|---|
| Clerk | Account authentication and session management | Account identity and authentication information; role and scope depend on the activity. |
| Stripe | Payments and billing | Payment-interface, transaction and billing information; separate controller activities are described in Stripe’s notice. |
| CookieYes | Website cookie consent management | Consent choices and identifiers, consent records and technical information needed to deliver and operate the banner. |
| PostHog | Configured analytics | Permitted website or product events and technical information; website choices are described in the Cookie Notice. |
| Google Ads | Optional website advertising measurement | Consented advertising events and click identifiers; not a general customer-content model processor. |
| OpenRouter and authorised downstream recipients | Model routing, research, generation and embeddings | Necessary Inputs and content for the enabled route; downstream legal entities, purposes and conditions must be identified in the applicable supplier schedule. |
Changes and objections
For authorised Subprocessors, the DPA provides at least 15 days’ advance email notice to the registered administrator, without requiring a separate subscription, and a reasonable data-protection objection process. New or changed routes must first satisfy the applicable authorisation and transfer requirements. Substituting a model version within an already authorised route does not itself authorise a new recipient or purpose.
The Provider may offer an alternative or terminate affected processing with unused prepaid fees refunded where an objection cannot reasonably be resolved. It will not bypass a timely unresolved objection by sending the affected Customer Personal Data to the proposed recipient. Full terms: /dpa#clause-9.