Terms of service
Last updated: March 20, 2026
This page summarizes the main operating rules for using Fluencity as a brand, creator, or platform operator, based on the current runtime behavior.
Eligibility and accounts
Fluencity is intended for legitimate brands, creators, and approved operators using the marketplace for real opportunities, contracts, communications, and payout workflows.
Users are responsible for keeping account, organization, and creator profile information accurate, current, and not misleading.
Role-based areas of the product are restricted. Brand, creator, and admin actions each carry different permissions and responsibilities.
Marketplace activity
Brands may create organizations, publish opportunities, invite creators, fund approved contracts, review deliverables, and request refunds where supported by the payment flow.
Creators may build profiles, apply to opportunities, submit deliverables, receive review decisions, connect payout details where supported, and use messaging or collaboration features when the required relationship exists.
Fluencity can limit or remove marketplace activity that appears fraudulent, abusive, misleading, unsafe, or inconsistent with platform controls.
Payments, approvals, and payouts
The current product uses approval-based payment logic. Contracts are funded by brands, deliverables are reviewed, and creator payouts are only released after contract approval and payout-account readiness.
Not every country is live for payouts. Country routing and payout availability are controlled at the platform level and may differ by provider and support status.
Platform fees, refund handling, payout restrictions, and dispute effects are governed by the relevant payment and refund policies and by underlying provider requirements.
Moderation and enforcement
Fluencity includes report submission, admin review, audit logging, and country-routing controls. Reports can be reviewed, resolved, dismissed, or escalated by authorized admins.
The platform may pause, restrict, suspend, or remove access to users, organizations, content, contracts, payouts, or other activity where operational, legal, trust and safety, fraud, or payment-risk concerns require intervention.
Changes and operational status
Because Fluencity is still evolving, features, country availability, payout corridors, and enforcement controls may change over time.
These terms should be treated as an operational summary of current platform rules, not a final launch-ready legal document.