/privacy

Privacy

This Privacy summary reflects the categories of information Grovoo currently handles across authentication, content, commerce, messaging, moderation, and launch operations. It is a real product-aligned baseline and should still receive final legal review before broader public release.

Information we handle

Grovoo currently stores account identifiers, session data, creator profile data, content metadata, message content, notification records, commerce and payout records, moderation records, support and feedback records, and operational logs.

Uploaded media is stored through the current media pipeline with public-safe previews and protected delivery controls where access decisions require them.

How data is used

We use platform data to operate accounts, authenticate sessions, deliver content, process purchases, grant entitlements, review moderation and support issues, process payouts, investigate fraud or abuse, and maintain service reliability.

Operational data may also be used for launch metrics, funnel analysis, and internal product hardening during open beta and v1 readiness.

Sharing and retention

Payment processing and billing events may involve third-party provider data exchange within the current CCBill integration boundary. Storage and delivery infrastructure may involve S3-compatible object storage and secure internal service components.

Retention periods vary by legal, accounting, safety, and operational needs. Some moderation, payment, and audit records may be retained after account closure when required for safety, finance, or compliance reasons.

Current limitations

Grovoo is still refining some support, KYC, and notification workflows. This page is intended to be honest about the current state rather than imply broader privacy guarantees than the system can actually support.

Related resources

Use the public web to orient first, then move into the app only when you need account-bound actions.