Sub-processors
Last updated: June 2, 2026
A sub-processor is a third-party service that processes Member data on our behalf to operate the Platform. We list every sub-processor we currently rely on so Members can make informed decisions about their data and so Enterprise Members receive the advance notice their agreement entitles them to under Member Terms of Service §18.6(g).
Current sub-processors
| Sub-processor | Purpose | Location of processing |
|---|---|---|
| Supabase | Database hosting, authentication, real-time, storage | United States |
| Stripe | Payment processing | United States |
| Resend | Transactional and marketing email delivery | United States |
| Anthropic | AI inference via Claude API for document generation | United States |
| Vercel | Web application hosting and deployment | United States |
| Cloudflare R2 | Backup storage (cold backups) | United States (ENAM region) |
| Google Workspace | Business email, support correspondence, and document storage | United States |
| Meta Platforms | Connected social media account integration, where Member has connected a Facebook Page or Instagram Business account | United States |
Referenced from our Privacy Policy §5 and Member Terms of Service §18.6(g).
Notification of changes
Enterprise Members receive at least thirty (30) days advance notice before we add a new sub-processor or change the location of an existing sub-processor's processing, in line with Member Terms of Service §18.6(g). The notice describes the proposed sub-processor, the data categories involved, and the effective date.
To receive these notifications today, email privacy@fashionweekblueprint.com and ask to be added to the sub-processor notification list. A proper subscription mechanism is on our engineering roadmap and will replace the manual email list when it ships.