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.
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.
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.
| Category | Purpose | Data context |
|---|---|---|
| Cloud infrastructure and hosting | Run application, database, storage, networking and backups. | Account and workspace data required to provide the service. |
| Payments — Stripe | Subscription checkout, billing and payment administration. | Billing identity, subscription and payment references; card data is handled by the payment provider. |
| AI services — including OpenAI where enabled | Generate user-requested content, classifications or recommendations. | Only content selected or required for the invoked AI feature. |
| Email and customer support | Deliver service messages and handle support requests. | Contact details and support correspondence. |
| Monitoring and security | Detect failures, abuse and security events. | Technical telemetry, IP address, logs and event context. |
| Connected commerce providers | Perform the integration explicitly selected by the customer. | Provider account and commerce data within the authorized scope. |
A contract-specific list, including relevant legal entities and transfer locations, is available from office@zavyra.com and may vary by enabled service.
Material changes are handled under the applicable Data Processing Agreement and communicated through the agreed channel.
A commerce provider is not treated as connected until the customer starts and completes its authorization flow.
Explore the workflows described below. Available actions depend on the connected service, account permissions and selected plan.
Hosting, storage, networking and backup services required to run Zavyra.
Payment processing and subscription administration without Zavyra storing raw card data.
User-requested AI features may use selected content needed for the invoked task.
Providers may support service email, error detection, abuse prevention and customer assistance.
Understand why each type of provider is needed and what data context can be involved.
Ask for relevant legal entities, regions and safeguards for the intended service scope.
Use the notice process defined in the signed Data Processing Agreement.
The exact provider and legal entity can vary by plan, region and enabled feature. A contract-specific list is available on request.
No. A commerce provider is connected only after the customer starts and completes its authorization flow.
Changes are handled under the applicable DPA and communicated through the agreed notice channel.
Review availability, choose the capabilities you need and keep provider access under your control.