Last Updated: September 27, 2026
BuildSpace uses the vendors below to run the platform and the apps Builders deploy on it. Builders can link to this page from their own privacy policy instead of listing these vendors themselves.
| Vendor | Purpose | End-user data? |
|---|---|---|
| Railway | Application hosting for BuildSpace and for Builder apps; BuildSpace's primary Postgres database (accounts, sign-in sessions, app users, usage events). | Yes |
| Turso | Managed databases provisioned for Builder apps. | Yes, if the app stores it |
| Cloudflare (R2) | File and object storage for Builder apps. | Yes, if the app stores files |
| Resend | Transactional email: sign-in codes, invites, and emails Builders send through BuildSpace. | Yes (email address, message content) |
| Stripe | Payments for BuildSpace plans, and Stripe Connect for Builders who sell through BuildSpace billing. | Yes, for purchasers |
| Vercel | DNS for managed app domains; privacy-friendly page analytics on BuildSpace sites, including the sign-in page. | Limited (page views, no cookies) |
| GitHub | Hosting Builder source code repositories. | No |
| OpenAI | AI features in BuildSpace tooling (Creator Studio, build agents). | No, unless a Builder sends it |
Builders may connect their own third-party services (for example AI or analytics providers). Those are the Builder's vendors, not BuildSpace subprocessors, and must be disclosed in the Builder's own privacy policy.
We update this page before adding or replacing a subprocessor.