Data and Cookies

What data flows through Gruplly

Gruplly handles account details, group and course content, membership records, invite links, uploaded media, and billing state required to operate creator communities. That includes information such as names, email addresses, avatars, course progress, and group settings.

Infrastructure providers

Authentication is powered by Supabase. Product data is stored in PostgreSQL through Prisma. Payments are processed by Stripe. Transactional email can be handled by Resend. Error monitoring is connected through Sentry. Media assets may be stored in connected object storage.

Current cookie posture

Gruplly currently relies on functional cookies required for authentication, redirects, and secure session handling. These are product-operational cookies rather than ad-tech or marketing-tracker cookies.

Based on the current codebase, there is no separate marketing analytics stack such as PostHog, GA, Mixpanel, or Segment wired into the public site. If that changes, the launch trust layer should be updated and a visible cookie notice should be reconsidered immediately.

Why there is no cookie banner right now

The current implementation does not justify a generic marketing-style cookie banner. The application uses strict operational cookies and authentication/session behavior needed to make the product work. If non-essential analytics, advertising pixels, or broader tracking are introduced, this decision should be revisited before public scale.

What to do next as the product grows

Before adding broader analytics, retargeting, or experimentation tools, Gruplly should define a stronger consent posture, review jurisdictional requirements, and update both the privacy policy and this page so the trust story stays coherent.