Skip to content
Log in
All legal documents

Subprocessors & Service Providers

Effective date: November 1, 2026

On this page
  1. 1 Purpose
  2. 2 Current provider register
  3. 3 Supabase
  4. 4 Vercel
  5. 5 Inngest
  6. 6 Amazon SES
  7. 7 Telnyx
  8. 8 Stripe
  9. 9 GitHub
  10. 10 Agencies, integrations and networks
  11. 11 Locations and transfers
  12. 12 Changes and objections
  13. 13 Contact

1. Purpose

This page identifies Sendra’s confirmed external technology providers and distinguishes their functions.

A subprocessor processes Merchant Personal Data on Sendra’s behalf.

An independent provider may determine purposes for specified activities under its own legal responsibilities.

A provider can perform more than one role. Its brand name does not establish its role for every information category.

2. Current provider register

ProviderFunctionInformation involved, to the extent supplied
SupabaseManaged database infrastructure, database encryption at rest and database-backup servicesMerchant and contact records, application configuration, relevant integration credentials and associated database information
VercelApplication hosting and deployment infrastructureApplication requests, relevant runtime information, technical metadata and operational records
InngestEvent-driven workflows and background-job orchestrationEvent payloads, task inputs and outputs, workflow status and related execution information
Amazon Web Services · Amazon SESEmail delivery infrastructureSender and recipient information, message content and relevant delivery or abuse information
TelnyxSMS/MMS delivery and relevant sender verificationTelephone numbers, message content, delivery information and business/program registration information
StripePayment processing and related billing functionsBilling details, transaction information, payment references and relevant fraud information
GitHubSource-code management, development collaboration and related software-delivery functionsDeveloper information, repository content, development and deployment metadata, and any limited diagnostic information appropriately supplied

The listed data categories describe the potential service scope; they do not authorize unnecessary disclosure.

3. Supabase

Supabase supplies the confirmed database and backup infrastructure.

Backups follow the applicable plan and configuration. No particular seven-, fourteen- or thirty-day period is represented by this page.

Database backups must not be assumed to include every object stored through a separate storage service.

Sendra remains responsible for appropriate configuration, access management and its own data-handling obligations.

4. Vercel

Vercel hosts the application and may process relevant requests and runtime information.

The location of the hosting provider’s corporate office does not establish the location of all execution, logging or access.

Any residency commitment requires confirmation of the actual deployment and associated services. Vercel’s own documentation describes a geographically distributed service infrastructure. Vercel

5. Inngest

Inngest supports workflow and event processing.

Event inputs, outputs and execution records can contain personal information where Sendra includes that information in the workflow.

Inngest must not be described as receiving only anonymous identifiers unless the actual payloads and retained execution information support that claim.

Payloads must be limited to the relevant task. Inngest’s documentation confirms that its service works from submitted event data and maintains workflow-related information. Inngest

6. Amazon SES

Amazon SES processes information necessary for configured email delivery and related operations.

Use of SES does not establish that all other Sendra systems or backups are hosted by AWS.

The relevant contracting entity and configured regions must be determined from Sendra’s actual AWS account and agreements.

Sendra’s security responsibilities include its own configuration and management of AWS services. AWS Documentation

7. Telnyx

Telnyx processes message content for relevant service-delivery purposes.

Its arrangements distinguish that content from account and communications-usage information for which it may act independently.

Sendra must accurately assess and disclose those differences. The provider must not be represented as acting solely on Sendra’s instructions for every activity. Telnyx

8. Stripe

Stripe supports customer payments and may act as processor or independently depending on the activity.

Merchant subscriber lists should not be supplied merely because Stripe processes Sendra’s subscription payments.

Use of Stripe does not itself make Stripe Sendra’s merchant of record. Its privacy materials distinguish its roles across different services. Stripe

9. GitHub

GitHub is identified as a development provider, not as the routine subscriber database.

Production subscriber datasets, payment secrets and integration credentials must not be unnecessarily committed to repositories or development records.

If Merchant Personal Data is included in development, diagnostic or delivery processes, the relevant processing must be assessed and protected. GitHub’s role depends on the service and relationship involved. GitHub Docs

10. Agencies, integrations and networks

A merchant-authorized ecommerce platform is not automatically Sendra’s subprocessor.

An agency’s role depends on the merchant’s authorization and actual arrangements.

Carriers and communications networks may have independent duties. Their involvement must be addressed through the relevant provider arrangements.

11. Locations and transfers

Sendra does not promise a particular country of storage or access unless expressly agreed.

The actual provider legal entities, deployment regions, remote-access locations and transfer mechanisms must be maintained in Sendra’s vendor records and supplied where reasonably necessary for due diligence or a required transfer arrangement.

A provider’s headquarters is not a substitute for identifying actual processing locations.

Before a restricted transfer, Sendra must establish the necessary safeguards rather than relying only on this general register.

12. Changes and objections

Direct subprocessor changes follow the Data Processing Agreement, including its 30-day advance-notice and reasonable-objection process.

Customers may contact legal@mailsendra.com with relevant data-protection concerns.

Independent provider activities are subject to their applicable transparency and legal requirements and must not be concealed within a generic subprocessor authorization.

13. Contact

legal@mailsendra.com
Legal

Terms and privacy

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement

Policies

  • Acceptable Use Policy
  • Email & SMS Messaging Policy
  • Billing & Refunds Policy

Trust

  • Subprocessors
  • Security
  • Report abuse

On this page

  1. 1 Purpose
  2. 2 Current provider register
  3. 3 Supabase
  4. 4 Vercel
  5. 5 Inngest
  6. 6 Amazon SES
  7. 7 Telnyx
  8. 8 Stripe
  9. 9 GitHub
  10. 10 Agencies, integrations and networks
  11. 11 Locations and transfers
  12. 12 Changes and objections
  13. 13 Contact

Email and SMS marketing for Shopify stores.

Customer service
info@mailsendra.com
Legal, privacy, abuse and security
legal@mailsendra.com

Terms and privacy

  • Terms of Service
  • Privacy Policy
  • Data Processing Agreement

Policies

  • Acceptable Use Policy
  • Email & SMS Messaging Policy
  • Billing & Refunds Policy
  • SMS program terms

Trust

  • Subprocessors
  • Security
  • Report abuse

© 2026 SENDRA INC. All rights reserved.

All legal documents