My Wedding Office
Subprocessors
This page describes the main service providers and subprocessors that may process personal data in connection with MWO. Some providers apply only when you enable a specific feature, connect an external account, or select a given configuration.
| Provider | Purpose | Data categories | Notes |
|---|---|---|---|
| Supabase | Authentication, sessions, user identity. | Account data, email address, user identifiers, login metadata. | Used for Supabase Auth and related account processes. |
| Amazon Web Services (S3, CloudFront, SES) | File storage, CDN, transactional email sending. | Service and customer files, documents, images, email addresses, transactional message content, technical metadata. | Scope depends on feature and configured region. |
| Stripe | Payments, subscriptions, invoices, customer portal, Stripe Connect in quote-to-cash. | Billing data, customer identifiers, payment status, invoices, subscription metadata. | Stripe may also act as an independent controller for some payment data. |
| Login, Gmail, Google Calendar, Google Business Profile, Maps/Places. | User-authorized email, calendar, review, location, token, and metadata. | Only when the user enables or connects Google features. | |
| Meta/Facebook | Social login, Meta webhooks, Chrome extension capture for Facebook leads. | Account identifiers, publicly visible content or metadata captured by the user, webhooks, integration tokens. | Only for configured features and subject to platform rules. |
| OpenAI | AI features: drafts, suggestions, summaries, insights. | Inputs, context, outputs, and metadata needed to perform the AI feature. | Data scope depends on feature and configuration. |
| Sentry | Frontend/backend error monitoring and diagnostics. | Error logs, paths, device information, user or workspace identifiers, limited metadata. | We aim to redact secrets and tokens, but the tool may receive personal data. |
| PostHog | Optional product analytics. | User or workspace identifiers, product usage events, technical device and browser data, approximate IP-derived location, and session data. | Enabled after user consent where required. Autocapture, automatic pageviews, heatmaps, and session recordings are currently disabled. Host depends on configuration; with PostHog EU Cloud, events are routed to the EU host without guaranteeing EEA-only processing. |
| Mailgun or AWS SES | Custom email, relay, transactional emails. | Email addresses, delivery metadata, message content, webhook statuses. | Use depends on email configuration. |
| DocuSeal | Platform-managed electronic signature in quote-to-cash. | Documents, signers, email addresses, signature statuses, audit logs. | Planned/configurable; scope depends on rollout. |
| Dropbox Sign, DocuSign, Autenti | User-connected e-sign providers. | Documents, signers, statuses, OAuth tokens, signature metadata. | Only if the user selects and connects that provider. |
Subprocessor Changes
We may update this list when we add, change, or remove providers. If you need advance notice of material subprocessor changes under the DPA, contact contact@myweddingoffice.com.