/terms

Terms

These Terms describe the current Grovoo platform categories, account expectations, payments baseline, moderation authority, and creator responsibilities for the current open-beta and v1 scope. This page is structured for launch readiness and should still receive final counsel review before any broader public launch.

Platform use

Grovoo currently provides public discovery, creator pages, fan and creator app surfaces, subscriptions, PPV unlocks, messaging, notifications, library access, payout requests, moderation, and admin operations tooling.

Users must maintain accurate account information, follow applicable law, and avoid fraud, abuse, harassment, impersonation, spam, payment misuse, or unlawful content uploads.

Creator obligations

Creators are responsible for the content they publish, the rights they claim to that content, age and consent compliance, payout accuracy, and honest communication with fans.

Grovoo may require identity or consent documentation and may pause publishing, commerce, payouts, or account access while creator approval or KYC review is pending.

Payments, refunds, and access

Subscriptions and PPV unlocks are processed through the current Grovoo commerce stack and its payment-provider boundary. Internal Grovoo order, ledger, entitlement, and payout records remain authoritative for platform operations.

Refund and chargeback outcomes can affect content access, creator earnings visibility, and payout eligibility. Some provider-side actions are still handled manually under Grovoo finance review.

Moderation and enforcement

Grovoo may remove content, restrict messaging, suspend accounts, reject creator approval, or escalate reports and legal requests where safety, fraud, or compliance concerns exist.

These Terms do not promise uninterrupted availability, guaranteed earnings, or immediate payout timing. Launch operations remain subject to review, holds, and platform safety controls.

Related resources

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