Legal
Sub-processors
The companies that help us run Viralix. Last updated 22 October 2026.
This document describes how Viralix works today. It is a draft for the operator's legal review before launch and is not legal advice.
These companies process personal data on our behalf, under contracts that limit them to our instructions. We will update this list before adding a new sub-processor that handles personal data, and you can write to support@viralix.art with questions or objections.
| Company | What it does for us | Data involved | Location |
|---|---|---|---|
| Supabase | Managed PostgreSQL database | Account, workspace, content, inbox and analytics data | Tokyo, Japan (AWS ap-northeast-1) |
| Cloudflare | Object storage (R2) for media files, and DNS | Images and videos you upload; DNS queries for viralix.art | Global network |
| Resend | Transactional email delivery | Recipient email address, name and the content of service emails | Provider-managed regions |
| Oracle Cloud Infrastructure | Application hosting (web, API and background workers) | All data while it is processed by the application | Provider-managed region |
Platforms you connect
Meta (Facebook and Instagram), Google (sign-in and YouTube) and TikTok are not our sub-processors. They receive and provide data because you choose to connect your accounts, under their own terms and privacy policies. See the privacy policy for how we handle data we receive from them.