Ulam Alloy — Subprocessors, Partners, and External Model Providers
Version: 1.0
Last updated: 26 June 2026
Product: Ulam Alloy — AI chat interface and API for AI/model routing
Operator: Yotta Content LTD, a private limited company registered in the United Kingdom under company number 12683376
Registered office: 71–75 Shelton Street, London, Greater London, United Kingdom, WC2H 9JQ
Privacy contact: privacy@ulam.ai
General contact: support@ulam.ai
1. Purpose
This page lists the material subprocessors, partners, infrastructure providers, payment providers, and external AI/model providers that Yotta Content LTD may use to provide, operate, secure, support, and bill Ulam Alloy.
Ulam Alloy is an AI routing product. Customer prompts, files, messages, API requests, outputs, and related metadata may be sent to external AI/model providers or routing partners when needed to generate responses, perform inference, handle fallbacks, monitor reliability, prevent abuse, debug issues, or provide support.
External providers may have their own terms, privacy policies, retention practices, training or improvement practices, safety policies, security controls, and processing locations. Ulam Alloy is not a zero-data-retention service by default.
2. Current production providers
| Provider | Category | Purpose | Data involved | Typical processing location |
|---|---|---|---|---|
| Hetzner Online GmbH | Hosting and infrastructure | Production server hosting, container runtime, storage, networking, databases, logs, and service operation | Account data, chat data, API metadata, usage data, logs, uploaded files, billing-related service data, and operational records stored or processed on the server | European Union / EEA |
| Stripe | Payment and billing | Subscription checkout, billing portal, payment processing, invoices, customer and payment references, tax and accounting records | Billing contact data, payment metadata, customer IDs, subscription status, plan, invoice and payment records. Do not submit prompts or model content to Stripe | May include UK, EU/EEA, US, and other Stripe processing locations |
| OpenRouter | External AI/model provider and routing partner | Paid model routing and selected fallback inference routes | Prompts, messages, API request data, responses, outputs, usage metadata, and technical metadata needed for inference and routing | Varies by OpenRouter and its upstream providers |
| Cohere | External AI/model provider | Public free-chat inference route where configured | Prompts, messages, API request data, responses, outputs, usage metadata, and technical metadata needed for inference | Varies by Cohere processing locations |
| Namecheap | Domain registrar and DNS provider | Domain registration and DNS routing for Ulam domains | Domain registration records and DNS traffic metadata. Not intended to receive prompts or model content | Varies by provider infrastructure |
| GitHub | Source-code and operations provider | Private source repository, deployment workflow support, issue tracking or operational collaboration when used | Source code and operational metadata. Customer content should not be pasted into GitHub issues or commits unless necessary for support and appropriately redacted | Varies by GitHub processing locations |
3. Self-hosted software components
The following components may process customer data, but in the current deployment they are run by Yotta on Ulam Alloy infrastructure rather than used as separate hosted subprocessors:
| Component | Purpose |
|---|---|
| LibreChat | Subscriber web chat interface, account/session handling, conversation history, and chat UI |
| MongoDB | LibreChat account data, conversation history, and related application records |
| Redis | Quota reservations, rate limits, free-chat claims, and hot usage windows |
| PostgreSQL | Operational schema target for future account, billing, usage, ledger, and route records |
| Meilisearch | Search indexing for the chat application where enabled |
| Caddy | TLS termination and reverse proxy |
4. Provider changes
Yotta may add, replace, remove, or change subprocessors, partners, infrastructure providers, or external model providers as Ulam Alloy evolves. Where required by applicable law or a written agreement, Yotta will provide notice of material changes and an opportunity to object.
Provider availability, routing, model selection, regions, and fallback behaviour may change without notice where needed for reliability, security, safety, cost control, or service operation.
5. Data handling notes
- Ulam Alloy does not expose raw provider model slugs as the public product surface.
- Customer-facing model names are Ulam-owned aliases such as ulam/alloy.
- External model providers may receive prompts, files, messages, API requests, outputs, and metadata when needed for inference or routing.
- External model providers may have their own retention, logging, monitoring, safety, training, improvement, and geographic processing practices.
- Do not submit sensitive, confidential, regulated, or zero-retention data unless Yotta has expressly agreed appropriate safeguards in writing.
- API gateway diagnostic payload logs, where kept by Yotta, are intended to be retained for up to one month / 30 days.
- Web chat history, uploaded files, account records, usage records, billing records, security logs, backups, and external-provider records may be retained for longer as described in the Privacy Policy and Data Processing Agreement.
6. Questions
For privacy or data protection questions, contact privacy@ulam.ai.
For general support questions, contact support@ulam.ai.