1.Subprocessors we use
These providers process personal information for every workspace to host, secure and deliver AIPageBuilder. Each works under a written agreement with data-protection terms. See the Data Processing Addendum for how we choose and oversee them.
| Name | Purpose | Personal data | Location |
|---|---|---|---|
| Vercel | Application hosting, content delivery, custom domains and serverless functions | All data in transit through the app; request logs (IP address, user agent) | United States (global edge network) |
| Supabase | Database, authentication and file storage | Account data, workspace data, end-customer contact and booking data, uploaded files | United States |
| Stripe | Subscription billing, payment processing and Stripe Connect payouts | Name, email, billing address, payment card and bank details, transaction history | United States |
| Resend | Transactional and marketing email delivery | Recipient name and email address, email content, delivery and engagement events | United States |
| Anthropic | AI text and image understanding (content generation, assistants) | Prompts and content you submit to AI features, which may include personal information | United States |
| OpenAI | AI text generation fallback and image generation | Prompts and content you submit to AI features, which may include personal information | United States |
| OpenRouter | Routing AI requests to model providers | Prompts and content you submit to AI features, which may include personal information | United States |
| Inngest | Background jobs, scheduled tasks and automation workflows | Event payloads, which can include contact identifiers and workflow data | United States |
| Upstash | Rate limiting and short-lived caching (Redis) | IP addresses and account or workspace identifiers used as rate-limit keys | United States |
| PostHog | Product analytics, and session replay on published pages where the customer enables it | Usage events, device and browser data, IP-derived location, session recordings (inputs masked) | United States |
| Sentry | Error monitoring and performance diagnostics | Error reports, stack traces, device and browser data, user and workspace identifiers | United States |
2.Optional integrations you connect
These services receive personal information only if a customer connects them to their workspace, using their own account with that provider. The provider’s own terms and privacy policy apply to that connection, and the customer can disconnect it at any time.
| Name | Purpose | Personal data | Location |
|---|---|---|---|
| Google (Calendar, Gmail, Meet, Sign in with Google) | Calendar sync, Meet links, inbox sync and sending from a connected Gmail account, Google sign-in | Calendar events and availability, email messages and contacts in the connected mailbox, profile name and email | United States |
| Microsoft (Outlook mail and calendar) | Calendar sync and inbox sync through Microsoft Graph | Calendar events and availability, email messages and contacts in the connected mailbox | United States |
| Zoom | Creating meeting links for bookings | Meeting topic, time and attendee details | United States |
| Apple (iCloud Calendar via CalDAV) | Calendar sync with iCloud | Calendar events and availability | United States |
| Vapi Not generally available in V1; processes data only when a customer adds their own Vapi key. | AI voice agents using the customer's own Vapi account | Call audio, transcripts, caller phone number | United States |
3.Changes to this list
We will update this page at least 30 days before a new subprocessor starts processing personal information and notify workspace owners by email. To object to a change, or for questions, contact support@aipagebuilder.app.