Subprocessors

Last updated: August 28, 2026

SaaSy Solutions LLC uses the processors below to operate the Service. This list matches integrations we can prove from production code and DNS. We will email workspace owners at least 30 days before adding a processor that receives Customer Data, unless the change is required to fix a security issue.

Aspirational or tenant-supplied connectors (for example a tenant's own SendGrid key) are not SaaSy subprocessors. Vercel is not used.

Current processors

ProcessorPurposeDataLocation
Stripe, Inc.Payments, subscriptions, checkout, dunningName, email, billing address, card token (held by Stripe), subscription metadataUSA
Fly.io, Inc.Application hosting for backend servicesApplication data in transit, IP addresses, request logsUSA
Neon, Inc.Managed PostgreSQLCustomer Data at rest: accounts, CRM, billing, health scoresUSA
Cloudflare, Inc.DNS, CDN, edge runtime for app.hellosaasy.aiIP addresses, request metadata, TLS handshake dataUSA (global edge)
GitHub, Inc.Marketing site hosting (GitHub Pages)Marketing-site visitor IPs and request logsUSA
Sentry (Functional Software, Inc.)Error monitoringStack traces, browser metadata, user IDs on error eventsUSA
PostHog, Inc.Product analytics and feature flagsPage views, clicks, user IDs, feature-flag evaluationsUSA
Anthropic, PBCLLM inference for advisory featuresPrompt content that may include Customer Data. Not used to train Anthropic models under their API terms.USA
OpenAI, L.L.C.LLM inference (alternate provider)Prompt content that may include Customer DataUSA
Microsoft CorporationTransactional email via Exchange Online (MX for hellosaasy.ai)Recipient address and transactional email bodyUSA
Plaid, Inc.Bank-account connection and ongoing transaction/balance sync when a tenant connects a bankAccount-holder name, account/routing last-4, balances, and full transaction history. Plaid holds its own copy under its retention policy.USA

Questions: privacy@hellosaasy.ai. Related: Privacy Policy and DPA.