Subprocessors and connected providers
Draft for the public release. Locations and agreements marked as unknown must be verified before publication.
Orage's controller is [Publisher legal name and address], currently Axel Rock acting as an individual. Questions: privacy@orage.ai. Read our Privacy Policy for purposes, retention, rights and transfer safeguards.
This list includes infrastructure processors, AI recipients, and services you choose to connect. A provider can be a processor for one function and a separate controller for its own account, billing or security. Your own ChatGPT, Claude, GitHub or Apple contract also applies. This page does not turn every provider into an Orage processor.
The country of a provider is not a promise about where each byte is processed. EU hosting can still involve support or control access abroad. Regional settings, further suppliers and transfer safeguards must be checked for the actual service.
Infrastructure, AI and measurement
| Provider | Purpose | Data | Country and processing location | Privacy notice |
|---|---|---|---|---|
| Railway | App server, persistent disk and file-store service | Account and connection records, chats, code, files, waitlist, music records and logs | United States provider; documented Orage server region Amsterdam, Netherlands; operations can involve the US | Railway |
| Tigris Data, through Railway | Railway's S3-compatible files bucket |
Captured files, saved chats, memory copies, permitted audio, host clips and episodes; network metadata on downloads | United States provider; [Tigris bucket processing locations] | Tigris |
| Boat, provided by Dedale AI, Corp. | Home and task cloud computers and disk snapshots | Cloned repositories, code, tasks, histories, computer credentials and logs | United States company; provider states sandbox and snapshot hosting in Germany, Finland and France; other operations may be in the US | Boat |
| Vercel | Public website, asset delivery and AI Gateway | Site request metadata; for the Gateway, prompts, connected content, work summaries, voice text and music tastes for the chosen feature | United States provider; global delivery and model routing; [Vercel AI Gateway route locations] | Vercel |
| OpenAI | Codex with your connected ChatGPT account; selected API and Gateway models | Account authentication, prompts, code, files, images, relevant chats and tool results; work or voice context and music tastes on applicable Gateway routes | United States and other service locations; provider entity depends on your contract | OpenAI |
| Anthropic | Optional Claude coding; Gateway host writing and voice responses | Claude account authentication for subscription use; prompts, code, task summaries, transcripts, conversation context and agent answers as applicable | United States and other service locations | Anthropic |
| TypeSafe AI | Jev decisions through Vercel AI Gateway | Connected message text, thread excerpts, work and device context, song metadata | United States, as stated in the provider's privacy policy | TypeSafe AI |
| ElevenLabs | Remote transcription, host and answer speech, episode rendering and alignment | Microphone audio, vocabulary hints including names, text to speak, audio and text for alignment | US and UK entities; [ElevenLabs processing region for Orage's plan] | ElevenLabs |
| PostHog | Product measurement and classified error tracking | Account or installation ID, session/thread/tool IDs, usage, errors, performance and site page views; no intended prompt or code capture | United States provider; EU service stores and processes user events in Germany; support and account operations can involve other countries | PostHog |
| OpenRouter, optional | Alternate Claude API route | Coding prompts, context and outputs passed to the selected model provider | United States provider; downstream locations depend on the chosen route | OpenRouter |
| Modal, optional | Remote analysis of permitted song audio | Audio and analysis results; no intended persistent song copy in Orage's analyzer endpoint | United States provider; [Modal execution and log locations] | Modal |
| [Support mailbox provider] | Support and privacy requests | Email address, correspondence, attachments and verification records | [Support mailbox processing locations] | [Support mailbox privacy URL] |
| [Waitlist email delivery provider] | Requested waitlist and access messages | Email address and message delivery records | [Waitlist email processing locations] | [Waitlist email privacy URL] |
| [Web payment provider], if introduced | Web subscriptions, payments and refunds | Customer and transaction records; payment details entered with the provider | [Web payment processing locations] | [Web payment privacy URL] |
No Neon database or direct Cloudflare R2 file store is configured for Orage in the reviewed code. Its current records use disk files and Codex's local databases. The bucket is Railway's Tigris-backed service. Boat may use Cloudflare for its own snapshots; that is a further supplier of Boat, not Orage's files bucket. Daytona is supported in code but is not the documented production computer provider. If these choices change, this page must change before data takes a new route.
Connected services and device services
These recipients are used only for the relevant feature or connection. Some receive data directly from your device. Their own account policies govern their independent processing.
| Provider | Purpose | Data | Country and processing location | Privacy notice |
|---|---|---|---|---|
| GitHub | Orage owner sign-in, repositories and authorized repository actions | Login and numeric ID, avatar, OAuth requests, repository data, commits and actions | United States provider; global service | GitHub |
| Apple | App Store purchases, push notifications, Live Activities, performance reports and artwork search; planned MusicKit | Push tokens and notification contents; purchase data; song title/artist searches; device request metadata; authorized MusicKit library and listening data when that feature exists | United States and regional Apple entities; global service | Apple |
| Your Jellyfin operator | Music library, favorites, artwork and streaming | Server address, connection key, searches, track requests and favorite changes | Your server's location and host, chosen by you | [Your Jellyfin operator privacy URL]. The Jellyfin project does not operate your server |
| Hugging Face | Download pinned local dictation models | Download request, model and network metadata; no dictation audio | United States provider; global file delivery | Hugging Face |
| Slack, optional | Connected team chat and signals | Authorized message queries, user/workspace information and actions you permit | United States provider; workspace settings affect storage | Slack |
| Google, optional | Connected mail, calendar and files | OAuth identity, authorized queries and requested content | United States and regional entities; global service | |
| Linear, optional | Connected issue boards and permitted issue actions | Issue queries, issue content and authorized writes | United States provider; [Linear workspace data region] | Linear |
| Sentry, optional connected source | Read errors in products you connect | Issue queries, project information and retrieved error details | United States provider; documented Cobl source uses Germany/EU; a connected project's region may differ | Sentry |
| Conductor, optional connected source | Read connected agent sessions for work and host context | Authorized session requests and retrieved messages | [Conductor contracting country and processing locations] | Conductor |
Orage currently sends its own error reports to PostHog, not Sentry. Its separately hosted Keys service can hold connected GitHub, Slack and Google credentials and expose authorized services to other agents connected to Keys. Keys is operated by the Orage publisher and hosted on Railway. It needs a distinct access choice and deletion coverage before public use.
The owner's unofficial YouTube route also contacts Google/YouTube and Apify's proxy. It is not part of the public service. Those routes, controls and downloads must be unavailable to public accounts and in the App Store build. Public music uses must follow the source's rights and restrictions.
Changes and safeguards
Before launch, Orage must confirm processor agreements, further suppliers, retention settings and EEA/UK transfer safeguards for each active route. Features with unresolved recipients must stay off. Where a business data processing agreement requires advance notice of subprocessor changes or a right to object, we follow that agreement. We also update this page and obtain new permission where an AI recipient or purpose changes.
Last updated 2026-10-09