Relisend

Legal & data governance

Subprocessor register

Version 2026-08-13Effective 13 August 2026

Providers planned or enabled to support the Relisend service.

Production contracts, processing regions and safeguards must be verified before launch.
Launch configuration incomplete. Relisend's verified operator name, service address, and representative must be configured before this register is relied upon publicly.
01

Subprocessor register

The table below lists the providers planned or enabled to support the Relisend service.

ProviderPurposeDataSafeguard status▱ HostingerApplication/database hostingAccount, configuration, operations△ Contract and region to verify☁ CloudflareDNS, edge and access securityIP, request, security metadata♢ DPF/SCCs as applicable✉ OpenSRS / TucowsMailbox and domain servicesDomain, mailbox, messages△ Terms and transfer mechanism to verify▭ Stripe / Paystack / Flutterwave / PaddlePayment processingContact, order, transaction referencesⓘ Only selected checkout provider▯ ExpoMobile build, update and pushDevice token and delivery metadata△ Provider safeguards to verify▤ OpenAI / GoogleOptional writing / Drive featuresUser-submitted content only⊘ Disabled unless configured and invoked
02

How provider use is controlled

We follow a simple process to ensure providers are only used when needed and with appropriate safeguards.

Provider needed
Configuration or checkout selection
Applicable safeguards verified
Limited data shared for the stated purpose
03

Our commitments

We apply the following principles to our use of subprocessors.

Purpose-limited sharingWe share only the data needed for each provider’s stated purpose.
Conditional integrationsSome providers are only used if a feature is configured or selected at checkout.
Change objectionsWe will consider reasonable objections to material changes to this register.