> ## Documentation Index
> Fetch the complete documentation index at: https://legal.essal.it.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Service providers and subprocessors

> See the providers confirmed for Essal's environment and distinguish software suppliers, processors and independent transaction or analytics controllers.

**Last updated: 18 November 2026.**

Essal uses the providers below in its service environment. A provider's inclusion does not mean every product sends it customer content, or that every provider acts as a subprocessor for every purpose.

| Provider or software | Role in the environment | Product-specific information |
| - | - | - |
| Cloudflare | Network and infrastructure services | Enabled services, data handled, contracting entity, processing/remote-access locations and transfer safeguards |
| Railway | Application hosting and hosting of the authentication software | Application/database/backup regions, data handled, contracting entity and safeguards |
| Resend | Email delivery | Product messages and recipient data, contracting entity, locations and safeguards |
| Better Auth | Authentication software hosted on Railway | Treat as software in the hosted stack; identify any separate external service before listing it as a recipient |
| PostHog | Optional analytics, subject to consent | Hosted or self-hosted instance, consent configuration, events collected, entity, locations and retention |
| Google Analytics | Optional analytics, subject to consent | Property configuration, events collected, entity, locations and retention |
| Mintlify | Hosting and delivery of this legal center | Legal-site visitor information; not automatically a recipient of customer tenant content |
| Netlify | Hosting of the marketing website identified during implementation | Marketing-site requests and any enabled forms/functions; not automatically a tenant-data subprocessor |

The stated application regions are Doha and Germany, selected by proximity. This is not a claim that email, global network services, analytics, remote support or every backup stays in those locations.

## Paddle's separate role

Paddle handles purchases for transactions where it is identified as the seller and Merchant of Record. It has independent purposes and obligations under its [privacy notice](https://www.paddle.com/legal/privacy) and applicable data-sharing terms. Do not treat Paddle as a universal Essal tenant-data subprocessor.

## Authorisation and changes

The [DPA](https://legal.essal.it.com/data-processing.md) requires prior written subprocessor authorisation. The accepted product schedule must identify which providers are actually authorised for the customer's processing. Advance change information and the opportunity to object follow that agreement. The customer-specific processing schedule records the authorised recipients and applicable transfer safeguards.

Ask [legal@essal.it.com](mailto:legal@essal.it.com) for the applicable product schedule or to raise a data-protection objection. Do not send tenant records or credentials merely to request the list.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.