> For the complete documentation index, see [llms.txt](https://www.size.club/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.size.club/docs/help/fair-play.md).

# Fair play and access

Review Size age and location requirements, fair-play rules, account restrictions and private verification guidance.

You must meet the age, capacity and eligibility requirements in [Terms Section 4](https://www.size.club/legal/terms-of-service.pdf). Read the [restricted jurisdictions](https://www.size.club/legal/restricted-jurisdictions.pdf) before using Size. Access to a screen does not confirm eligibility.

## Play fairly

* Use one account per person unless Size expressly permits otherwise.
* Make your own trading decisions and follow restrictions on automation and account sharing.
* Do not self-refer, farm rewards, collude or exploit bugs.
* Avoid scams, harassment and spam.

Breaches can invalidate results or restrict your account under the Terms and program rules. If a rule is unclear, [contact support](/docs/help/support.md) rather than assume an exception.

## Verification

Use Size's private verification channel if information is requested. Never post identity documents, sign-in codes or wallet secrets in public chat.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.size.club/docs/help/fair-play.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
