Sub-processors
Last updated: April 2026
Blisso uses the categories of providers below to deliver the product. Exact vendors depend on your deployment and configuration; update this list to match production (for example if you use a different email provider). See also our Privacy Policy.
| Provider | Role | Privacy |
|---|---|---|
| Vercel | Frontend hosting and CDN (typical deployment). | vercel.com/legal/privacy-policy |
| Railway (or similar) | Backend API and worker hosting (typical deployment). | railway.app/legal/privacy |
| MySQL / managed database provider | Primary application database as configured in your environment. | www.mysql.com/about/legal/privacy/privacy-policy.html |
| Google Sign-In (OAuth), fonts (optional), and related Google-hosted scripts or APIs the browser loads when you use those features. | policies.google.com/privacy | |
| Twilio | SMS OTP and WhatsApp messaging where configured. | www.twilio.com/legal/privacy |
| Resend | Transactional email when configured (typical): account verification and security messages, product notifications, and contact form delivery via the Resend API. Other SMTP providers may be used depending on deployment. | resend.com/legal/privacy-policy |
| Firebase Cloud Messaging (Google) | Push notification delivery and Firebase Installations / device registration for web (and mobile where enabled). | firebase.google.com/support/privacy |
| Cloudinary | Image and media hosting when configured (for example event or organization cover images uploaded from the web or mobile app). Files are sent to Cloudinary under your org’s use of the product. | cloudinary.com/privacy |
| OpenAI | Optional Event Co-Pilot / AI draft generation when you use that feature. | openai.com/policies/privacy-policy |