> For the complete documentation index, see [llms.txt](https://docs.gearrunner.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gearrunner.app/faq.md).

# FAQ

<details>

<summary>1. Do I Need Crypto Knowledge?</summary>

No.

Gear Runner is playable as a normal mobile game.

Blockchain technology works in the background and does not interfere with gameplay.

</details>

<details>

<summary>2. Who Is This Game For?</summary>

* Fitness-focused users
* Casual mobile gamers
* Competitive runners
* Strategy-driven players
* Web3 users seeking real utility

</details>

<details>

<summary>3. How does Gear Runner prevent cheating?</summary>

Through a multi-layered anti-cheat system that includes:

* GPS & motion validation
* AI-based pattern detection
* Device fingerprinting
* Third-party audits and immutable logs

This ensures fairness and transparency for all users.

</details>

<details>

<summary>4. How is user data protected?</summary>

Gear Runner enforces:

* Minimal data collection (only activity-relevant data)
* User control over privacy settings
* AES and TLS-level encryption
* GDPR-aligned compliance for international data protection standards

</details>

<details>

<summary>5. What are Tech Fragments?</summary>

Tech Fragments are crafting materials obtained through running, dismantling, or spinning the Lucky Wheel.\
They are used to upgrade or fuse Gear Modules, adding depth to the earning and progression system.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.gearrunner.app/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.