Subprocessors

Last updated 2026-07-12 · Beta draft — under legal review; wording may change.

These are the vendors that can process data when you use PostBeacon. Most are conditional: they only receive anything if the deployment has them configured and your run actually uses them. We’ll update this page before adding a vendor.

Current vendors

VendorRoleData it can seeRegionWhen
VercelHosting, serverless functions, cookieless web analyticsAll request traffic (platform logs: IP, user agent, path); aggregated page viewsUSAlways
SupabaseAccounts (auth) and databaseEmail / OAuth identity, saved projects, workspace experiments & outcomes, usage entitlementsOperator-chosen project regionOnly when accounts are configured and you sign in
AnthropicAI model (Claude)Your product page text, profile, plan context, and anything you paste to the copilotUSOnly for runs where you select Claude
OpenAIAI model (GPT)Same prompt content as AnthropicUSOnly for runs where you select OpenAI
DeepSeekAI modelSame prompt content as AnthropicChinaOnly for runs where you select DeepSeek
FirecrawlHeadless rendering of JavaScript-only product pagesThe product URL being analyzedUSOnly if configured, and only when a plain fetch of your page comes back empty
TavilyWeb search for community discoverySearch queries derived from your product profile (never the raw page text)USOnly if configured
PolarMerchant of record (checkout, invoices, tax)Purchase identity and transaction data — card numbers never touch PostBeaconEU/USOnly when billing is configured and you buy a plan
GoogleOptional OAuth sign-inOAuth handshake onlyUSOnly if you choose “Continue with Google”

AI providers are alternatives, not a chain: a single run sends prompts only to the one model you selected for it.

Questions or requests about your data: contact us. © 2026 PostBeacon · postbeacon.app