Last updated 2026-11-01 (version 2)
Sub-processors
The vendors HAVA Export B.V., trading as Vibel engages to run Vibel Reply, and what each one processes.
Sub-processors Vibel Reply engages
| Name | Purpose | Data processed | Region |
|---|---|---|---|
| Vercel | Application hosting and edge network | All data in transit through the app, as HTTPS requests and responses | US |
| Railway | The background worker that sends Instagram DMs | Campaign, webhook, and delivery-log data needed to process a send | US |
| Supabase / PostgreSQL | Primary database | Account, workspace, campaign, and encrypted Instagram token data | EU or US, depending on the project |
| Redis | Queue for comment-to-DM jobs | In-flight job payloads (comment and campaign references), short-lived | US |
| Resend | Transactional email (magic-link sign-in) | Recipient email address and the sign-in link content | US |
| Meta (Instagram, Facebook Messenger, WhatsApp) | Sending the private reply and, optionally, the public reply, and messages on the Meta channels you connect | The comment, the connected Instagram account's credentials, and the message content you configured | US (Meta Platforms), EU Standard Contractual Clauses |
| Stripe | Subscription billing and payments | Billing email, plan, and payment details entered at checkout (card data goes to Stripe, not to us) | US (Stripe), EU Standard Contractual Clauses |
| Anthropic | AI model for the Reply Copilot and AI replies | Prompts you submit and the comment and message text needed to draft a reply or flow | US, EU Standard Contractual Clauses |
| TikTok | Connected TikTok account features, when you connect one | The connected TikTok account's credentials and the content and events needed for your campaigns | Varies by TikTok entity, see TikTok's privacy policy |
Changes to this list
If Vibel Reply adds a new sub-processor, we will update this page before the change takes effect. Email legal@getvibel.com to be notified of changes.
Contact
Questions about this list: legal@getvibel.com.