Skip to content
sendalto.
ProductSolutionsIntegrationsPricing
RULog inGet started
ProductSolutionsIntegrationsPricingFor B2B teamsSecurityLog in
TRANSPARENCY
Service terms — readiness noticePrivacy — processing and readinessData processing agreement — readinessAcceptable use and sending boundariesSubprocessor inventory — readinessSupport, privacy and abuse contacts
Production-readiness notice

Subprocessor inventory — readiness

This is a configuration-dependent inventory, not a finalized contractual subprocessor list. Provider adapters do not mean that every provider is currently enabled.

Operator identity, contractual terms and verified contact details are still required before production use. This page is not legal advice or a compliance certification.

1. Hosting, database, storage and network

The deployed host, PostgreSQL storage, backups, optional S3-compatible storage and network/CDN services must be inventoried by the operator. Exact contracting entities, processing locations, retention, security obligations and transfer terms have not been published here. Do not infer EU-only residency from the hosting plan.

2. Email and CRM connections

Optional adapters include Amazon SES, Google Gmail, Microsoft Graph, SMTP/IMAP providers and HubSpot. They may receive recipient addresses, message content, mailbox data or CRM records according to the enabled connection. A customer-connected service may have a direct customer relationship; roles must be determined from the actual agreement.

3. AI and payments

OpenAI is the configured AI adapter; Stripe is the platform billing adapter. Relevant approved context or billing metadata is processed only when the respective service is configured and used. Final entity names, models/endpoints, regional availability, retention and contractual safeguards require operator review before production.

4. Publication and change process required

Before production, publish a dated inventory with legal names, purposes, data categories, countries and applicable safeguards, plus a verified channel and policy for change notifications and objections. This page does not represent provider endorsement, certification or executed contractual safeguards.

Read alongside the security overview and the integration-specific requirements. Any final agreement must match the deployed service, not an aspirational roadmap. Security overview →
sendalto.

Thoughtful emails. Meaningful conversations.

Built for teams, not for spam.

Explore

ProductFor SaaSFor B2B teamsPricing

Trust & transparency

SecurityIntegrationsSubprocessorsSupport & abuse

Legal readiness

TermsPrivacyData processingAcceptable use
© 2026 SendaltoOperator and contractual details must be finalized before production use.