The third parties that process data on SearchFit's behalf, what each one is for, and where it processes. Being listed here does not mean we disclose your data to that company: most of these run the infrastructure the Service sits on, and all of them are contractually barred from using your data for their own purposes. Last updated: August 14, 2026.
SearchFit runs on these. Your data resides on and moves through their systems because that is where the Service operates. We do not disclose it to them, and none may use it for their own purposes.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Railway | Application hosting and compute | All data in transit through the application | United States |
| Neon | Managed PostgreSQL database, operated on AWS infrastructure | Account data, project data, generated content | Australia (Sydney) and United States |
| Cloudflare | Content delivery, object storage (R2), DDoS protection | Uploaded files and media, request metadata | Global edge network |
| Trigger.dev | Background job processing | Project data passed to scheduled and queued work | United States |
| Sentry | Error monitoring and diagnostics | Error traces, which may incidentally include user identifiers | United States |
Each receives only the data its function requires.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Clerk | Authentication and user management | Name, email address, authentication credentials | United States |
| Stripe | Payment and subscription processing | Billing details, payment card data (held by Stripe, never by us) | United States |
| Resend | Transactional and notification email | Email address, message content | United States |
We send model requests to one gateway, which routes them onward.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Vercel (AI Gateway) | Routes model requests to the providers listed below | Prompt and response content | United States |
Our agreement is with Vercel; these are its sub-processors rather than ours. They are listed because your prompts reach them, not because we contract with them directly.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Anthropic | Language model inference (Claude) | Prompt and response content | United States |
| OpenAI | Language model inference (GPT) | Prompt and response content | United States |
| Language model inference (Gemini) | Prompt and response content | United States |
Usage data only. No project content is sent to these.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| PostHog | Product analytics | Usage events, user identifiers | United States |
| Google Analytics | Website analytics | Usage events, IP address, device data | United States |
| Umami | Privacy-focused website analytics | Aggregated page views, no cookies | European Union |
| Hotjar | Session insights on marketing pages | Interaction events, device data | European Union |
We call third-party APIs that return search and ranking data. Those requests carry a domain, a keyword, or a search query, and never account details, customer contacts, or anything identifying a person. They are not sub-processors of personal data and are not listed for that reason.
Services you connect yourself, such as Google Search Console, Google Analytics, Webflow, and Slack, are not sub-processors either. You grant SearchFit access to those accounts directly and can revoke it at any time from your integration settings.
We update this page when a sub-processor is added or removed. Customers on a data processing agreement can request notice of changes by emailing [email protected].
Questions about this list or our data processing:
[email protected]