Last reviewed: 2 April 2026
This page lists the direct Riverbank subprocessors we are currently comfortable naming publicly based on the codebase and maintained GDPR inventory. It also separates customer-configured downstream services that may receive personal data because a site owner enables or configures them.
Read this alongside our Data Processing Addendum (Draft) and Privacy Policy.
These are the providers Riverbank relies on directly to operate platform infrastructure, payments, observability, email delivery, or optional AI processing.
Observability and logging · Core platform service
Operational logging, observability, and troubleshooting.
Typical data categories
Transfer note: Provider contractual commitments or similar documented safeguards
Email delivery · Optional feature or transport
Transactional email delivery when the Mailgun transport is configured.
Typical data categories
Transfer note: Provider contractual commitments or similar documented safeguards
AI-assisted processing · Optional feature or transport
Optional AI-assisted media classification, embeddings, and related processing.
Typical data categories
Transfer note: Provider contractual commitments or similar documented safeguards
Email delivery · Optional feature or transport
Transactional email delivery when the Resend transport is configured.
Typical data categories
Transfer note: Provider contractual commitments or similar documented safeguards
Payments · Optional feature or transport
Payment processing, refunds, disputes, and connected-account payment operations.
Typical data categories
Transfer note: Provider contractual commitments or similar documented safeguards
Hosting, storage, and authentication · Core platform service
Database, authentication, and object storage for platform and site data.
Typical data categories
Transfer note: Provider contractual commitments or similar documented safeguards
Hosting, storage, and authentication · Core platform service
Application hosting, deployment, delivery, and runtime infrastructure.
Typical data categories
Transfer note: Provider contractual commitments or similar documented safeguards
These recipients are not presented as direct Riverbank subprocessors. They are enabled or selected by a site owner as part of their own operational setup and may still receive personal data through the platform.
Customer-configured integrations · Optional feature or transport
Delivery of outbound webhook payloads to endpoints chosen by the site owner.
Typical data categories
Transfer note: Customer-managed connection or destination
These recipients are selected by the customer and may fall outside Riverbank's direct subprocessor set.
Customer-configured integrations · Optional feature or transport
Customer-enabled calendar syncing and availability checks for booking resources.
Typical data categories
Transfer note: Customer-managed connection or destination
This recipient is customer-enabled and tied to a customer-managed Google connection rather than a core always-on Riverbank subprocessor relationship.
Customer-configured integrations · Optional feature or transport
Optional import and media-ingestion flows initiated by the customer.
Typical data categories
Transfer note: Customer-managed connection or destination
Riverbank intends to keep this page updated when direct subprocessors or customer-facing processor materials change. Until a more formal notification workflow exists, this page acts as the maintained publication point for changes to the public subprocessor list.
