The providers below may process limited data for the stated purpose. A provider is used only when its related feature, model, payment method or deployment component is enabled. Creavax should update this list before adding a materially different provider.
Service operator
Section 01
| Provider or category | Purpose | Data involved | When used |
|---|---|---|---|
| OVH | Application hosting, networking, logs and operational security. | Account requests, IP addresses, logs and encrypted application traffic. | For the production deployment. |
| S3-compatible object storage selected by the operator | Private uploads, generated assets, backups and signed downloads. | Files, asset metadata and storage identifiers. | When object storage is enabled. |
| Resend (primary); Google Gmail SMTP (fallback) | Transactional email, verification, password recovery and service notices. | Email address, message content and delivery metadata. | When email delivery is enabled. |
Section 02
| Provider | Purpose | Data involved | When used |
|---|---|---|---|
| OpenRouter | Routing requests to supported text and media models. | Prompt, selected attachments, model settings and request metadata. | Only for an OpenRouter-backed model. |
| fal.ai | Image, video, audio, upscale, edit and 3D processing. | Prompt, selected input files, model settings and callback metadata. | Only for a fal.ai-backed model. |
| OpenAI | Managed text or support features configured by the operator. | Prompt and conversation context needed for the request. | Only when the OpenAI integration is enabled and selected. |
| Google Gemini | Managed text or support features configured by the operator. | Prompt and conversation context needed for the request. | Only when the Gemini integration is enabled and selected. |
Section 03
| Provider | Purpose | Data involved | When used |
|---|---|---|---|
| NOWPayments | Crypto checkout, status confirmation and refunds. | Order identifier, amount, currency, payment status and wallet-related transaction metadata. | Only when the user chooses a supported crypto checkout. |
| Zarinpal | Iranian payment checkout and verification. | Order identifier, amount, callback and payment status. | Only when the user chooses Zarinpal and the gateway is enabled. |
| Stripe | Card or supported payment processing. | Customer, checkout and payment status data; sensitive card data is handled by Stripe. | Only when Stripe is enabled and selected. |
| PayPal | PayPal checkout and payment confirmation. | Customer, order and payment status data. | Only when PayPal is enabled and selected. |
Section 04
None unless enabled with consent is the configured analytics position for this release. Optional analytics and marketing tools must remain disabled until the cookie policy, consent interface, retention period and transfer safeguards identify the actual provider and data fields.
Section 05
Creavax may replace a provider with an equivalent service after reviewing security, privacy and transfer requirements. Material changes should be posted before the new provider begins processing where required. Users may contact privacy support with questions or objections that apply under local law.
Contact privacy support