This register distinguishes fixed or optional providers Marvin selects, providers and endpoints a customer selects, and public research destinations an agent selects under the customer's research request. A connector or provider supported by the product is not automatically an active Marvin subprocessor.
Encryption boundary
Marvin provides end-to-end encrypted handling through the Marvin-managed boundary, with decryption only inside authorized workloads that perform requested processing. This is not zero-knowledge or customer-only-key encryption.
A transfer from Marvin's managed service to an external processing recipient ends Marvin's technical boundary at an approved encrypted handoff. Core hosting and storage components that deliver the managed service remain inside that boundary. Marvin-selected providers remain subject to vendor review, contractual controls, monitoring, and disclosure.
Core Marvin-selected service providers
| Service brand | Purpose | Data that may be processed |
|---|---|---|
| Fly.io | Hosted frontend, Account backends and volumes, networking, secrets, and Postgres | Identity, Account data, customer content, credentials, usage, and operational data |
| Cloudflare | DNS and edge security | Network and request metadata and encrypted application payloads within the target boundary |
| Tigris Data | Object storage and backups | Datasets, artifacts, database replicas, and workspace data |
| Amazon Web Services | KMS key wrapping and transactional email through SES | Cryptographic key material and encryption context; message and recipient data |
| Google and GitHub | Customer authentication | Login identity and authentication metadata |
| Stripe | Subscription and billing administration | Account, subscription, billing, and transaction metadata |
Optional Marvin-selected processing services
These services are reviewed and added to the effective public register before Marvin enables them to process customer data.
| Service class | Supported brands | Possible data and purpose |
|---|---|---|
| Managed model routes | z.ai, MiniMax, Together AI, Makora, OpenRouter | Prompts, selected context, tool results, generated output, and usage metadata for model inference |
| Managed compute and private research | Modal, Paperclip, Isaac | Selected inputs, code, credentials, logs, outputs, queries, context, and returned material for compute, discovery, retrieval, and inspection |
| Fixed literature and citation services | Semantic Scholar, OpenAlex, arXiv, PubMed/NCBI, Google Scholar, Perplexity, Wikipedia, Crossref | Queries, identifiers, URLs, minimum necessary context, network metadata, and returned research material |
Modal can be Marvin-selected when service-funded or customer-selected when configured with a customer-supplied credential.
Marvin-operated Account-scoped Kubernetes compute is inside the managed boundary and is not itself a subprocessor. Its underlying infrastructure provider belongs in the effective provider register.
Customer-selected recipients
Customers can select model providers such as Anthropic, OpenAI, Google Gemini, xAI, z.ai, MiniMax, OpenRouter, or a compatible custom endpoint. They can also select customer-supplied Modal or another custom compute endpoint and connect services such as Google Drive, Notion, GitHub, Amazon S3, Dropbox, Box, data warehouses, scientific repositories, laboratory systems, workflow tools, and customer-hosted endpoints.
These recipients can receive customer-selected files, records, queries, URLs, context, actions, credentials, and outputs within granted permissions. Customers control selection and provider-side permissions. Disconnecting in Marvin may not revoke a provider grant or delete provider-held data.
Agent-selected public research destinations
Research agents can select public literature, search, citation, and open-web destinations as authorized by the customer's research request; the customer does not individually choose every destination. Marvin sends the minimum necessary data through an encrypted handoff and records or exposes the destination. An agent-selected site is not automatically a contracted subprocessor. A recurring or fixed service enters Marvin's vendor review and effective register.
Provider approval and notice
Before a Marvin-selected provider processes customer or personal data, Marvin records its purpose, data categories, service role, security and privacy review, contractual protections, retention and training terms, processing locations and transfers, subproviders, credential scope, incident and deletion terms, exit plan, owner, and review date.
The effective register distinguishes product capability, approved configuration, active use, and observed processing. Marvin versions this page and gives any advance notice required by law or contract. Material provider changes are reviewed before activation.