Data vendors

Last updated 2026-07-25 · Private beta — current product behavior; this notice may change as testing evolves.

These are the vendors currently configured for this private beta. A vendor only receives the data described below when the related feature is actually used.

Current vendors

Vendor	Role	Data it can see	Region	When
Vercel	Hosting, serverless functions, cookieless aggregate product analytics	All request traffic (platform logs: IP, user agent, path); aggregated page views and allowlisted lifecycle event names with low-cardinality stage/provider/checkpoint labels — never submitted URLs, content, email, account ids, or outcome values	US	Always
Supabase	Accounts (auth) and database	Email / OAuth identity, saved projects, workspace experiments & outcomes, usage entitlements	Operator-chosen project region	Only when accounts are configured and you sign in
OpenAI	AI model (GPT)	Your product page text, profile, plan context, and anything you paste to the copilot	US	Only if configured, and when selected as primary or used as a clear-policy fallback
DeepSeek	AI model	Your product page text, profile, plan context, and anything you paste to the copilot	China	When selected as primary, or as the explicitly enabled beta fallback after another provider fails
Google	Optional OAuth sign-in	OAuth handshake only	US	Only if you choose “Continue with Google”
Upstash	Anonymous preview abuse limits	A keyed digest of a random visitor token and aggregate request counts — never the submitted URL, page text, IP, user agent, or draft	Operator-chosen database region	Only when the signed-out one-channel preview is enabled

You choose a primary AI provider. If the primary model is unavailable, PostBeacon may retry with another configured provider. During this beta that can include DeepSeek, which processes data in China and does not clearly exclude training use; avoid confidential material. A failed provider may already have received the first attempt.