Back to Foundable

Subprocessors

Last updated: May 21, 2026

Every third party that processes customer data on Foundable's behalf is listed below. Recipients that act under their own terms, including optional advertising providers, are called out separately.

What's a subprocessor

A "subprocessor" is a third party that processes Customer Content on Foundable's behalf to help us operate the Service. Hosting providers, error trackers, our LLM provider — all subprocessors. We use the minimum number needed.

Disclosure of subprocessors and prior notice of changes is required by Article 28(2) of the GDPR and by analogous provisions in our Data Processing Addendum.

Production subprocessors

ProviderPurposeData processedLocation
Anthropic, PBCLarge language model inference (Claude)Customer Content (chat messages, files attached to chats, tool inputs and outputs)United States
Supabase, Inc.Managed Postgres database, authentication, storageAll Customer Content; account credentials; encrypted Integration tokensUnited States (us-west-1)
Amazon Web Services, Inc.API server hosting, worker runtime, container logsRequest payloads in transit; ephemeral logsUnited States (us-west-1)
Vercel, Inc.Web (UI) hosting and edge deliveryStatic assets and request metadata; no Customer Content stored at restGlobal edge (primary: United States)
Cloudflare, Inc.DNS, edge network, DDoS protectionIP addresses, request metadata, TLS handshake dataGlobal edge
Functional Software, Inc. (Sentry)Error monitoring and performance tracingStack traces, request URLs, user IDs. Authorization/cookie headers and sensitive body keys (passwords, tokens, secrets, API keys) are redacted server-side before events leave our process; stack-trace context can still incidentally include other Customer Content.United States
Better Stack (Better Stack Sp. z o.o.)Uptime monitoring and incident alertingEndpoint response codes and latency only; no Customer ContentEuropean Union
GitHub, Inc.Source code repository, CI/CDNo Customer Content. Account-related metadata when employees act on issues that reference customer reports.United States

Integration providers (not subprocessors)

When you connect a third-party service to Foundable (e.g. Linear, Notion, Slack, HubSpot) or approve a Foundable Ads campaign, that provider becomes a recipient of the data you direct Foundable to send it.

These providers are not subprocessors— they are independent controllers governed by their own terms and privacy policies. You are responsible for reviewing each provider's terms before connecting and for the data you choose to share with them through the Service.

Advertising recipients (not subprocessors)

Foundable Ads uses advertising providers only after an operator opts into the feature and approves the campaign or conversion event use. For Meta campaigns, Meta Platforms, Inc. may receive limited campaign data, approved ad creative, destination URL, provider object IDs, spend and delivery metrics, and server-side conversion event data.

Meta is not a general Foundable subprocessor for Customer Content. It acts under its own business, advertising, and privacy terms for the ad services you choose to use. We do not send Meta unrelated Customer Content or raw integration credentials for other services.

Anthropic data handling

Because Anthropic processes the largest portion of Customer Content (every chat goes through them), the specifics matter. Per our agreement with Anthropic and their published commercial terms:

  • Customer Content sent to Claude is not used to train Anthropic's models.
  • Anthropic retains API inputs and outputs for up to 30 days by default. Where a request is flagged for trust- and-safety review, Anthropic may extend retention up to 2 years for inputs/outputs and up to 7 years for the related trust-and-safety classifications. See Anthropic's data-retention documentation for current details.
  • Anthropic operates from the United States; data may transit other regions Anthropic uses for inference capacity.
  • Reference: Anthropic Commercial Terms.

How we add new subprocessors

Before engaging a new subprocessor that will process Customer Content, we:

  1. Review their security posture and data practices.
  2. Sign a data-processing agreement that imposes the same or stronger obligations than our DPA with you.
  3. Update this page at least 30 days before the new subprocessor begins processing Customer Content.
  4. Notify subscribed customers (see the next section).

Subprocessor change notifications

We notify customers of new subprocessors:

  • By email to account admins at least 30 days before the new subprocessor begins processing Customer Content.
  • By updating this page on the same day the email goes out.
  • In our changelog (in-product release notes) for visibility.

To subscribe to subprocessor change notifications, email privacy@autono.sh with the subject line "Subprocessor notifications" and the email address(es) you want notified. We will add you to the announcement list.

Objecting to a new subprocessor

If you reasonably object to a new subprocessor on data-protection grounds, contact us within the 30-day notice period at privacy@autono.sh. We will work with you in good faith to find an alternative. If we can't, you may terminate the affected portion of the Service for cause without penalty.


Questions about this document? privacy@autono.sh

Postal: Autono Labs, Inc. (operator of Foundable), 131 Continental Drive, Suite 305, Newark, DE 19713, USA. See /legal for our full set of policies.