Terms of use
This draft describes the relationship between [legal entity name] and TRENDX users, including taking and creating surveys, interacting with content and using related services.
- Responsible entity
- [Legal entity name and registration details]
- Contact
- [Approved support channel and contact details]
- Last updated
- [Approval date for this version]
Operator and service scope
The platform is operated by [legal entity name] under [approved registration or licensing details]. Available services, intended users and service locations: [complete the actual scope].
Accounts and eligibility
Users provide accurate information, protect their sign-in methods and do not share verification codes. Complete the requirements for eligibility, age, representing organizations and multiple accounts before approval: [approved requirements].
Participation and content
Users respect others’ rights and participate honestly, avoiding impersonation or abuse of surveys and rewards. Content, attachment, moderation and appeal rules: [actual rules and review process].
Content ownership, permissions needed to display it and process survey results, and limits on creators’ use of results: [approved wording].
Fees, points and rewards
Paid service details and charges are shown before an order is confirmed. Complete the rules for earning and redeeming points, provider terms and handling errors: [approved rules].
This draft does not assign a cash value to points, determine refund eligibility or promise a payment date. Complete those matters in the approved terms and policy.
Availability, restrictions and account closure
Set out maintenance, account restriction or termination, notices, appeals and effects on content and pending orders: [approved procedures]. Account deletion requests are reviewed under the deletion policy; recording a request is not confirmation of erasure.
Changes, contact and disputes
Complete liability, applicable law, jurisdiction and dispute resolution provisions: [wording reviewed by the appropriate adviser].
Updates have a clear date and version. State how users are notified or asked for consent when required: [approved process]. Contact: [approved contact details].