# Zupost ## Data Processing > Category: Resources --- ## Pages ### Getting started - [What is Zupost?](https://docs.zupost.com/getting-started/what-is-zupost) - [Rate Limits](https://docs.zupost.com/getting-started/rate-limits) ### Quickstart - [Node.js](https://docs.zupost.com/quickstart/node-js) ### Resources - [Security](https://docs.zupost.com/resources/security) - [Acceptable Use](https://docs.zupost.com/resources/acceptable-use) - [Data Processing](https://docs.zupost.com/resources/data-processing) --- # Data Processing This page explains how Zupost approaches data processing in relation to infrastructure partners and subprocessors. For customers evaluating Zupost, this is an important topic. Email delivery platforms process operational data by design, and trust depends not only on what the product does, but also on which external providers are involved, for what purpose, and how intentionally those choices are made. Zupost is built with a strong Europe-first direction. That applies not only to product positioning, but also to infrastructure decisions. We deliberately aim to keep the platform operationally independent, understandable, and aligned with a more sovereign European technology stack wherever practical. ## Our approach We believe data processing should be as deliberate as possible. That means: - using subprocessors only where they serve a clear operational purpose - keeping the list of subprocessors limited - preferring European providers where possible, especially for core infrastructure - avoiding unnecessary outsourcing of critical delivery functions - being transparent about the categories of providers involved Zupost operates its own email sending infrastructure and does not rely on a third-party cloud email sending backend for message delivery. This is an intentional architectural choice and an important part of our broader platform direction. ## What we mean by subprocessors In the context of Zupost, subprocessors are third-party service providers that may process data on our behalf as part of operating the platform. These providers are not used casually. They are selected to support specific parts of the service, such as infrastructure, hosting, edge delivery, or billing. Not every provider plays the same role, and not every provider touches the same categories of data. Their involvement depends on the function they provide within the platform. ## Why subprocessors matter For many customers, especially teams with privacy, compliance, or infrastructure sovereignty requirements, the subprocessor model matters for several reasons: - it helps clarify where data may be processed - it shows how much of the stack is directly controlled by Zupost - it gives customers a better understanding of infrastructure dependencies - it provides transparency for procurement, legal, and security review processes We think this level of transparency should be standard, not exceptional. ## Our current subprocessors At this time, Zupost uses the following subprocessors and infrastructure partners. ### Hetzner - **Legal entity:** Hetzner Online GmbH - **Address:** Industriestr. 25, 91710 Gunzenhausen, Germany - **Role:** Infrastructure and hosting Hetzner is used for infrastructure-related workloads within the Zupost platform. This aligns with our Europe-first infrastructure direction and our preference for providers that help us maintain a more sovereign and operationally controlled stack. ### IONOS - **Legal entity:** IONOS SE - **Address:** Elgendorfer Str. 57, 56410 Montabaur, Germany - **Role:** Infrastructure and hosting IONOS is used for infrastructure-related services within the Zupost platform. Like other core infrastructure choices at Zupost, this reflects our preference for European providers where possible, particularly in areas that are foundational to platform operation. ### Bunny - **Legal entity:** BunnyWay d.o.o. - **Address:** Dunajska cesta 165, 1000 Ljubljana, Slovenia - **Role:** Edge and supporting infrastructure services Bunny is used for supporting infrastructure-related functions within the Zupost platform. Where edge delivery, asset distribution, or similar supporting services are needed, we prefer providers that fit our broader operational and regional priorities. ### Stripe - **Legal entity:** Stripe Payments Europe, Limited - **Address:** 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland - **Role:** Billing and payment processing Stripe is used for billing and payment-related functions. Stripe is not part of the core email delivery path, but it may process customer-related billing information where necessary to support commercial operations and subscriptions. ## How we think about European sovereignty European sovereignty is not a decorative label for Zupost. It directly influences how we think about infrastructure and provider selection. In practice, that means: - we do not use a third-party cloud email sending backend for core delivery - we prefer European infrastructure providers for foundational platform components - we aim to keep the operational stack understandable and intentionally chosen - we try to minimize unnecessary dependency on large external platforms where reasonable alternatives exist At the same time, we want to be realistic and honest. Not every operational function can always be served by the exact same provider profile, and some support functions may still require external services that are widely used in software businesses. Our goal is not purity for its own sake. Our goal is deliberate, responsible, and transparent choices. ## Categories of data that may be processed Depending on the role of the provider, subprocessors may process categories of data such as: - account and workspace information - technical configuration data - infrastructure-level operational metadata - billing and payment-related information - service usage data necessary for operating the platform - limited support and diagnostic data where operationally required The exact categories depend on the service involved and the role it plays in the platform. ## Core delivery philosophy A central part of Zupost’s architecture is that we operate our own SMTP delivery infrastructure instead of outsourcing message sending to another email delivery platform. This matters because it reduces dependency on an external sending provider for the most critical part of the product: the actual delivery layer. For customers, this means Zupost is not simply acting as a thin wrapper around another major email backend. We consider direct operational ownership of the delivery path an important part of both product quality and infrastructure independence. ## Data minimization and operational discipline We aim to keep data processing proportionate to what is actually required to operate the service. That means we try to: - avoid unnecessary provider sprawl - avoid unnecessary data exposure - keep infrastructure choices intentional - reduce dependence on third parties where direct operation is the better fit - choose subprocessors for specific operational reasons, not convenience alone Customers also play an important role here. The data sent through Zupost depends in part on how customers structure templates, variables, recipients, and workflows. Good data hygiene at the customer level remains important. ## Reviewing and updating subprocessors Our subprocessor list may change over time as the platform evolves. This can happen, for example, when: - infrastructure needs change - we improve reliability or performance - we replace a provider with a better-fit alternative - legal, operational, or regional requirements change When changes are made, we aim to keep this page current so customers can review the providers involved in operating the platform. ## Questions from customers We understand that many customers, especially B2B teams, need more than a short marketing statement. They may need to understand the operational stack, the regional infrastructure direction, and the role of external providers before onboarding. If your organization needs additional details regarding subprocessors, infrastructure scope, or data-processing documentation, please contact us. ## Related pages For more information about how we approach platform protection and operational security, see our [Security](/resources/security) page. For questions related to data processing or infrastructure partners, contact: **[privacy@zupost.com](mailto:privacy@zupost.com)**