Privacy
Privacy Policy
Communo helps creators and educators operate communities, courses, events, payments, messaging, automations, and analytics. This page explains the privacy model the product is being built around.
TLDR
- Communo uses account, community, course, payment, messaging, and analytics data to run the product.
- Community owners control the member data inside their own communities.
- Supabase, Vercel, Stripe, Resend, Twilio, Bunny.net, Inngest, and AI providers may process limited data.
- Native mobile apps are future-facing, but the API-first backend is designed to support them later.
Overview
Communo collects only the information needed to create accounts, run communities, deliver course and event experiences, manage paid access, send communications, and provide analytics to creators.
Data we collect
This may include names, emails, avatars, profile details, community memberships, roles, posts, comments, reactions, course progress, event RSVPs, tags, notification settings, payment references, and delivery metadata for email or SMS.
How we use data
Data is used to authenticate users, isolate each community, unlock paid content, show member progress, deliver notifications, power CRM automations, send broadcasts, generate analytics, and keep the service secure and reliable.
Service providers
Communo is expected to use Supabase for auth and data, Vercel for hosting, Stripe for payments, Resend for email, Twilio for SMS, Bunny.net for video, Inngest for background jobs, and connected AI providers when a community owner enables AI features.
Community owner data
Creators and admins can access member lists, tags, purchase status, progress, engagement metrics, and broadcast results for the communities they operate. Communities are designed to remain isolated from one another.
Retention and security
Data should be retained only as long as needed for product operation, legal obligations, dispute handling, security, and backups. Supabase row-level security, scoped API access, and environment-managed secrets are core parts of the intended security model.
Your choices
Members should be able to update profiles, manage notification preferences, leave communities, and request account or data changes where applicable. Email and SMS communications should include preference or unsubscribe controls before production use.
Contact
Privacy requests, account questions, and production legal reviews should be routed through the official Communo support contact once configured.