Subprocessors

A "subprocessor" is a third-party vendor that processes personal information on Goodspeed's behalf to operate the Service. Goodspeed remains accountable for its subprocessors and contractually requires each one to maintain appropriate security and confidentiality.

This list is part of and incorporated into our Privacy Policy and is provided for transparency and to support GDPR Article 28 obligations.

The data controller is Goodspeed LLC, 3844 Santa Caterina Blvd, Bradenton, FL 34211. This list was last verified as of the "Last Updated" date above.

Current Subprocessors

• Stripe, Inc.
  • Purpose: Payment processing, billing, subscription management, dispute handling
  • Data categories: Billing details, last-four card digits, transaction history, customer ID
  • Region: United States
  • Transfer mechanism: SCCs + UK Addendum; SOC 1 & 2, PCI-DSS Level 1
• Supabase, Inc.
  • Purpose: Database, authentication, file storage, real-time sync
  • Data categories: Account info, app content, audit logs, files
  • Region: United States (AWS us-east-1)
  • Transfer mechanism: SCCs; SOC 2 Type II
• Vercel, Inc.
  • Purpose: Application hosting and edge network for goodspeed.app, admin.goodspeed.app, and user app subdomains
  • Data categories: Web traffic logs, deployment metadata
  • Region: Global (Vercel Edge Network)
  • Transfer mechanism: SCCs; SOC 2 Type II
• Cloudflare, Inc., Workers (edge compute)
  • Purpose: Edge routing and serverless compute for select routes
  • Data categories: Request metadata, IP-level traffic logs
  • Region: Global (Cloudflare edge)
  • Transfer mechanism: SCCs; SOC 2 Type II
• Cloudflare, Inc., R2 (object storage)
  • Purpose: Object storage for uploaded files, generated source archives, and code-export bundles
  • Data categories: File contents, generated code archives, file metadata
  • Region: Global (primary region with replication)
  • Transfer mechanism: SCCs; SOC 2 Type II
• Anthropic, PBC
  • Purpose: Large-language-model inference (Claude family) for app generation, analysis, and agent flows
  • Data categories: Prompts, prompt context, response outputs
  • Region: United States
  • Transfer mechanism: SCCs; commercial terms prohibit training on customer data
• OpenAI, OPCO LLC
  • Purpose: Large-language-model inference (GPT family) for app generation and analysis
  • Data categories: Prompts, prompt context, response outputs
  • Region: United States
  • Transfer mechanism: SCCs; API terms prohibit training on customer data by default
• Voyage AI, Inc.
  • Purpose: Embedding generation for retrieval, clustering, and semantic search
  • Data categories: Text inputs to be embedded
  • Region: United States
  • Transfer mechanism: SCCs; commercial terms prohibit training on customer data
• Resend, Inc.
  • Purpose: Transactional and marketing email delivery
  • Data categories: Recipient email addresses, email content, delivery telemetry
  • Region: United States and EU regions
  • Transfer mechanism: SCCs; SOC 2 Type II
• PostHog, Inc.
  • Purpose: Product analytics (page views, feature usage, funnel analysis)
  • Data categories: Pseudonymized usage events, IP-derived geo, session identifiers
  • Region: United States (PostHog Cloud US)
  • Transfer mechanism: SCCs; SOC 2 Type II
• GitHub, Inc. (Microsoft Corporation)
  • Purpose: Source-code hosting and issue tracking for generated application code that customers elect to export to GitHub; OAuth identity provider for sign-in
  • Data categories: GitHub username, OAuth tokens, repository contents (only when customer initiates)
  • Region: United States
  • Transfer mechanism: SCCs; Microsoft EU Data Boundary commitments
• Apple, Inc.
  • Purpose: App-store distribution of mobile applications you build using the Service (only when you elect to distribute)
  • Data categories: App binaries, app metadata, your developer account info
  • Region: Global
  • Transfer mechanism: Apple Developer Program License Agreement
• Google LLC
  • Purpose: Play-store distribution of mobile applications you build using the Service (only when you elect to distribute)
  • Data categories: App binaries, app metadata, your developer account info
  • Region: Global
  • Transfer mechanism: Google Play Developer Distribution Agreement
• Sentry / FunctionalSoftware, Inc.
  • Purpose: Application error monitoring
  • Data categories: Stack traces, error context, request metadata (PII scrubbed where possible)
  • Region: United States
  • Transfer mechanism: SCCs; SOC 2 Type II
