Terms of Use

1. Using Clipeo

Clipeo connects creator profiles with brand workspaces. Depending on account type and review state, users can maintain profiles and portfolios, publish or browse opportunities and packages, submit campaign applications, and communicate in marketplace threads.

Use an account only when you are legally able to do so. Keep account details accurate, protect sign-in credentials, and use only accounts and brand workspaces you are authorized to control.

2. Content and communications

Only upload or share content you have the right to use. Do not use Clipeo for unlawful, deceptive, abusive, threatening, infringing, malicious, or privacy-invasive material. Do not attempt to bypass access controls, impersonate another person or business, or interfere with the service.

Creators and brands remain responsible for confirming a brief, deliverables, usage rights, price, deadlines, and other commercial terms before work begins.

3. Marketplace transactions

The current product supports discovery, applications, packages, campaign context, and direct messaging. Protected payment, escrow, payout, refund, and dispute-resolution services are not represented as active product features. Do not rely on Clipeo as an escrow or payment guarantor.

4. Safety and enforcement

Users can report content or accounts and can block marketplace accounts from sending new messages. Existing conversation history may remain visible for context and reporting. Product administrators can review reports and may restrict access where the account state or product rules require it.

For immediate conversation controls, use the in-app report and block actions. See Support for current self-service options.

5. Account deletion

Authenticated creators can request permanent account deletion from Profile → Account & security → Delete account. The request requires the current password and targets only the signed-in account. See the public account deletion instructions.

6. Policy status

This version is the document identifier used by the mobile legal-consent contract. Publishing a later approved version requires a new version identifier and corresponding product rollout; acceptance records must not be silently reassigned to different text.