1. Scope
This page identifies the core third-party providers Vibeler uses to host, process, secure, deliver, and support the Services. A provider's role applies only when the related Vibeler feature is used.
2. Current core subprocessors
- DigitalOcean: app hosting, backend/frontend infrastructure, managed compute, databases, workers, network operations, and related service hosting.
- Cloudflare and Cloudflare R2: object storage, media storage, signed media support, custom-domain/SaaS hostname infrastructure, DNS or edge services where configured.
- Stripe: payment processing, subscriptions, Connect onboarding, payouts, invoicing, card/payment method handling, fraud screening, disputes, and chargebacks.
- SendGrid: transactional email, newsletter sending, delivery events, bounce/drop/spam/unsubscribe signals, and email templates.
- OpenAI: text generation for creator AI tools, including prompts, selected context, generated drafts, generated quiz drafts, and operational metadata. OpenAI's API data-handling terms and applicable account controls govern provider-side retention.
- GitHub/GHCR: source control, CI/CD, and container image build and registry workflows. These systems support software delivery and are not used as the primary store for Vibeler user content.
3. Live Room transport when enabled
Native Live Rooms use Vibeler-operated realtime servers hosted by DigitalOcean. They receive the audio and video that hosts and speakers publish, together with the connection information needed to carry it (IP address, network candidates, device codec support). When a network blocks direct media, the connection is relayed by Cloudflare's TURN service. The audience receives the live stream and room activity (chat, questions, reactions, speakers, visible listeners) from Cloudflare R2 and Cloudflare's network; listeners send no audio or video. To keep access rules in force, a listener's browser checks in with the live server about once a minute; this check-in is kept in memory for about two and a half minutes to count who is present and is deleted when the session ends. Server and network logs do not record listeners' IP addresses at informational level and are kept for at most 14 days.
4. Changes to subprocessors
Vibeler may add, replace, or remove subprocessors as the Services evolve. Vibeler will document material changes and, where required by contract or law, communicate them with reasonable notice.
5. Creator data responsibilities
Creators who collect, upload, or message audience members through Vibeler should review this list and determine whether their own privacy notices, contracts, consent language, or data processing arrangements need updates.