Sub-processors
Last updated: October 1, 2026
Logo.dev uses the following sub-processors to deliver our services. This page is maintained as a standalone notice and may be referenced by our Data Processing Agreement or other customer agreements where applicable.
Each sub-processor is bound by data protection obligations no less protective than those described in the applicable customer agreement.
| Name | Purpose | Location |
|---|---|---|
| Amazon Web Services (AWS) | Cloud infrastructure, databases, and storage | United States |
| Cloudflare | Authoritative DNS | United States |
| Elastic Cloud | Search infrastructure | United States |
| Fathom Analytics | Website analytics | European Union |
| Gemini models for AI logo generation, image processing, and the onboarding assistant | United States | |
| Linear | Issue tracking for feature and logo update requests | United States |
| Metronome | Usage metering for API credits | United States |
| Mintlify | Documentation hosting | United States |
| Neon | Databases for the brand directory and the Transaction Enrichment API beta | United States |
| Ntropy | Merchant identification for the Transaction Enrichment API beta | United States |
| PostHog | Product analytics | United States |
| Resend | Email communications | United States |
| Sentry | Error monitoring | United States |
| Slack | Internal notifications about logo update requests | United States |
| Stripe | Payment processing | United States |
| Svix | Webhook delivery | United States |
| Vercel | Hosting and CDN | United States |
| WorkOS | Authentication and user management | United States |
We update this page when sub-processors change. For questions, email team@logo.dev.