Subprocessors and Data Recipients
Last updated October 13, 2026
Effective September 24, 2026
Contents7 sectionsHide
How to read this registry
A subprocessor processes Customer Personal Data for Foundable to deliver the Service. The table states the production path that uses each provider; an entry does not mean every customer uses every provider. Providers used only for Foundable's own operations, and third parties that determine their own purposes, are described separately after the table.
The location column identifies verified project regions or the provider's published processing footprint. It is not a promise that support, security, or subprocessor access can occur in only one country. Contact us if your procurement process requires the account-specific contracting entity, data-residency configuration, or transfer mechanism.
Customer-data subprocessors
| Provider | Scope and purpose | Data processed | Primary storage / processing locations |
|---|---|---|---|
| OpenAI | Core AI: The models behind Ted's conversation, idea-first onboarding, chat titles, and the embeddings that let Ted recall older chats | Customer Content in a chat: messages, attached context, retrieved history, tool inputs and outputs, and the text embedded for recall | United States and other OpenAI or subprocessor locations unless a separate data-residency arrangement applies |
| Anthropic, PBC | Build and drafting AI: Claude models for Build's website agents and their planning, Inbox reply drafts, and the composition of videos Ted renders | The brief, the website source and files a Build run works on, the mail a reply is drafted for, and the composition a video is made from | Stored in the United States; processing may occur in the United States, Europe, Asia, and Australia unless a separate arrangement narrows it |
| fal.ai | Image generation: Runs OpenAI's GPT Image model for the images Build and Ted generate | Image prompts, reference images, generated outputs, and request metadata | Provider and model infrastructure locations; no single processing region is asserted by Foundable |
| Perplexity AI, Inc. | Web search: Web search when Ted researches on your behalf | The search queries Ted derives from a conversation and the public results returned | Provider and subprocessor locations; no single processing region is asserted by Foundable |
| Monid Inc. | Public data: Routes the public data lookups Ted runs and his business searches to the data providers it lists (social platforms, reviews, listings, markets and search rankings) and bills them | The lookup inputs Ted derives from a conversation, such as search terms, business names and public page or profile addresses, and the public data returned; Monid keeps each run's input and output on Foundable's account | United States (Monid Inc., San Francisco); each provider a lookup reaches processes it in its own locations |
| Turbopuffer, Inc. | Chat recall: The search index over a foundable's older chats that Ted retrieves from | Embeddings and excerpts of a foundable's chat history with their chat and foundable identifiers | AWS us-west-2 (Turbopuffer's region for Foundable's index) |
| Mobbin | Design references: Screen references Build searches while planning a website | Search terms derived from the brief; no Customer Content beyond those terms | Provider locations under its terms |
| Judgment Labs, Inc. | AI quality analytics: Traces of Ted's model calls and Build's tool activity for quality monitoring | Model inputs and outputs, tool names and result previews, token counts, and the chat and turn identifiers; the foundable and user are identified only by stable hashes | Provider and subprocessor locations under the applicable service terms; contact Foundable for account-specific details |
| Amazon Web Services, Inc. | Core infrastructure: The API and workers on ECS Fargate, the Aurora PostgreSQL database, object storage for saved files, uploads and workspace checkpoints, secrets, and service logs, behind a CloudFront front door | Account data, Customer Content, requests in transit, runtime data needed to execute work, and application and infrastructure logs | AWS us-west-1 for the database, services and storage; CloudFront's global edge for requests in transit |
| Cloudflare, Inc. | Publishing and connected websites: Serves every published website on foundable.app from its edge, stores their releases in R2, runs a website's server code in a Worker and records that code's server log, captures the screenshots of saved versions, and runs the remote browsers used to sign in to connected websites and do Ted's work in them | Published website files, a website's server code, the requests its visitors make and what the code prints, the pages captured for thumbnails, and connected websites' sign-in inputs, cookies, page contents and actions | Global network |
| Temporal Technologies, Inc. | Durable workflows: Temporal Cloud orchestrates Ted turns, Build runs, mail and social delivery, scheduled runs and waitlist work so interrupted work resumes | Workflow histories: the inputs and results each step records, which include Customer Content from the turn or run they belong to | Temporal Cloud; the namespace's region and retention are under Foundable's Temporal account |
| Modal Labs, Inc. | Sandboxes: Isolated sandboxes where Build authors and compiles websites, Ted's workspace runs commands, and videos are rendered | Website source and files, build instructions and output, workspace files, logs, and rendered video | Modal's infrastructure in the environment Foundable configures; no single region is asserted by Foundable |
| Supabase, Inc. | Website backends: One hosted backend per website, created only when the website needs one: its database, storage and its visitors' sign-in | The website's data and files, and its visitors' accounts and sign-in events | AWS us-west-1 (the region Foundable creates each project in); support and subprocessor processing may occur elsewhere under Supabase's DPA |
| WorkOS, Inc. | Authentication: Sign-in with Google, Apple, or an emailed code, and the sessions that keep you signed in | Account email and name, the identity from Google or Apple, and sign-in and session events including IP address and user agent | United States and subprocessor locations under WorkOS's DPA |
| Stripe, Inc. and applicable Stripe affiliates | Billing and Foundable Payments: Checkout, subscriptions, invoices and the billing portal for Foundable plans; and the Stripe account a foundable uses to sell to its own customers through Foundable Payments | Billing contact and address, payment-method details entered with Stripe, invoices, subscriptions and transaction history; for Foundable Payments, the foundable's account details and its customers' purchases | Stripe and payment-network locations under the applicable agreement |
| AgentMail, Inc. | Inbox: The mailbox each foundable gets on foundable.app or its own domain, and the mail sent from it | Sender and recipient addresses, subjects, message bodies, attachments, replies, and delivery events | United States and European Union under AgentMail's current subprocessor list |
| Linq | Texting: Texting with Ted over iMessage or SMS, for the waitlist and for signed-in accounts that link a phone | Phone numbers, message content, images sent in a text, and delivery events; a paused number's STOP or START is kept as a salted digest | United States hosting under Linq's terms |
| ZERNIO SOFTWARE SL | Social publishing: Connecting social accounts and publishing to them from Run | Connected-account credentials and identifiers, post copy and media, publishing status, and engagement analytics | Spain / European Union and provider subprocessor locations |
| Sampark Inc (Composio) | Connected apps: Connects the apps an owner or admin links in Settings > Integrations, holds their sign-in credentials, and runs the reads Ted makes and the actions an owner or admin delegates or approves in them | Connected accounts' credentials and identifiers, the reads Ted runs and what they answer, and the actions delegated or approved in a connected app | Provider and subprocessor locations; no single processing region is asserted by Foundable |
| Intercom, Inc. and applicable Intercom affiliates | Customer support: The signed-in support Messenger, conversation history, teammate inbox, and reply notifications | A signed statement of the operator's account identifier, the support messages and attachments the operator sends, and a Ted-prepared summary only after the operator approves it | United States workspace when enabled; limited support and subprocessor processing may occur elsewhere under Intercom's DPA |
| Plus Five Five, Inc. (Resend) | Email delivery: Sign-in codes, team invitations, waitlist admission notices, reply notifications, and the account emails of websites built with Foundable | Recipient addresses, message content, and delivery metadata | United States and subprocessor locations under Resend's DPA |
| PostHog, Inc. | Product analytics: Explicit product events from the workbench and the public pages | Named product events with route families and timing, an anonymous identifier, and on the landing page a device identifier and campaign tags; no page contents, no session recordings, and no person profiles inside the product | PostHog Cloud in the region Foundable's project is created in (United States or European Union) |
| Functional Software, Inc. (Sentry) | Error monitoring: Error reports from the browser and the servers | Error messages, stack traces, the release and a request identifier; headers, bodies, credentials and personal fields are removed before an event leaves, and no session is replayed | Sentry's ingestion region for Foundable's project |
AI-provider data handling
OpenAI's models are the primary model family for Ted's conversation and for idea-first onboarding; Anthropic's Claude models power Build's website agents, Inbox reply drafts and video composition. fal.ai receives prompts and reference images only when an image is generated, Perplexity receives queries only when Ted searches the web, and Monid receives a lookup's inputs only when Ted looks up public data or searches for businesses. Each provider is limited to the feature scope and data categories listed in the table.
- OpenAI states that business/API data is not used to train models by default. Its endpoint-specific retention and abuse-monitoring rules are described in its data-control documentation.
- Anthropic's commercial terms prohibit training on Customer Content submitted through its services. Its standard API retention is generally up to 30 days, with longer trust-and-safety or legal retention in documented cases. See its current retention documentation.
- Judgment Labs receives the agent traces described in the table for quality monitoring: model inputs and outputs and tool activity, with the foundable and user identified only by stable hashes. Contact Foundable with account-specific contractual or data-handling requirements.
Operational service providers
These vendors support Foundable's controller-side operations. They are not included in DPA Annex III when they do not process Customer Personal Data on a customer's behalf:
- GitHub: Foundable's source code. Customer-report metadata may appear when employees handle an issue, but product Customer Content is not intentionally stored there.
Recipients acting under their own terms
Some features send data to a recipient that acts as an independent or joint controller, or has a role that varies by activity. Those recipients are not blanket Foundable subprocessors for that activity:
- Connected integrations and social networks receive the data and actions you direct Foundable to send. Their own terms govern their use of it.
- Google signs the visitors of a published website in when the website offers Google sign-in, under Google's own terms; the visitor's account then lives in the website's backend.
- Stripe processes billing operations for Foundable and determines its own purposes for payment-network, fraud, compliance and tax activities, both for your Foundable purchases and for the Stripe account a foundable uses to sell through Foundable Payments.
Changes and objections
We update this registry when a provider or its role changes. Where a countersigned DPA or applicable law requires advance notice, we use the notice method and period stated in that agreement or law.
To ask about a provider, request account-specific processing details, or raise a data-protection objection, email privacy@foundable.com. If an effective DPA gives you a formal objection right, its process and deadline control.
Contract status
The public DPA page is available for review. Foundable and the customer complete an account-specific agreement to activate transfer mechanisms, audit rights, and notice periods.