Virali subprocessors

Active and conditional providers

• Stripe: payment processing and recurring subscription management; billing contacts, customer/subscription identifiers, payment and consent metadata. Active for paid billing. Stripe handles card data rather than Virali storing full card details.
• Render: application hosting and service runtime; workspace account data, logs, and configuration metadata.
• Supabase: PostgreSQL database, authentication, storage, and backups; application data, authentication data, files, and logs.
• Resend or configured SMTP provider: transactional email; email address and delivery metadata.
• Google APIs and Gmail: enabled user-authorized email, calendar, and file workflows; connected account identity, relevant message/thread or calendar metadata, files, and encrypted OAuth credentials.
• Bright Data: enabled creator/content analytics workflows; public social-content URLs and provider job metadata.
• OpenAI API: enabled AI-assisted outreach drafting and workflow decisions; the creator, campaign, prospect, and conversation context provided to that feature. Google Workspace API data is not authorized for model training.
• GitHub: source control and supplemental synthetic monitoring; operational metadata and restricted review evidence.

Deferred providers

• Slack: deferred by the approved initial product scope.
• Cal.com: not used for the current scheduling flow.

Changes and objections

The Data Processing Addendum describes notice and objection terms for new subprocessors. Questions or objections may be sent to support@tryvirali.com.