Sub-processors

Last updated: June 17, 2026

To run betterlanders we rely on the third-party services below. Each handles data only as needed to provide its part of the service. This list is part of our Privacy Policy; we update it here when a sub-processor changes.

Sub-processorPurposeData processedLocation
SupabaseAuthentication, primary database, object storageAccount, content, leads, billing metadataUnited States
Fly.ioBackend API hostingAll API requestsUnited States (iad)
VercelFrontend + published-lander hostingRequest metadata, UI assetsGlobal edge / US
CloudflareCDN, DDoS protection, coarse country derivationRequest metadata, IP-derived country (IP not stored)Global
UpstashRedis — rate limiting, pub/sub, analytics countersHashed IP / visitor countersUnited States
AnthropicLLM inference (primary)Briefs, prompts, page contentUnited States
GroqLLM inference (fallback)Briefs, promptsUnited States
OpenRouterLLM inference routing (fallback)Briefs, promptsUnited States
PaddlePayments (Merchant of Record)Billing details, subscription status, last 4 of cardEU / Global
ResendTransactional email (welcome, billing, lead alerts)Your email address, email contentUnited States
Pexels / UnsplashStock image searchImage search queriesUnited States
SentryError monitoring (optional)Error logs, diagnostic metadataUnited States / EU

Briefs and prompts you submit are sent to LLM providers to generate output; we do not train models on your content. Leads collected on landers you publish are data you control — you are the controller and betterlanders is your processor for that data.

Questions, or want notice of sub-processor changes? privacy@betterlanders.com.