Current public list
Virali Subprocessors
Virali provides at least 30 days' notice before a new subprocessor begins processing Customer Personal Data. Customers may submit a reasonable data-protection objection within 15 days. Provider certifications are not Virali certifications.
Active production providers
| Provider | Purpose | Data categories | Status |
|---|---|---|---|
| Stripe | Payment processing and recurring subscription management when paid billing is enabled | Billing contacts, customer/subscription identifiers, payment and consent metadata | Active for paid billing; card data is handled by Stripe rather than stored by Virali |
| Render | Application hosting and service runtime | Workspace account data, logs, configuration metadata | Location/certifications pending vendor review |
| Supabase | Postgres database, Auth, storage, backups | Application data, Auth data, files, logs | Location/certifications pending vendor review |
| Resend / configured SMTP provider | Production transactional email | Email address and email delivery metadata | Location/certifications pending vendor review |
| Bright Data | Approved creator/content analytics workflows | Public social content URLs and provider job metadata | Location/certifications pending vendor review |
| Google APIs / Gmail | User-authorized email outreach sending and reply synchronization | Connected mailbox identity, email message/thread metadata, message content needed for outreach workflows, OAuth tokens encrypted server-side | Active when a workspace user connects Gmail |
| OpenAI API | AI-assisted outreach drafting, reply classification, pricing suggestions, and workflow decisions | Creator, campaign, prospect, Outreach conversation context, and relevant Gmail reply content for known Outreach conversations when AI Outreach is enabled | Active only when AI Outreach is enabled; Google Workspace API data is not authorized for model training |
| GitHub | Source control and supplemental synthetic health workflow | Operational metadata and issue/PR evidence | Location/certifications pending vendor review |
Deferred providers
- Slack: Deferred by the approved beta scope
- Cal.com: Not used for the current scheduling flow