Subprocessors

Feynly uses the following subprocessors to operate the service. Data residency varies by provider; student study content sent for AI processing may transit through OpenRouter to underlying model hosts (including non-Western providers when configured).

SubprocessorPurposeData processedLocation (typical)
SupabasePostgres database, authentication, RLSAccount, study data, quotasConfigurable (EU/US)
Cloudflare R2Object storage (Pro opt-in originals)Uploaded filesCloudflare edge
OpenRouterAI gateway (generation, grading, teach-back, STT)Prompts, extracted text, audio clips (STT discarded immediately)US; routes to model providers globally
Groq (via OpenRouter)Cloud speech-to-text (Whisper)Audio during transcription onlyUS
Google Gemini / other model hosts (via OpenRouter)LLM inferencePrompts and extracted textPer model routing
RevenueCatSubscription managementPurchase tokens, entitlement stateUS
Google PlayBilling & distributionPayment method (Google), purchase historyPer user region
Firebase / GoogleCrashlytics, Remote Config, FCM pushCrash logs, config flags, device push tokensGoogle infrastructure
PostHog CloudAnalytics, funnels, session replay, feature flagsUsage events (consent-gated)EU or US cloud (project setting)
GlitchTipBackend error reportingAPI error payloads, request contextYour hosting region
Fly.ioAPI + worker hosting (custom domain api.feynly.app)Request logs in transitFly region you choose

We prefer Western-hosted model routing for student data where available. See the Privacy Policy athttps://feynly.app/privacy.

Updates to this list will be reflected in the Privacy Policy.