Overview
This page lists the core third-party subprocessors and service providers that Mobyform may use to operate the public website and hosted product. We update this page when the baseline vendor set changes in a material way.
This page focuses on Mobyform-operated vendors. It does not attempt to list every third-party integration that a customer may choose to connect to their own systems.
How to Read This List
- A vendor may process different categories of data depending on the feature in use.
- Some vendors are only involved if a customer uses a specific optional feature, such as billing.
- Some infrastructure choices can vary by deployment, environment, or region.
Core Vendors
| Vendor | Purpose | Typical Data Involved | Scope |
|---|---|---|---|
| Cloudflare | DNS, CDN, edge delivery, traffic filtering, request handling, custom domain routing | IP address, request metadata, cached assets, security events, edge routing information | Public website, docs, help pages, public forms, and hosted traffic |
| Resend | Transactional email and newsletter delivery | Recipient email address, sender metadata, template content, delivery events | Contact flows, support follow-up, transactional messages, newsletter operations |
| Stripe | Subscription billing and payment processing when Stripe is active | Billing contact details, subscription metadata, payment transaction details | Paid plans, checkout, invoices, refunds, subscription lifecycle |
| Creem | Subscription billing and payment processing when Creem is active | Billing contact details, subscription metadata, payment transaction details | Paid plans, checkout, invoices, refunds, subscription lifecycle |
Stripe and Creem are alternative billing providers. In a given hosted billing environment, only one of them is typically the active checkout processor at a time.
Deployment-Dependent Infrastructure
Depending on the active deployment, Mobyform may also use a configured storage backend for uploads and generated assets. The product architecture supports Alibaba Cloud OSS, Amazon S3 or S3-compatible storage, Google Cloud Storage, Azure Blob Storage, and local or customer-managed storage. The exact vendor may vary by deployment, environment, region, or customer-managed setup, so not every possible storage backend appears here as a baseline Mobyform-operated subprocessor.
Optional analytics, monitoring, or anti-abuse vendors may also vary by deployment and are only in scope when enabled in the active production environment.
What Is Not Included Here
This page does not list:
- customer-controlled downstream integrations chosen by the customer
- customer-managed downstream systems outside the hosted Mobyform product
- ephemeral tools used for one-off internal operations that do not process customer-controlled data in the ordinary course
Subprocessor Management
When we engage subprocessors, we expect them to:
- process data only for authorized purposes
- operate under contractual privacy and confidentiality obligations
- maintain safeguards appropriate to the services they provide
Related Pages
Contact
If your security or procurement team needs more detail about a listed vendor, contact support@mobyform.com.