Conifer Solutions, Inc.
Subprocessors
Every third party that processes data on Conifer's behalf, what they receive, and why.
This page lists the third parties that process personal data on Conifer's behalf. It is published separately from the privacy policy so it can be kept current without amending the policy itself. If you rely on this list, check it when your agreement renews.
Infrastructure and service providers
| Subprocessor | What it does for us | What it receives | Location |
|---|---|---|---|
| Cloudflare, Inc. | Hosts conifer.build; network, TLS, and bot protection for our sites and api.conifer.build | Requests and responses in transit, with metadata such as IP address, user agent, and country; newsletter subscriber records | United States / global edge |
| Railway Corp. | Runs the API gateway, its response cache, and the billing service and its database | Requests in transit; cached responses; usage data; billing and plan records | United States |
| Google LLC (Google Cloud, Google Fonts) | Hosts the gateway's database and a standby gateway; serves fonts for the console and the status board | Usage data, account balances, encrypted provider keys, and deferred jobs; requests in transit while the standby is serving; IP address and user agent when fonts load | United States |
| Modal Labs, Inc. | Hosts Conifer's router service | The routing input, when you ask us to choose the model with auto, balanced, or best | Region not fixed by Conifer |
| Supabase, Inc. | Account sign-in and our account database | Account details, including your password hash and sign-in profile; website analytics; form submissions and newsletter subscribers; console account data; Parallax usage data | United States |
| Fly.io, Inc. | Runs Parallax's servers, cloud machines, and the phone app's relay | Uploaded sessions and their reviews; account details and GitHub token; cloud machine disks and the credentials sent to them; Parallax usage data; the research dataset | United States |
| Depot Technologies, Inc. | Builds Parallax cloud machine images | Repository code, when an image is built from it | Region not fixed by Conifer |
| Stripe, Inc. | Payment processing | Name, email address, and payment details, which Stripe collects directly | United States |
| Resend (Plus Five Five, Inc.) | Account email and the newsletter | Email address, name, the messages you send us, and newsletter open and click events | United States |
| Slack Technologies, LLC | Our Slack app and internal support | Account details and usage | United States |
| GitHub, Inc. (Microsoft) | Sign-in with GitHub, the Parallax GitHub App, and Parallax downloads and updates | GitHub account details; the repositories you give the App access to; IP address when Parallax downloads or checks for updates | United States |
| 650 Industries, Inc. (Expo) | Notifications and updates for the Parallax phone app | Your phone's notification token and the text of each notification | United States |
Model providers
A model provider receives a request when it serves it: when you name a model it serves, when the router chooses one of its models, when you list fallback models, or when the gateway retries a failed request with another provider that serves the same model. Parallax's reviews, memory, and free models reach them the same way, through our gateway. The served catalogue is at conifer.build/models.
- Where they are. Most of our model providers are based in the United States. Those based elsewhere are DeepSeek, Moonshot AI, Tencent Cloud, Xiaomi, and Z.ai (China), Mistral AI (France), Nebius (Netherlands), Cohere (Canada), and Upstage (South Korea). Each processes requests in locations it chooses.
- Inference marketplace. Some open-weight models are served through an inference marketplace, which chooses the host that serves the request under that host's own terms.
- Choosing the model. For
beta-auto, the request's content also goes to a decision model hosted by one of our model providers. - Their terms. Each provider handles the requests it serves under its own
terms and privacy policy, including when you bring your own API key. To keep
your requests with particular providers, set a provider allow-list with
PUT /v1/account/allowed-providers.
Not on this list
Services you connect with your own account or key, such as your Claude or ChatGPT subscription, Slack, Devin, or Capy, act under your own agreement with them and are not our subprocessors.
We do not use advertising networks, data brokers, session-replay tools, or third-party analytics services.