Skip to content
Subprocessors

Transparency across the service supply chain.

See the categories of providers used to host, secure, support, bill for and operate Zavyra, with a clear route to request the contract-specific list.

Review the public categoriesUnderstand why each type of provider is needed and what data context can be involved.
Request the contract listAsk for relevant legal entities, regions and safeguards for the intended service scope.
Track material changesUse the notice process defined in the signed Data Processing Agreement.
Subprocessor transparency

Service categories, processing purpose and review path.

Zavyra uses service providers only where needed to operate, secure, support or bill for the platform. The exact provider used can depend on the customer plan, region and enabled feature.

Current processing categories

CategoryPurposeData context
Cloud infrastructure and hostingRun application, database, storage, networking and backups.Account and workspace data required to provide the service.
Payments — StripeSubscription checkout, billing and payment administration.Billing identity, subscription and payment references; card data is handled by the payment provider.
AI services — including OpenAI where enabledGenerate user-requested content, classifications or recommendations.Only content selected or required for the invoked AI feature.
Email and customer supportDeliver service messages and handle support requests.Contact details and support correspondence.
Monitoring and securityDetect failures, abuse and security events.Technical telemetry, IP address, logs and event context.
Connected commerce providersPerform the integration explicitly selected by the customer.Provider account and commerce data within the authorized scope.

Provider names and regions

A contract-specific list, including relevant legal entities and transfer locations, is available from office@zavyra.com and may vary by enabled service.

Changes

Material changes are handled under the applicable Data Processing Agreement and communicated through the agreed channel.

No hidden connection

A commerce provider is not treated as connected until the customer starts and completes its authorization flow.

Subprocessors

Built for clear, connected operations.

Explore the workflows described below. Available actions depend on the connected service, account permissions and selected plan.

Infrastructure

Hosting, storage, networking and backup services required to run Zavyra.

  • Service delivery
  • Resilience
  • Technical operations

Billing providers

Payment processing and subscription administration without Zavyra storing raw card data.

  • Stripe
  • Invoices
  • Subscription references

AI providers

User-requested AI features may use selected content needed for the invoked task.

  • Feature-specific use
  • Visible purpose
  • Customer choice

Monitoring and support

Providers may support service email, error detection, abuse prevention and customer assistance.

  • Technical telemetry
  • Support correspondence
  • Security context
How teams use it

From source data to a clear next move.

  1. 01Review the public categories

    Understand why each type of provider is needed and what data context can be involved.

  2. 02Request the contract list

    Ask for relevant legal entities, regions and safeguards for the intended service scope.

  3. 03Track material changes

    Use the notice process defined in the signed Data Processing Agreement.

Explore more

Continue through the Zavyra platform.

Data processing agreementDocumented safeguards for customer-controlled data.Privacy controlsDisconnect integrations and request data deletion.Security at ZavyraBuilt for secure commerce operations.
Frequently asked questions

Clear answers before you connect.

Why are provider categories shown instead of a universal list?

The exact provider and legal entity can vary by plan, region and enabled feature. A contract-specific list is available on request.

Does opening an integration page connect that provider?

No. A commerce provider is connected only after the customer starts and completes its authorization flow.

How are material changes handled?

Changes are handled under the applicable DPA and communicated through the agreed notice channel.

Your next step

Explore the options for your workspace.

Review availability, choose the capabilities you need and keep provider access under your control.

Request the current list Read the DPA summary