Subprocessors

Every third party that processes data on Selyf's behalf, what they see, and where.

This list is verified against the code that actually calls each service, not a planned or aspirational list — see Privacy for what each one is allowed to do with your data.

Data processors

Services that receive some part of your actual data (Gmail content, or analytics events) in order to provide the product.

ProviderPurposeData typeLocation
Google (Gmail API, OAuth)Source of your Gmail data; sign-in identityMessage metadata and content for threads you open; your Google account emailGlobal (Google infrastructure)
AnthropicAI analysis and draft generationA thread's message content, only when you explicitly analyze or draft a replyUnited States
Google GeminiAI analysis and draft generation (alternate/default provider)A thread's message content, only when you explicitly analyze or draft a replyGlobal (Google infrastructure)
PostHog (EU Cloud)Product usage analytics, server-side onlyEvent names and non-identifying properties — never Gmail content, never sent from your browserEuropean Union
Sentry (EU)Error tracking, server-side only, unhandled server errors onlyA stack trace and your account ID (not your email) — never Gmail content, subject lines, sender addresses, or tokens; filtered out before anything leaves the serverEuropean Union

Infrastructure

Services that run or route the product but don't process your Gmail data themselves.

ProviderPurposeData typeLocation
VercelHosts the web app (selyf.com) — marketing pages and dashboard UIStandard web hosting traffic; no Gmail content is processed by Vercel itselfGlobal (edge network), United States-headquartered
CloudflareDNS resolution for selyf.com onlyDNS queries only — traffic is not proxied through Cloudflare (DNS-only / "grey-clouded"), so Cloudflare never sees request or response contentGlobal

Only the web app (selyf.com) runs on Vercel. The API (api.selyf.com) and the status page (status.selyf.com) run on a separate, self-managed server — Vercel never sees Gmail content, AI requests, or database traffic, since it only ever serves the frontend. Cloudflare is DNS-only for this domain: traffic is not proxied through Cloudflare's network, so it is not in a position to process, inspect, or log any request or response content — it is not a data processor in the traffic path, only the DNS registrar/host.