• Fly.io (Hobby Farm, Inc.)
  • Purpose: Ephemeral build and worker compute that runs the app generation, build, and quality-gate pipeline
  • Data categories: Prompts, prompt context, generated code, build logs
  • Region: United States (primary regions)
  • Transfer mechanism: SCCs (to verify at renewal)
• Expo (650 Industries, Inc.)
  • Purpose: Compiling the mobile applications you build into installable binaries, and publishing over-the-air updates to them
  • Data categories: Generated application source, build artifacts and binaries, build logs, signing material supplied for the build
  • Region: United States
  • Transfer mechanism: SCCs (to verify at renewal)
• Langfuse (legal entity to verify)
  • Purpose: Tracing and evaluation of generation runs: quality measurement, failure diagnosis, and per-run spend accounting
  • Data categories: Prompts, prompt context, response outputs, run and step metadata
  • Region: United States or European Union, depending on the region of the hosted service we are configured against
  • Transfer mechanism: SCCs (to verify at renewal); not authorized to train on customer data
• Upstash, Inc.
  • Purpose: Rate limiting and short-lived caching in front of the web application
  • Data categories: Visitor IP address, account identifier, request counters. No message or file content
  • Region: United States
  • Transfer mechanism: SCCs (to verify at renewal)
• RevenueCat, Inc.
  • Purpose: In-app purchase and subscription management for the paywall shipped inside the apps you build. Goodspeed's own plan subscriptions are billed through Stripe and do not pass through RevenueCat
  • Data categories: Purchase and subscription status, app user identifiers, receipt data
  • Region: United States
  • Transfer mechanism: SCCs; SOC 2 Type II
• OpenRouter, Inc.
  • Purpose: Model routing and gateway for idea intake, file extraction, and design generation
  • Data categories: Prompts, prompt context, response outputs
  • Region: United States
  • Transfer mechanism: SCCs; routes to underlying model providers under their terms
• Google LLC (Gemini models)
  • Purpose: Large-language-model inference (Gemini family) for generation and analysis, including image and design generation
  • Data categories: Prompts, prompt context, response outputs
  • Region: United States
  • Transfer mechanism: SCCs; Google Cloud terms prohibit training on customer data
• Rewardful (legal entity to verify)
  • Purpose: Affiliate referral attribution: credits a partner when a visitor who arrived through their referral link later subscribes. Loads only after a visitor accepts cookies
  • Data categories: Referral identifier, visit metadata, subscription conversion event
  • Region: United States
  • Transfer mechanism: SCCs (to verify at renewal)

Notes

• The list is current and was last verified as of the "Last Updated" date above. A vendor's transfer mechanism and certifications are checked when we add the vendor and reviewed periodically; where a detail is still being confirmed it is marked "(to verify)".
• "Region" indicates where the subprocessor primarily processes data; many subprocessors use globally-distributed infrastructure for redundancy and edge delivery.
• "Transfer Mechanism" describes how each subprocessor lawfully receives personal information from the EU/UK to the US or other regions. Standard Contractual Clauses (SCCs) are the European Commission's approved set of contractual safeguards.
• Apple and Google are listed because if you elect to publish a Goodspeed-built application to their stores, distribution flows through them and they receive the relevant data. They are not subprocessors for the operation of Goodspeed itself.
• We do not currently use third-party advertising networks, behavioral-advertising platforms, or data brokers.

Changes to This List

We will update this page when we add, remove, or replace a subprocessor that processes personal information. For material changes, we will notify active customers at least 30 days before the change takes effect, where reasonably practicable. If you object to a new subprocessor, your remedy is to stop using the Service before the change takes effect; we will not be able to continue the Service for you without the subprocessor.

For Customer Content (your prompts, your generated application code, your uploaded files), we do not switch subprocessors mid-contract without notice. For ancillary processors (e.g., a swap from one error-monitoring vendor to another that affects only diagnostic telemetry), we may make changes without individual notice, but the list above will be kept current.

Enterprise Customers and DPAs

Enterprise customers requiring a Data Processing Agreement (DPA) under GDPR Article 28 or under state privacy laws should contact legal@goodspeed.app. We will provide our standard DPA on request and review reasonable redlines.

Questions

Questions about our subprocessors or our diligence on them: privacy@goodspeed.app