Subprocessors

Purpose

This page identifies how Formerie will publish production subprocessors and related customer notice information.

Production subprocessors are not finalized in this website scaffold. Before Formerie processes production customer submission data, this page should list each active production subprocessor and the purpose of processing.

What is a subprocessor?

A subprocessor is a third-party service provider that processes customer personal data on behalf of Formerie so Formerie can provide the service.

Subprocessors may help with hosting, storage, authentication, email delivery, billing, support, observability, security, analytics, or similar service operations.

Expected production list format

The production list should include, where applicable:

• Provider name.
• Service purpose.
• Categories of data involved.
• Processing location or region where known.
• Security or privacy documentation link.
• Date added.
• Whether the provider is required for core service operation or optional feature use.

Expected categories

Expected categories may include:

• Cloud hosting and edge runtime.
• Database and object storage.
• Queueing and asynchronous job processing.
• Transactional email delivery.
• Customer authentication.
• Billing and subscription management.
• Product analytics and operational metrics.
• Error monitoring and observability.
• Customer support tooling.
• Security, abuse prevention, and incident response.

Customer notice

Formerie should provide a practical notice mechanism for material subprocessor changes where required by customer agreements or applicable law.

Notice may be provided through the website, customer app, email, changelog, or another reasonable method.

Customers with a contractual objection right should follow the process in their applicable agreement.

Subprocessor obligations

Formerie should require subprocessors to protect customer data using appropriate confidentiality, security, and data-protection obligations.

Subprocessors should be allowed to process customer data only as needed to provide the contracted service to Formerie or as otherwise permitted by the applicable agreement.

Provider credentials and templates

Provider credentials, delivery rules, and templates remain server-side. Public form clients must never supply recipients, provider credentials, or email templates.

If customers configure their own providers in the future, Formerie should store credentials securely and use them only for the configured customer service purpose.

Current launch status

The public launch scaffold should not be treated as a final production subprocessor list. The final list must be completed after the production hosting, auth, billing, delivery, analytics, support, and security providers are selected.