Sub-Processors
Last Updated: April 26, 2026
Phera relies on the third-party providers listed below to deliver the Service. Each is bound by a data-processing agreement and is contractually prohibited from using your data for its own purposes (including model training, except where strictly necessary to deliver the Service back to you). We update this list when sub-processors are added or removed.
| Provider | Purpose | Data | Region |
|---|---|---|---|
| Supabase | Postgres database, auth, file storage | All account, wedding, guest, RSVP, message, and vendor data | United States (AWS us-east-1) |
| Vercel | Web hosting + edge runtime + cookieless analytics | IP, request metadata, aggregated page views | United States (global edge) |
| Meta (WhatsApp Business Cloud API) | Sending guest-facing WhatsApp templates and Concierge messages | Guest phone, name, message body, message status | United States / Ireland |
| Whapi.Cloud | Mirroring WhatsApp vendor groups for the Coordinator product | Vendor group messages (text/voice/image), participant phone numbers | European Union |
| Anthropic (Claude) | LLM for Concierge replies, summaries, and AI builder | Inbound guest messages, wedding context, vendor message summaries | United States |
| Groq | LLM inference (Llama) and Whisper speech-to-text | Inbound guest text + voice notes, vendor voice notes | United States |
| OpenAI | LLM and Whisper speech-to-text (where used) | Inbound guest text + voice notes | United States |
| Stripe | Payment processing and subscription billing | Couple billing details, last-4 of card, transaction metadata. Phera never stores full card numbers. | United States / Ireland / India |
| Resend | Transactional and (opt-in) marketing email | Recipient email, subject line, message body | United States |
| Sentry | Error monitoring, traces, and source-map debugging | Stack traces, request metadata; PII scrubbed where possible | United States |
To request notification when this list changes, email privacy@phera.io with the subject "Subscribe sub-processor updates." You will be notified at least 30 days before a new sub-processor begins processing your data, with the right to object as described in our DPA.
Phera was built by a couple frustrated with the complexity of planning a modern Indian destination wedding. We knew there had to be a better way—so we built it.
Making Indian weddings beautiful to plan, not just beautiful to attend.
© 2026 Phera Events. All rights reserved.
Phera Events is owned and operated by Ghumaan Ventures, LLC.